-
Notifications
You must be signed in to change notification settings - Fork 11
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
Changed entire website to Markdown + new link checker #679
Conversation
|
docs/community_resources/workshops_events_archive/access_workshop_2023/training_materials.md
Show resolved
Hide resolved
Multiple environment variables are separated by a comma (_,_). | ||
|
||
- **Jobfs size**<br> | ||
The maximum amount of local disk available to the session.<br> |
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.
Edit: replace "to the session" with "for the session"
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.
That is the original jobfs description on the ARE website
You can delete a session before its automatic expiration (based on the specified [Walltime](#walltime-option) by clicking on the session's ![Session Delete button](/assets/session_delete_button.png){: style="height:1em"} button in the [Interactive Sessions](https://are.nci.org.au/pun/sys/dashboard/batch_connect/sessions) page. |
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.
Edit: replace 'before its automatic expiration...' with "before it automatically expires..."
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 prefer its automatic expiration here. Is there any particular reason why you make your suggestion?
Thanks for the speedy and review @heidinett! |
Fixed lychee config file path test testing link checker testing link checker testing link checker testing link checker testing link checker testing link checker testing link checker testing link checker testing link checker testing link checker
… of the 'community_med' folder as will be reviewed later with the MED review
…erences tag to render references.
…Created custom HTML tag for the simulated terminal info admonition
… and docs/community_resources/community_med folders
Fix link to section in README Updated README Updated README Updated README Updated README Updated README Updated README Updated README Updated README
…erminal info admonitions to pages with simulated terminals. Updated REAMDE Minor edit to custom-not-supported tag
Updated README adding reviews
Adding Heidi's reviews Updating branch with latest updates from old branch
ced4256
to
5b044ce
Compare
…d scheduled check every Sunday at 3:07am.
Thanks a lot @heidinett, @flicj191 and @KAUR1984 for the reviews! |
This is another very big PR, where the following changes have been made:
All syntax changed to Markdown (where possible)
Some exceptions are cards, references (more on this below), simulated terminals, content tabs (for example the one used for different versions of ACCESS-OM2).
The files related to Model Evaluation (inside
docs/model_evaluation
anddocs/community_resources/community_med
were not changed as the syntax of those files will be changed within the extensive MED restructure.New link checker
lychee (more specifically its GitHub action lychee-action) is now used for link checking.
It checks for broken URLs of links and images both with Markdown and HTML syntax.
In the README there is a badge that shows the status of the link checker. Ideally this should always pass. Now it is failing because there are still the MED links to check (as mentioned above).
All internal URLs changed to ABSOLUTE URLs
All internal URLs (links and images) changed to absolute URLs.
Internal URLs need to be ABSOLUTE URLs, starting with
/
which indicates the base website https://access-hive.org.au/ (http://localhost:8000/ when deploying withmkdocs serve
, https://access-hive.org.au/development-website/ for the development website, and https://access-hive.org.au/pr-preview/pr-PRNUM/ for the PR previews).So, a reference to the page
https://access-hive.org.au/models/configurations/access-cm/
will be/models/configurations/access-cm
. Also, all assets need to be linked starting with/assets/...
.This because currently the link checker does not handle relative links properly.
Custom tags
To facilitate the rendering of recurring components, custom tags have been created (in the
js/custom-tags.js
file).Currently, the available custom tags are:
"NOT directly supported by ACCESS-NRI" admonition
The
<custom-not-supported/>
tag renders a preset "NOT directly supported by ACCESS-NRI" admonition (example for community MED page).References
The
<custom-references> ... </custom-references>
tag renders references to be used at the bottom of a page. Each new line (created by pressing return/Enter) inside...
is rendered as a separate bullet point. A hyphen (-
) can included at the beginning of a new line (for clarity) but it is stripped off at the time of rendering (example for How to run ACCESS-CM2 page)..Simulated terminal info
The
<custom-simulated-terminal-info/>
tag renders a preset info admonition on the pages where simulated terminal are used.It should not be used manually as it is automatically added in the pages containing simulated terminals.
README updated
Updated the guidelines for developers in the README.
Other minor modifications
I understand the number of changed files is massive, but in most files content does not change much (only syntax).
What I suggest for the review, apart from looking at the changes themselves, is to compare the PR-preview website to the Development website. Most pages should be exactly the same despite the changes in the syntax.