Skip to content
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

Open
1 task
harisood opened this issue Aug 15, 2023 · 13 comments · May be fixed by #77
Open
1 task

Set up Read the Docs/Hugo site for RAM resources #48

harisood opened this issue Aug 15, 2023 · 13 comments · May be fixed by #77
Assignees

Comments

@harisood
Copy link
Member

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?

  • Setup this repo to render as a readthedocs or similar site

Who can help?


Updates

  • [Replace this sentence to provide a status summary after the issue has been opened. To avoid others from reading through the full thread of comments, please share updates (e.g. decisions taken) regularly.]
@dingaaling
Copy link
Collaborator

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)

@kallewesterling
Copy link
Collaborator

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!

@aranas
Copy link
Collaborator

aranas commented Aug 16, 2023

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 :)?

@kallewesterling
Copy link
Collaborator

Yeah, sure!

@kallewesterling
Copy link
Collaborator

@harisood let me know what you think - and if this aligns with what you had thought of!

@harisood
Copy link
Member Author

yeah exactly right! Down for a mini workshop too

@kallewesterling
Copy link
Collaborator

kallewesterling commented Aug 16, 2023

@kallewesterling have you used it before and would be willing to give us a mini-workshop :)?

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.

@dingaaling
Copy link
Collaborator

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

@kallewesterling
Copy link
Collaborator

kallewesterling commented Nov 23, 2023

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 !

@kallewesterling kallewesterling moved this from Backlog to In Progress in RAM Nov 23, 2023
@aldenc
Copy link
Collaborator

aldenc commented Nov 23, 2023

Somehow I missed this whole discussion the first time but I’m very interested, Dec 8 sounds great!

@harisood
Copy link
Member Author

wfm!

@kallewesterling
Copy link
Collaborator

OK, I'll prepare something and keep you all in the loop!

@kallewesterling
Copy link
Collaborator

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 Setup

1. Visual Studio Code (VS Code) Installation

If 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 Installation

MkDocs 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 Installation

Open VS Code's integrated terminal (from the "View" menu, select "Terminal").

Run the command: pip install mkdocs.

To confirm the installation, type mkdocs --version.

Create a Sample MkDocs Project

In the terminal, navigate to a directory where you want to create your test project. Then run mkdocs new test-project to create our little test set up.

Explore the generated test-project directory and familiarize yourself with its structure.

Additional resources that you may want to explore before we get started

@dingaaling dingaaling moved this from In Progress to Backlog in RAM Dec 4, 2023
@kallewesterling kallewesterling changed the title Read the Docs site for RAM resources? Read the Docs/Hugo site for RAM resources? Feb 27, 2024
@kallewesterling kallewesterling changed the title Read the Docs/Hugo site for RAM resources? Set up Read the Docs/Hugo site for RAM resources Feb 27, 2024
@kallewesterling kallewesterling self-assigned this Feb 27, 2024
@kallewesterling kallewesterling linked a pull request Feb 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Status: Backlog
Development

Successfully merging a pull request may close this issue.

5 participants