Re: plone.org has been upgraded! - next steps

> Does that mean these documents will go to the knowledgebase first and we
> will pick and integrate them in manuals later?

What if the script *copies* (rather than *moving*) the contents of
identified how-tos into manual sections, setting the destination "in
progress"?

Then, the how-to can be removed after manual integration. We'll need
to make sure to set a redirect from the source to the destination upon
the completed integration.

On Thu, Jan 1, 2009 at 12:06 PM, Israel Saeta Pérez <[email protected]> wrote:
> On Wed, Dec 31, 2008 at 11:01 PM, Steve McMahon wrote:
>>
>> Just to clarify, my intention is to script the movement of
>> *everything* in how-to and tutorial to the knowledgebase, *except*:
>>
>> 1) Documents that are not published or have no sections specified.
>>
>> 2) Content identified for inclusion in an already-existing manual.
>> That will be turned into a manual section.
>>
>> I may see if we can repurpose new.plone.org (now that the Plone 3
>> switch is done) to test and check the scripted part of the
>> reorganization.
>
> In the case of the development section, there are a lot of documents which
> could be merged with existing manuals or serve as a base for new ones, but
> they need integration work and can't become part of a manual without
> adapting them.
>
> Does that mean these documents will go to the knowledgebase first and we
> will pick and integrate them in manuals later?
>
> -- israel



-- 

Steve McMahon
Reid-McMahon, LLC
steve-HR5nRXif9uVv8oa/[email protected]
[email protected]

------------------------------------------------------------------------------