On Sat, Dec 26, 2015 at 4:14 AM, David H <[email protected]> wrote:
> 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. > I'd second this, as it is the main way to use Sphinx. It also works quite well in the sense of writing RST code can be done even directly in a web-browser with the help of GIT web interfaces. This way you allow mostly everyone to edit pages, but you have an approval process for free via the Pull Requests mechanism. It also makes it very easy to : * mass edit files * validate links offline * automatically regenerate some reference pages > Just a thought, maybe it fits your situation, maybe not. > I agree that it only works well when the amount of modifications is quite small as manual validation of all the edits are mandatory. A group of users could be handled the right to merge and do direct modifications. It is also the way that many OpenSource projects do handle their documentation. -- Steve Schnepp -- 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.
