How might I create a "step-by-step process" content type? I'm thinking about creating a process manual for an intranet. Most (all?) of the processes have a very clear order, although the actual order may change from time to time. The plan is to have the subject matter experts, probably a half-dozen or so, enter and update the process pages. The users of the site need to be able to quickly review the processes while interacting with customers, often face-to-face.

Here's the options I've thought of:


Train the authors to use ordered lists. Pro: easiest for me. Con: relies on training non-technical people, could be hard to style for readability.
Organize each process into a book. Pro: uses something that's already there. Con: harder to enter, complicated to read.
Create a content type with a "step" field that could be entered unlimited times, and theme so as to show the order number. Pro: easy to see that each step is independent, can be reordered easily (?) Con: more work for me (I feel like there something else in this option that I'm missing, but I can't put my finger on it!)
Custom module, something like the Recipe module but w/out ingredients. At least I'm assuming the Recipe module has step-by-step directions. Pro: most customization for entry, learning experience. Con: a LOT more work for me, kinda out of my expertise.


From your experience, is there a clear winner among these options?

Is there an option I'm missing? (is there a module out there that already does this, for example? Googling this concept was a nightmare.)

Am I over-thinking this?

I don't know yet whether this project will be Drupal 6 or 7.
I agree with Craig Hyatt but I thought I'd expand a bit more.

Train the authors to use ordered lists - Like you said it's more effort for you to train users. Your times better spent developing the final product in my opinion.

Organize each process into a book - Why re-invent the wheel? It provides you with the basics of your requirements out of the box. Using this will give you the extra time spent developing something to work on the cons of using this, or better put you get to spend more time adding helpful stuff than building it from the ground up.

Create a content type with a "step" field - You mention that this could be more work for you but it's not a huge amount, using CCK and nodereference this could give you a bit more flexibility compared to the book route.

Custom module - There's no need to do this, the above two points will give you enough freedom to code around drupals inbuilt options.

The clear winner for me would be to create a content type and build around that. You can actually set up a content type to use book functionality as well which is what I'm currently doing for a large project. So in this case you get the best of both worlds.