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

Bring documentation into front-end application #648

Open
3 of 4 tasks
chrisdburr opened this issue Nov 8, 2024 · 5 comments
Open
3 of 4 tasks

Bring documentation into front-end application #648

chrisdburr opened this issue Nov 8, 2024 · 5 comments
Assignees

Comments

@chrisdburr
Copy link
Collaborator

chrisdburr commented Nov 8, 2024

User Role

Developer

Goal / Desire

As a developer, I want to implement docusaurus or Astro starlight

Benefit / Reason

So that we can improve the documentation platform by ensuring everything is integrated into one place

Acceptance Criteria

  • Existing structure for documentation is maintained
  • Documentation is stored in markdown files (or MDX), to allow easy editing
  • Similar UI elements to those in Material are preserved
  • When merged to main, documentation is recreated and available on the main site

Additional Notes / Considerations

No response

@RichGriff
Copy link
Collaborator

@chrisdburr here are some screens of the documentation site.

Please note: It didnt work having the sidebar in the bright colour, so i opted to style the navbar. It still uses the same colours and isnt a world apart from the application.

Image
Figure 1: Documentation in light mode with all the same docs in the current main branch

Image
Figure 2: API Documentation in dark mode, I opted to section this off so it would be easy for users to quickly access the api configurations.

@RichGriff RichGriff self-assigned this Dec 9, 2024
@RichGriff
Copy link
Collaborator

"When merged to main, documentation is recreated and available on the main site"

This doesn't matter now. As the documentation is part of the frontend application it will reflect the code for staging and production. So if a doc has been added in staging it will only appear in staging site until that push has been made into production.

@RichGriff
Copy link
Collaborator

@chrisdburr this is now in staging for review

@chrisdburr
Copy link
Collaborator Author

Thanks, @RichGriff.

In general, this looks good. However, there are some issues with callout formatting and some missing images across a number of pages.

How would you like to handle this?

I can do a general review if you open a PR, or I can create a new branch from develop.

@RichGriff
Copy link
Collaborator

Hey @chrisdburr thanks for taking a look.

Probably best to highlight any issues here along with screenshots to support. I think I initially removed some images to prevent build errors when they didn't exist. if you can let me know which pages these are (with a link to the 'old' docs site - even better). I can also look at adding these for you.

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

No branches or pull requests

2 participants