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

Reorganize docs with Diataxis method #2597

Closed
thomas-bc opened this issue Mar 16, 2024 · 9 comments
Closed

Reorganize docs with Diataxis method #2597

thomas-bc opened this issue Mar 16, 2024 · 9 comments
Assignees
Labels
Documentation Documentation, Tutorials and References updates Easy First Issue An issue that should be straight forward to implement, and easily tested via CI. help wanted High Priority High Priority issue that needs to be resolved.

Comments

@thomas-bc
Copy link
Collaborator

thomas-bc commented Mar 16, 2024

Description

See https://diataxis.fr/

Now that we have a HowTo Guide section, I think it would be really great for navigation and understandability if we reorganized our documentation this way. 4 categories:

  • Tutorials
  • Explanation (this is probably most of our current "User Guide", we could keep it named this way)
  • How To Guides
  • Reference (API docs, maybe links to SDDs? etc...)

I've seen this method pop up more and more and I think it's really great.

@thomas-bc thomas-bc added the Documentation Documentation, Tutorials and References updates label Mar 16, 2024
@thomas-bc
Copy link
Collaborator Author

Realistically, this could simply be taking the API section out of the User Guide and into a new Reference section in the sidebar/TOC, and grouping Design and Philosophy section in a top level section of the User Guide.

Maybe also double check that things in the User Guide don't belong to another (HowTo or Reference) section.

@thomas-bc thomas-bc added help wanted Easy First Issue An issue that should be straight forward to implement, and easily tested via CI. labels Mar 20, 2024
@GavinKnudsen
Copy link
Contributor

Would it be alright if I take a crack at this? It would be my first issue in this project. Thanks!

@thomas-bc
Copy link
Collaborator Author

Yes please that would be great! Let me know if you have any questions or need anything

@LeStarch LeStarch added the High Priority High Priority issue that needs to be resolved. label Mar 27, 2024
@GavinKnudsen
Copy link
Contributor

@thomas-bc Thanks. I have done some looking around the current documentation and had a question. Would it make sense to move the "getting started with F'" content under the "Getting Started" section? My my thought process is we can have the four categories that you mentioned, but also have a kind of "Start here" section that includes how to read the documentation, the basics of F', and/or how to get started all consolidated into one section where it is easy for new learners to know where and how to start. Should this section be included in the 4 categories as well? What are your thoughts?

@thomas-bc
Copy link
Collaborator Author

thomas-bc commented Mar 29, 2024

Yes I think that would make sense! Feel free to clean that section up as well since one of the link is the landing page and another one is the tutorials which are already referenced in the sidebar.
Also maybe move the Console autocomplete thing under the GDS part of the User Guide as this isn't really relevant to "get started"

@thomas-bc
Copy link
Collaborator Author

Also this link here

<h4><a href="/fprime/Design/general.html">How-To Guides</a></h4>

should be changed to link to /fprime/HowTo/general.html instead

@Saty70
Copy link

Saty70 commented May 1, 2024

hey i want to contribute on this issue can you guide me what should be prequisite needed to know to do so as i am new to open source contribution

@GavinKnudsen
Copy link
Contributor

Sorry I've been inactive for a while and thank you for your patience! I've been busy with school, but now that my semester has ended, I have more time to work on this project. I'm aiming to submit a pull request by Monday evening, assuming there are no unforeseen issues.

@Saty70, for the prerequisites for this issue, you should be familiar with markup languages such as HTML and review the diataxis documentation method. Additionally, I recommend checking the project's contributing guidelines and documentation to help you get started.

This is my first contribution to this project as well, and I am not a maintainer, but I would still be happy to guide you if you have any questions. If you decide to work on a different issue, please feel free to explore the easy first issues list.

Thank you for understanding, and let me know if you have any questions.

@Saty70
Copy link

Saty70 commented May 4, 2024

Thanks @GavinKnudsen for guiding really helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Documentation, Tutorials and References updates Easy First Issue An issue that should be straight forward to implement, and easily tested via CI. help wanted High Priority High Priority issue that needs to be resolved.
Projects
None yet
Development

No branches or pull requests

5 participants