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

docs: Updates to landing pages and minor edits #26

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

AshleyCliff
Copy link
Contributor

Updated the landing page descriptions for how-to and explanation, removed empty tutorial page for time being, updated homepage to reflect new content, and made some minor edits to the README and Contributing docs.

@AshleyCliff AshleyCliff added the documentation Improvements or additions to documentation label Jan 31, 2025
@AshleyCliff AshleyCliff requested a review from a team as a code owner January 31, 2025 21:58
@AshleyCliff AshleyCliff requested review from NucciTheBoss and removed request for a team January 31, 2025 21:58
Copy link
Member

@NucciTheBoss NucciTheBoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, looks good.

I'd challenge removing the emojiis from the section headers given that it breaks the visual consistency with our other project READMEs. I don't think the emojiis are bad, and other community groups like the Rockcrafters use them in READMEs, but exclude them from the official rockcraft documentation.

A lot of projects on the awesome-readme collection use them as well. They can helps with engagement on GitHub, specifically. Here's one big project's README for example: https://github.com/gofiber/fiber#readme

Let me know your thoughts here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's an issue for us to use emojiis here since READMEs are more meant for developers (us and the other Charmed HPC developers) than it is for potential customers. For example, the Rockcraft community uses emojiis sparingly in their community README: https://github.com/rockcrafters

I don't think it hurts to have them in the README, but they should largely be kept out of the actual documentation. I'm mostly hung up about their removal since it makes the docs repo visually inconsistent with our other repositories.


🚧 WIP 🚧
Periodically, issues within the docs repository will be labeled as 'Good First Issues'. These issues are ideally the first place to get started helping with the Charmed HPC documentation. If there are currently no 'Good First Issues' or none that fit your interest, feel free to reach out on Matrix and ask if the team has any suggestions. Otherwise, small PRs for grammar and formatting are always a good place to start.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple suggested revisions here. Big thing is changing it from 'Good First Issues' to good first issue since that how our new issue labels are styled:

Suggested change
Periodically, issues within the docs repository will be labeled as 'Good First Issues'. These issues are ideally the first place to get started helping with the Charmed HPC documentation. If there are currently no 'Good First Issues' or none that fit your interest, feel free to reach out on Matrix and ask if the team has any suggestions. Otherwise, small PRs for grammar and formatting are always a good place to start.
Periodically, issues within the docs repository will be labeled as `good first issue`. These issues are ideally the first place to get started helping with Charmed HPC's documentation. If there are currently no issues labeled `good first issue`, or none of the issues fit your interest, feel free to reach out on [Matrix](https://matrix.to/#/#hpc:ubuntu.com) and ask if the team has any suggestions. Otherwise, small PRs for grammar and formatting are always a good place to start.


For more information on how to access or contribute to Charmed HPC's
documentation, check out the [Getting Started](#-getting-started) and
[Development](#️-development) sections below 👇
[Development](#️-development) sections below.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll give you this one... the 👇 isn't necessary 🤣


Use the following command to start the development server and see your
documentation changes render in real time:
To start the development server and render a local preview run:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[comment]: More succinct; I like it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants