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

fix(mkdocs): structure according best practices #442

Merged
merged 2 commits into from
May 9, 2024

Conversation

zzehring
Copy link
Contributor

@zzehring zzehring commented May 9, 2024

This change structures mkdocs according to their recommended file layout. This moves mkdocs.yml to the root of the project, alongside the docs/ directory.

Also, update the catalog-info.yml's backstage.io/techdocs-ref annotation to .. Backstage strongly recommends techdocs-ref annotation to be set to dir:. in almost all situations.

This change structures mkdocs according to their [recommended file
layout][mkdocs-file-layout]. This moves `mkdocs.yml` to the root of the
project, alongside the `docs/` directory.

Also, update the `catalog-info.yml`'s `backstage.io/techdocs-ref`
annotation to `.`. Backstage [strongly recommends `techdocs-ref`
annotation to be set to `dir:.` in almost all
situations][backstage-techdocs-ref].

[mkdocs-file-layout]: https://www.mkdocs.org/user-guide/writing-your-docs/#file-layout
[backstage-techdocs-ref]: https://backstage.io/docs/features/techdocs/how-to-guides/#how-to-understand-techdocs-ref-annotation-values
@zzehring zzehring requested a review from a team as a code owner May 9, 2024 16:24
@julienduchesne
Copy link
Member

Heh, exactly my PR: #441

@julienduchesne
Copy link
Member

Can you fix the refs in the workflow file like I did in here: #441

@zzehring
Copy link
Contributor Author

zzehring commented May 9, 2024

Can you fix the refs in the workflow file like I did in here: #441

Oh yea good catch! Will do.

This should now be run in the root rather than inside the `docs/` dir.
Also update paths for when workflow should run.
Also fix comment for serving mkdocs locally
@zzehring zzehring force-pushed the zzehring/docs/fix-structure-for-mkdocs branch from be282cd to 74d3d39 Compare May 9, 2024 16:43
Copy link
Member

@julienduchesne julienduchesne left a comment

Choose a reason for hiding this comment

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

:shipit:

@julienduchesne julienduchesne merged commit 4dc308b into main May 9, 2024
7 checks passed
@julienduchesne julienduchesne deleted the zzehring/docs/fix-structure-for-mkdocs branch May 9, 2024 16:44
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.

3 participants