Re: Moved a chapter from Sphinx to plone.org developer-manual: experiences and feedback
Israel Saeta Pérez <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Mikko Ohtamaa wrote: > > Few rationales: > > - Code examples: Managing tab and whitespace is difficult in WYSIWYG > editors. You basically need to use external editor to create the > snippet and then copy-paste it into Plone. Because you know writing > code example is so difficult to have you tend to avoid doing them. > ... > > Looks like this sphinx-or-plone discussion will never end. :P I know Mikko doesn't want to work on anything which is not open for everybody and the current developer-manual in the Plone.org manual section is not going to be so open, so I propose: 1) Keep the manual section in Plone with TTW editing. We can add TinyMCE, regular autosave, bespin or whatever we want to ease the editing work. The Knowledgebase can also benefit from all this stuff. 2) Find a way to publish the collective.developermanual in Sphinx as part of the Knowledgebase at Plone.org. Dylan is already working on this, right? Everybody with collective access would be able to edit it, so it would be quite open. Moreover, the documentation is already in the package so we wouldn't have to move anything. Thoughts? -- israel ----- Israel Saeta Pérez -- View this message in context: http://n2.nabble.com/Moved-a-chapter-from-Sphinx-to-plone-org-developer-manual-experiences-and-feedback-tp4157870p4160131.html Sent from the Documentation Team mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Plone-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-docs