-
Notifications
You must be signed in to change notification settings - Fork 12
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
✨ NEW: Add RTD site #33
Conversation
Because why not!
Nice. Should we maybe put the doc-specific files in a |
Ah but then I believe you would have to put all the documentation under the |
There you go: https://aep--33.org.readthedocs.build/en/33/ |
All done on my end. |
Would be good to add this to the steps for submitting an AEP in AEP 000. |
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.
Thanks @chrisjsewell !
Should we maybe put the doc-specific files in a docs sub directory to keep root from getting to cluttered?
Ah but then I believe you would have to put all the documentation under the docs directory, which is obviously everything in the repository lol
I would also have preferred that but if there's no way to do a ../
there, it's ok with me.
root: README.md | ||
subtrees: | ||
- caption: Proposals | ||
entries: |
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.
There's no way to automate this, right?
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.
nope, not currently
Because why not!
submitted
README.md