Re: Plone 3.2 User Manual Update

Hmm... could the prose of the user manual contain hooks in hidden comments
in an unobtrusive way (invisible to editors)?

Jeff

Jeff Pittman
http://www.geojeff.org


On Sat, Dec 20, 2008 at 1:29 PM, Jeff Pittman <[email protected]> wrote:

> Yes, keeping the editable prose in Plone is the way to go -- sorry to have
> suggested svn for this.
>
> For developing a system of updating the screen captures and other
> analytical/update work done independently on the user manual -- independent
> of the standard prose editing in place on plone.org -- the html of the
> prose could be grabbed over the top with a scrape, or via a custom script on
> plone.org.  A python/filesystem approach could be developed in parallel
> for doing the automation by parsing the html/restructured text.  A parallel
> html version of the user manual could be rendered on the desktop for
> inspection as you work on the screen captures, and fresh images/media could
> be uploaded in bulk when done.
>
> Jeff
>
> Jeff Pittman
> http://www.geojeff.org
>
>
> On Sat, Dec 20, 2008 at 12:41 PM, Steve McMahon <[email protected]> wrote:
>
>> Automating the screenshots is totally cool. It's the editable prose
>> that we'd like to keep inside the CMS, where it can be worked on by
>> prose writers who aren't necessarily comfortable with svn and
>> particular markup schemes.
>>
>> On Sat, Dec 20, 2008 at 10:31 AM, Jeff Pittman <[email protected]>
>> wrote:
>> > The screen capture facility would be accomplished, I imagine, with a
>> driver
>> > script operating on hooks (special codes) in the docs to drive the
>> browser
>> > and captures -- or such a script developed in parallel.
>> >
>> > Regarding complication of such a system, having a driver system in
>> python is
>> > not a bad thing -- we are a python house, ultimately. :)
>> >
>> > And, I wouldn't want us to shy away from innovation.  Such an approach
>> > inherently requires an intelligent system, for which we are fully
>> capable of
>> > designing and maintaining.  It would be like other complicated python
>> > scripts I use on the command line -- a chore to build, but once they
>> work,
>> > they become workhorse utilities.
>> >
>> > Jeff
>> >
>> > Jeff Pittman
>> > http://www.geojeff.org
>> >
>> >
>> > On Sat, Dec 20, 2008 at 12:18 PM, JoAnna Springsteen <[email protected]
>> >
>> > wrote:
>> >>
>> >> On Sat, Dec 20, 2008 at 11:38 AM, Jeff Pittman <[email protected]>
>> >> wrote:
>> >> > Also, at a recent sprint, there was an exploration of automation for
>> >> > screen
>> >> > captures for the user manual and other documentation needs.
>> >>
>> >> Yup. Seems like we've been talking about this since the PSU symposium.
>> >> I know Paul Everitt had thoughts on how this could be done too.
>> >> Not sure if anything ever came of it though.
>> >> Would still be interested in hearing how we could accomplish this
>> >> without making it hugely complicated.
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Plone-docs mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/plone-docs
>> >
>> >
>>
>>
>>
>> --
>>
>> Steve McMahon
>> Reid-McMahon, LLC
>> steve-HR5nRXif9uVv8oa/[email protected]
>> [email protected]
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Plone-docs mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/plone-docs
>>
>
>

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

_______________________________________________
Plone-docs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-docs