Zines have special needs, including a author management and workflow. If you have a small magazine running on drupal (or another CMS) what do you wish drupal would do to make your site work better, and be easier to administer?

Please leave a comment here!

Comments

tag-1’s picture

One thing that comes to mind quickly is multiple 'zines, similar to multiple blogs. Ideally, they'd have choosable layouts/themes (NOT visitor-configurable), and able to have a distinct URL rather than 'node/87' or whatever. I suppose alias'ing could handle that part.

Motime's blog creation module(s?) is a good example and quite nice, letting users choose a layout/theme from a visual catalog.

Another idea, not specific to zines but overall, is the word "node" itself. What an ugly word! I suppose many will find such nit-picking silly, but ugh. The only field I'm aware of that uses the term is (computer) networking or medical (lymph nodes). First replacement I can think of is 'item'. Maybe there are better ones...

In an older version of Drupal I used I just renamed 'node.php' to 'article.php' (and think maybe hacked some internals to deal with this), but something less "tech-y" would be nice. I need to take a look but this might be easy to do with mod_rewrite or a similar style hack in a page handler.

A robust workflow mod might be useful -- I've seemed to manage in the past with roles and (publish) permissions. This doesn't allow granular perms though like "the Arts editor can publish work into the Art section only". I think many zine-specific features might clash with the more general nature of Drupal.

Of course this then veers into a big CMS vs. community software vs. publishing sw, etc. etc. discussion, and the "do one thing and do it well" UNIX philosophy, etc.

robbt’s picture

Issue Management- useful for magazines which are also print zines. This would mean that articles could be clumped into articles and sort of sorted by that. This could probably be handled by a new taxonomy term.That each item could have.

Content Layout- this seems to be the biggest stumbling block towards making Drupal really useful as a zine at least for us. The whole dichotomy between front page, the haphazard administration and voting thing seems to orientate everything to a slashdot/blog style layout where as a magazine would typically have a more static or at least organized via topic front page. It just seems that having a main column and then a bunch of administrative blocks on either side is a little limiting as far as layout goes. If you could have multiple columns in the main block that were arranged with different categories or a taxonomy term as the heading that might go a ways to make it easier. Like a sports or politics section.

Another thing in general that might help with drupal would be something similar to the node_image module but allows one to associate files that could be used as HTML tags rather than auto-insert also such as a PDF version of articles and what not. This would be cool, prolly not to hard.

I could think of more, such as repeating events within the events module, but thats about it for now.

christina@widgetopia.net’s picture

Drupal doesn't seem to have a staging ground (i.e. a place for editors to see how next week's issue looks like). I assume one would get around that with permissions and roles?

Malthus’s picture

Drupal's workflow does need some improvement, but it already has all the basic functionality. You can simply give editors access to unpublished items, while access will be disallowed for regular users.

antony’s picture

Although any comments posted by editors prior to publication appear as comments post publication. It would be nice if these pre publication comments could be hidden from regular users.

bertboerland’s picture

Just to make sure we all use the right vocabulary; drupal doesnt have workflow (as mosts CMSes dont have that)

Workflow (define) is something else than having a Authorisation and Authentication layer.

--

groets


bertb

--
groets
bert boerland

freyquency’s picture

i'm curious if anyone who wrote here has tried the workflow module yet. I've just installed it, and i'm having a bit of trouble configuring it to what I need, but that said I'm the "web guy" not the "magazine guy", so sorting out the different 'users' is confusing; i'm just testing everything out before the magazine goes to print (and ahem, web.)

I think that a taxonomy that could seperate by issue #, possibly weighted (to accomodate a reasonable interpretation of the table of contents), and include things under default content types (reviews, news, etc) would be great. Other than that a setup that really helps fine tune content creation, preventing / decluttering things for specific roles and doesn't let anything 'leak' (statistics module does this with view permissions) would be crucial to managing AND publishing a magazine.

this post brought to you by:
`':,..,:'``':,..,:'``':,..,:'``':,..,:'`
erik mallinson