People have been suggesting you use a wiki so that you get ACLs. But do you really need people to edit your web pages inside of a web browser?
Do you want access privileges to control who can edit your pages, or is it mostly to control who can view your pages? The reason why I ask is this: If only a few, technically advanced people need to edit your pages, you still could use Sphinx to publish them, and get the viewing access privileges enforced by the web server that serves up the published pages. Use a source control system like git for collaborative editing, just like you do for program source code. Then publish the static web pages to be served by a regular web server like Apache, and use that web server's access control features to control who can see the web pages. For example, Apache can require authentication for all pages underneath a certain URL. Just a thought, maybe it fits your situation, maybe not. On Monday, December 21, 2015 at 6:06:35 AM UTC-5, Renato Pontefice wrote: > > Hi, yes this answer help me a lot. > They let me understand, that spinx is not the solution :-) > > So, what I can look about a solution for my prob? > I mean: > - build a centralized store of doc (it could be a wiki,but any sudgestion > are welcome) with privilege access > - writing doc in RST format > - export the same base of doc in different format (i.e. one format to use > as a book, one format to use as a wiki ...) > > are that info enought? > > Renato > > > Il giorno venerdì 18 dicembre 2015 16:24:49 UTC+1, David H ha scritto: >> >> Answers to your questions: >> >> 1. Yes, Sphinx is open source software. It's source code is available on >> Github here: https://github.com/sphinx-doc/sphinx >> 2. No, Sphinx does not create wiki output. It creates static HTML output, >> that can be easily published to a website. >> 3. No, once Sphinx creates the HTML output, it doesn't give you the >> ability to create access control lists with privileges. >> >> Sphinx and Wikis are two different, opposing ways to manage content on a >> website. WIth a wiki someone can log in and edit the page in their web >> browser. With Sphinx, you edit the source text files of the web site using >> a text editor, then run a Sphinx command to re-build the HTML files, then >> you copy those files to your website. You can do collaborative editing of >> the files in the same way you would edit code, using source control tools >> such as git or mercurial, etc. >> >> I hope this helps - >> David H >> >> On Friday, December 18, 2015 at 5:27:59 AM UTC-5, Renato Pontefice wrote: >>> >>> Hi, >>> I need to find a solution, for the documentation on my company. >>> We develop and distribuite a java sw >>> is a big project. We need to unify the doc and give a centralized repo >>> of it. >>> I have been instructed to find a solution. >>> I think, I've found it in sphinx. >>> I'd like to post some question, before start to use it: >>> 1 - is it Open source sw? This, because we release our sw under that >>> license >>> 2 - I've understand that I can create my doc, using rst syntax, and then >>> render it in the format i prefer. Can I deliver it on a web plattform as >>> wiki? (I'm thinking at moin moin wiki, but also the sphinx web site seem to >>> have the same requirement.) >>> 3 - if answer of letter 2 is "yes", can I create more user access with >>> different privilege ? >>> >>> That info are enought for me to start using it. >>> eventualy, later, I will ask for more info. >>> >>> TIA >>> >>> Renato >>> >> -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
