What should we use for the software of the magazine?

My inclination would be to quick it simple and use vanilla Joomla!, as much as possible. (That way, we could also include a basic "how to" for the first issue.)

Ideas:

- Section for the entire Magazine

- Category for each month. And then, of course, an Article for each Article. :)

- Category for all of the Author Profiles. And an Article for each Author. Recommend using a Standard Article format for each Article Profile, along with a nice picture. Also recommend updating the profile and link to each Article an author writes. The Article itself should include a link to the profile from each article or we can make a quick module to embed a bit of the profile, with a link to the full page.

- Use Meta Tags so that Related Items Module can be used for basic Tags. This should be enough.

The Cover Page of each Issue can be a simple Category Blog.

Also, need a page listing all issues. That could be a simple Article page with hardcoded links. Something very easy.

We might want to recruit a designer who would work on layouts and provide specifications for image sizes, pay layouts, typography, etc. Anyone know a designer?

Other ideas on technical aspects of the magazine? Joomla! core really is plenty, IMO, for a basic community magazine.

Views: 26

Replies to This Discussion

Thanks for kicking off this discussion Amy. I think the approach you have laid out here makes sense, and I also like the "keep it simple" theme you touched on more than once.

At this point I am trying to keep an open mind (and a blank slate) on pretty much everything. I am looking forward to having Michael weigh in with his thoughts on this subject as well as the others that are being brough up now that this project is starting to get off the ground.

I have traded some messages with Michael over the last day or so. I know he is looking forward to this project. My sense is he wants to collect his thoughts before diving in here, which isn't necessarily a bad thing for a project like this.
Yes, it will take a bit to bring everyone together and gather ideas. I briefly talked to Mike yesterday, as well. He was hoping to stop by as soon as he can. It's not a good idea in a free software project to sit and wait. Let's keep discussions moving so we don't lose interest and communicate in the open so anyone can participate. Those are the ingredients for a collaborative environment where good things happen.
I understand and respect your point that it's not a good idea in a free software project to sit and wait. Another point is that at the start of a project, it's a good idea for the team to get some direction from the leader before moving too far in any direction.

I don't mean to discourage any discussions (in fact I started a new one a few minutes ago), but I just think we should keep those discussions pretty broad and high level until Michael weighs in, which along with you I also expect will be soon.
It's all good! I talked to Mike, too, and he said he will join us when he is able. Meanwhile, people can talk and the conversation is here for everyone to read, when they are able, there is simply no reason to be concerned.

We are using a participative model, not an in charge model. If others want to lead, the way we handle that is, they simply say "I want to lead, too", and they are also leaders. It's very, very, very community oriented rather than top-down. We only had one volunteer in this group so far, but I expect we will wind up with several leaders before it's done. Some people might like leading certain aspects and shared leadership shares the burden, too.

The difference is that the leader's job isn't to bring the plan to the others and assign tasks, but rather to keep the group generating ideas and moving towards consensus. We try to encourage any discussion, rather than limit it until someone arrives. We want ideas. All of them. Even if the group decides not to use most of them.

It is a little different approach from a business world, mainly because it's more like a neighborhood or a church community. But folks tend to like it after working with it for awhile. It takes the pressure off of everyone and helps people come to agreement together. Keeps people feeling like they have ownership in the process.

The other half of that, and this might be what helps you feel a bit better, is that consensus is an important element of the group decision making. There is no reason to worry that it will all be decided before Mike arrives. It will be decided as a group, and that will naturally include Mike.
If it gets decided to use Joomla! to "publish" the magazine, will the obvious domain be magazine.joomla.org ?

Some of the people who are future leaders in our community, haven't even been to our website yet, or may have never used Joomla! yet! There will always be a "melting pot" in our community!

Here's an idea: If it is decided to use Joomla! to publish the magazine, wouldn't it be very COOL to do it with 1.6? The ACL system would open many opportunities for our community magazine!
I think we should use Jxtended Magazine, myself. It's tailor made for the job, as other people have suggested.
Before we decide what technology to use, can we talk about how the magazine is organized?

Issue numbers?

Topics?

Certain months?

It's likely that a visitor may wish to see the November 2009 issue, all articles that are about beginning Joomla, specific articles about templating and CSS, or all articles written by Amy Stephen.

Agreed? I think that's pretty typical for a magazine.

A straight section/category system does not support this well.

We will need a tagging technology so the site visitor can slice and dice up the magazine articles to view what's of interest.

I believe K2 does this well and it's GPL. That's what I would suggest. If there are other technologies that slice and dice content well, as I've described, we can certainly consider those as well.

thanks,
Jen
Much better approach. Let's think about the types of information.

Issue, (ex. January 2010, New Beginnings All Together)

Magazine Sections (Site Builder, Community, Developer, Site Profile, whatever),

Topics (Security, CSS, JUGs)

Author: Name, Profile, Web site, Listing of Author's Articles

- In terms of what application to use, I do like the idea of using Extensions from different developers, especially very popular pieces that many have already found to be stable. Free of charge GPL is an obvious plus. Part of the reason I recommend staying close to core on joomla.org is this discussion.
Amy - Yes of course people can talk, I hope you don't think I was suggesting otherwise. And no there is no reason for concern, I am not concerned I was just expressing my opinion.

I am also not suggesting that this group should have a top-down model, where the leader's role is to tell us how everything will work and to assign tasks to all of us. I love consensus and I love a participative environment. I do think that the dynamics of leadership in a participatory model are a bit more complex than how you characterized them, but I'll leave that for another thread ;-p .

I want to help produce a great online magazine. I also hope we can take advantage of every asset and resource we have so all the work can get done efficiently and with as few stops and starts and course changes as possible.

That last point is where I see Michael's experience as a valuable asset to this group, especially as we are starting out. And that's why I think it's a good idea to hear him weigh in with his thoughts before we move too far in any direction.
And K2 has ACL, plus with JoomFish added to it, we have "instant' translation built into the Magazine.

Talk about "killing 2 birds" with one stone!
I think we're good, yes? I'm sure Mike will be here as soon as he can and everyone is eager to get a great issue. Let's have fun!
I guess the key question that arises is this "just" a community magazine or are we trying to address a broader audience and attract more new members to the community?

If the latter is the case then my bias would be to utilise the the maximum functionality and formatting capacity we can in order to showcase the capability of our beloved platform.

What is the consensus on this?

BTW - Any ideas on what we are going to call our publication? After all it will be the best open source community magazine on the planet!!!

Cheers
Mike

RSS

Badge

Loading…

© 2012   Created by Amy Stephen.

Badges  |  Report an Issue  |  Terms of Service