david at kineticode
Jul 16, 2009, 11:31 PM
Post #6 of 7
(1216 views)
Permalink
|
|
Re: Seeking advice for redesign staging environment
[In reply to]
|
|
On Jul 14, 2009, at 12:29 PM, Schults, Chris wrote:
> 1) I check out and edit the existing templates, and preview content as
> necessary -- everyone else goes about their normal business. However,
> this would mean I'm the only one who could generate a web page with
> the
> new design, which could be overwritten by someone else burning the
> same
> story.
If you're not making major changes, I'd go with this.
> 2) Create a new output channel that doesn't publish to the production
> site, add this output channel to all relevant stories, create new
> templates under this output channel and deploy them when ready to
> review
> so that any user can use them. I assume the URI format for this new
> output channel would have to be such that a story's URI is unique,
> like
> /new-design/%{categories}/. (But this seems like it would cause
> linking
> problems.) Then, when it is time to launch, edit the URI format,
> remove
> the old output channel, and republish the site.
You can let the URI format be the same; a given story can have the
same URI in more than one OC. I did this for The Tyee. It was a bit of
a PITA, but it did work. The migration was tough, but if you keep
careful track of what new templates replace what old ones, you can do
it. Just associate the develoment OC with "Enabled" unchecked, so that
users don't get errors when they publish stories for which you haven't
yet developed a new template in the new OC.
Another option is to clone the installation, install it on a new box
(or vm or whatever), and do your development there.
HTH,
Daivd
|
smime.p7s
