-
Notifications
You must be signed in to change notification settings - Fork 3
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
Set up Read the Docs/Hugo site for RAM resources #48
Comments
Ooo wondering if @aranas has thoughts on this bc she's looking into similar resources for clim-recal docs - alan-turing-institute/clim-recal#42 (comment) |
I can help with this if you'd like... But I think you'd might want to go with MkDocs rather than Sphinx if we're working with markdown files, since the latter uses RST (Restructured Text) format, which is slightly different from markdown. You can use markdown in Sphinx as well, but it's not the native language. IMHO, MkDocs is much more user-friendly and fitting for a first project like this! |
Yes, I wanted to eventually use MkDocs for clim-recal as well, as Chris had recommended. @kallewesterling have you used it before and would be willing to give us a mini-workshop :)? |
Yeah, sure! |
@harisood let me know what you think - and if this aligns with what you had thought of! |
yeah exactly right! Down for a mini workshop too |
I forgot to reply to this @aranas -- yes, I did work with MkDocs intensely about 2 years ago on this site. (see repo here: https://github.com/kallewesterling/django-app-documentation). I'm sure there are new features etc but happy to read up on those. |
100% to mini workshop! Noting that specifically for the task described in this issue we should discuss how this site would add additional value vs. 1) existing documentation in TTW 2) documenting in this Github repo |
Ooops! This mini workshop has completely dropped off my schedule. I could schedule one in for Dec 8 if folks are still interested? Let me know @dingaaling @aranas @harisood ! |
Somehow I missed this whole discussion the first time but I’m very interested, Dec 8 sounds great! |
wfm! |
OK, I'll prepare something and keep you all in the loop! |
I assume that all are familiar with Markdown. I'm not, however, sure that you all have a full Python setup on your laptop. That's why I've provided some clear, concise instructions for the initial setup. It will ensure that all of you are is ready to dive into MkDocs during Dec 8. Pre-Workshop Setup1. Visual Studio Code (VS Code) InstallationIf you haven't already, please download and install VS Code from https://code.visualstudio.com/. Familiarize yourself with VS Code's basic features here. 2. Python InstallationMkDocs requires Python. If you don't have Python installed, download and install Python 3 from https://www.python.org/downloads/. During installation, ensure you select the option to 'Add Python to PATH'. If you run into any problem, just feel free to send me a message on Slack. 3. MkDocs InstallationOpen VS Code's integrated terminal (from the "View" menu, select "Terminal"). Run the command: To confirm the installation, type Create a Sample MkDocs ProjectIn the terminal, navigate to a directory where you want to create your test project. Then run Explore the generated Additional resources that you may want to explore before we get started
|
Summary
J a thought I have, a way to render any MarkDown resources we create in a bit more of a professional way, e.g. as done with SATRE.
A skill I kinda want to learn too and may be useful for RAMs to pick up!
What needs to be done?
Who can help?
Updates
The text was updated successfully, but these errors were encountered: