[wp-hackers] Two new, long-overdue plugins to make your wordpress life a little easier...

[Ryann Micua]

I think what Marcus is trying to say here is create 
content/changes/modifications in dev, send it to staging where qa takes 
a look at it "live" not as "draft", then when it's all good, the 
content/changes/modifications are pushed to production. Which is why you 
don't need to generate content from the production site because content 
generation starts from dev.

I'm guessing that for Marcus, the clients wants to be able to "preview" 
the "live" site before actually "publishing" the content/modifications 
to the public. DEV is for Marcus, STAGING is for the client/qa, 
PRODUCTION for the world.

Which is why he wants to be able to use root relative urls.

On Tuesday, 01 November, 2011 01:13 PM, 
wp-hackers-request at lists.automattic.com wrote:
> So to be clear, Marcus, all this and you're not even using WordPress to generate content on the production server? Why*don't*  you use a more CMS-centric solution like Joomla! or Drupal?
>
> You're ignoring WordPress's own publication workflow and instead using separate databases to create a workflow. WordPress is, at its*core*, a blogging platform. If you're blogs require three databases to properly workflow, I don't think a blog is what you're actually looking for.
>
> That said, I do enterprise-grade WordPress sites for a living, including sites that may not be readily consider a "blog." I love WordPress, and have had no significant challenges in my workflow. But once the site is live, new content is created on the production server and published when it's approved. Why on earth would I need two or three databases (or at least schemas) to create content workflow when it's built right into the platform? (BTW, I also have clients that require WCGA 2 AA compliance, and it's not a problem. )

-- 
*Ryann Micua*
/Web Developer/
------------------------------------------------------------------------

Website: /www.pogidude.com/
Skype: /rmicua/
Mobile: /+639169273059/