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: make the README user-friendly #273

Merged
merged 1 commit into from
Apr 1, 2024
Merged

docs: make the README user-friendly #273

merged 1 commit into from
Apr 1, 2024

Conversation

epmog
Copy link
Contributor

@epmog epmog commented Apr 1, 2024

What was the problem/requirement? (What/Why)

We are preparing for the first public release which includes publishing our distribution artifacts to PyPI. The description of the package on PyPI will include the README.md contents of this repository. Any links in the README.md that are relative need to be made absolute since they will not resolve correctly on PyPI. When choosing the absolute link, the link must refer to the correct branch (mainline vs release) depending on the context of the link.

Additionally, once the repository becomes public, visitors will be looking for basic information about the project such as:

  • what is it?
  • what can it be used for?
  • how can it be used and operated?
  • how can people interact with the project?

What was the solution? (How)

  • Wrote it in VSCode with .md rendering
  • view in Github rendering

What is the impact of this change?

Readers landing on our published PyPI and GitHub pages will have a more clear and curated introduction to the project, emphasizing why they might find it important and providing information to help them get started using it and contributing to it.

How was this change tested?

  • Using Visual Studio Code's markdown preview feature
  • Reviewing GitHub's markdown rendered version

Was this change documented?

This change is documentation :)

Is this a breaking change?

No


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@epmog epmog force-pushed the update_readme branch 4 times, most recently from 966023e to a3d8c02 Compare April 1, 2024 09:28
@epmog epmog marked this pull request as ready for review April 1, 2024 09:29
@epmog epmog requested a review from a team as a code owner April 1, 2024 09:29
marofke
marofke previously approved these changes Apr 1, 2024
README.md Show resolved Hide resolved
@epmog epmog force-pushed the update_readme branch 2 times, most recently from 6b8b139 to 6d91b56 Compare April 1, 2024 13:57
moorec-aws
moorec-aws previously approved these changes Apr 1, 2024
ddneilson
ddneilson previously approved these changes Apr 1, 2024
README.md Outdated Show resolved Hide resolved
@epmog epmog dismissed stale reviews from ddneilson and moorec-aws via 5b2601d April 1, 2024 15:16
@ddneilson ddneilson enabled auto-merge (squash) April 1, 2024 15:20
@ddneilson ddneilson merged commit 291dce4 into mainline Apr 1, 2024
18 checks passed
@ddneilson ddneilson deleted the update_readme branch April 1, 2024 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants