On Sat, 12 Jan 2019 at 14:46, Christer Enfors <[email protected]> wrote:
> Once I've managed to fix this on my own site (so that I'm sure I can at > least do it), I'm more than willing to help update the documentation. I'd > imagine I need to get write access to... something? Where the documentation > is stored? How do I go about acquiring that? > Speaking out of turn here (apologies if I cause offence by butting in!), but: I'd imagine you would fork the mezzanine repo, make the changes you'd like to see in your fork, then submit a pull request on github as is usually the process for submitting changes to projects on github. And to point out further in case this isn't obvious: The documentation for Mezzanine is part of the source code repository. Compare for example the following page from the documentation site ( http://mezzanine.jupo.org/docs/deployment.html and particularly the raw version http://mezzanine.jupo.org/docs/_sources/deployment.rst.txt) with the file in the mezzanine repository on github ( https://github.com/stephenmcd/mezzanine/blob/master/docs/deployment.rst and the raw version https://raw.githubusercontent.com/stephenmcd/mezzanine/master/docs/deployment.rst). As you can see the raw source RST text files are identical. HTH Walter -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
