-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create docs on docs.plone.org for this image #46
Comments
To clarify, the only docs I see in this repo are in Does in-depth information exist somewhere? If so, where? As far as where in-depth docs of backend should go, anyone can create a pull request against the |
I think we need some kind of deployment documentation, so there will be. |
we have the deployment training now, this can be closed |
No, Training is not the authoritative source for Documentation. We maintain Documentation all the time now, whereas a Training is usually only updated by the author. Additionally we do not want to punish users to go between two websites to get the information they seek. Please reopen. |
I will change the ticket title |
@jensens for some reason, I cannot assign this ticket to myself or add it to the Plone 6 Docs release GitHub Project. I could not reopen the ticket myself yesterday either. Would you please check my permissions on this repository, and grant me sufficient rights? Thank you! After I have the opportunity to run through the training and provide feedback in a couple of weeks, then I'll work on this ticket. |
@stevepiercy indeed, Developers group had only read access. @ericof by intend? Anyway, I change this to "Triage". |
@jensens thanks. Assigned and added to the GitHub project Release Plone 6 docs. |
The README here lands on Docker Hub, so it should contain basic about the image and Plone.
In depth information has to be moved to docs.plone.org (6-dev branch)
@stevepiercy knows better where to put it there. Lets keep this issue open until this is finished.
The text was updated successfully, but these errors were encountered: