That might work. Are you able to specify multiple versions?<br><br>-Justin<br><br><div class="gmail_quote">On Fri, Mar 7, 2008 at 7:39 PM, Tim Knapp <<a href="mailto:duffyd@kokorice.org">duffyd@kokorice.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Martijn/Justin et al,<br>
<br>
Just a thought, in previous version of PHC you could specify a relevant<br>
Plone version that the document applies to (hopefully this feature is<br>
still there). Couldn't we just repurpose this feature for Grok?<br>
<br>
HTH,<br>
<font color="#888888">Tim<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Fri, 2008-03-07 at 17:49 +0100, Martijn Faassen wrote:<br>
> Hey Justin,<br>
><br>
> Thanks for your comment on the documentation, I think that's a valuable<br>
> point.<br>
><br>
> We need to see how to organize the website to do this. I'm looking at<br>
> Kevin Teague now for advice on whether plone help center would allow<br>
> such a thing.<br>
><br>
> The way we could work is to have the documentation in the present<br>
> location always reflect the most recent release.<br>
><br>
> Then, as we make a release, we copy all that documentation into its own<br>
> section named after the release. The hardest part will be to fix up all<br>
> the internally pointing URLs to be consistent...<br>
><br>
> This way, we could keep a record of the state of the documentation at<br>
> release. We need to couple this with clear guidelines concerning the<br>
> main flow of documentation: it should only contain documents relevant to<br>
> the most recent release, and not anything that won't work anymore or not<br>
> yet.<br>
><br>
> There is a need to develop documentation ahead of time for a new<br>
> release. This could be done in SVN trunk, or in some special area on the<br>
> website. Upon release, *before* we shift the documentation off into its<br>
> own section, we should integrate all this into the main section.<br>
><br>
> There is enough to watch and work out here to need someone who shepherds<br>
> this process. Without a plausible volunteer I don't think we have enough<br>
> resources to afford this right now. Instead we should then just focus on<br>
> maintaining the current set of documentation to be up to date.<br>
><br>
> Regards,<br>
><br>
> Martijn<br>
><br>
> _______________________________________________<br>
> Grok-dev mailing list<br>
> <a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
> <a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</div></div></blockquote></div><br>