-
Notifications
You must be signed in to change notification settings - Fork 17
✨Add service documentation for the new Community Documentation feature #255
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
base: main
Are you sure you want to change the base?
Conversation
|
||
(learn-authoring)= | ||
|
||
### Learn about authoring with Jupyter Book and MyST Markdown |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to explicitly say "we are only responsible for setting this up, not maintaining it"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. These instructions make it clear that the "community representative" are intended to make the content changes and only bring in 2i2c for configuration changes.
@jmunroe you're away on leave, but I'm assigning you to review this as it's on the services side. Feel free to assign someone else if you think that's the wrong call. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is 'safe to try'!
Part of 2i2c-org/infrastructure#5045, under 2i2c-org/infrastructure#5338