I've had a little bit of time to think about this. Many interesting and thought provoking posts. Charley, I think you're getting somewhere. Don't hide so much. ;)
The idea of defining the different types of workflow is what's needed. Some of them we all support, others we don't - or don't want to. Here's what I've come up with so far: Life cycle: create/publish/archive/delete dates Authoring: custom content creation forms etc. Approval: Chain document approval like departments or up hierarchies etc QA: dev/staging/production transitions What am I missing? NOTE: There's a difference between QA and approval in case you're wondering. Approval is for internal content management and QA is for publishing (functionality etc). a. -----Original Message----- Behalf Of Charley Bay However, where I get stuck is when "workflow" in the general CM use can mean *anything*, and that's where I don't know where workflow starts and stops nor even what it *is*. Is workflow authoring? storing? reviewing? approving? editing? expiring? deleting? Heck, if it's everything, then it is nothing (the term lacks any specificity). In creating content managing tools, I must admit, I have a specific approach to "workflow": When I hear the word, I scream in terror as loud as possible and run away. (This has caused me great stress in my personal life. I hide under my bed for weeks at a time. I tremble in fear at hearing each falling footstep. I wake up from nightmares in cold sweats. I'm pretty sure "they" really *are* out to get me.) --charley [EMAIL PROTECTED] -- http://cms-list.org/ trim your replies for good karma.
