Skip to content
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.

feat: Types of documentation #10

Closed
BekahHW opened this issue Dec 15, 2023 · 3 comments
Closed

feat: Types of documentation #10

BekahHW opened this issue Dec 15, 2023 · 3 comments

Comments

@BekahHW
Copy link
Member

BekahHW commented Dec 15, 2023

This kind of overlaps with multiple sections, so I'm happy to take feedback here. But I think there are different types of documentation.

So far, we cover readmes, cocs, contributing files. I think this section can talk about more technical aspects of documentation. We can cover some of the stuff here, but also talk about

  • User Documentation: Guides, tutorials, and FAQs for end-users.
  • API Documentation: Detailed information about the APIs, for developers who want to use or integrate with your project.
  • Developer Documentation: This includes setup guides, contribution guidelines, code of conduct, and development practices, crucial for new contributors.

Documentation should be clear, concise, and accessible to both technical and non-technical users. Avoid jargon and explain complex concepts in simple terms.
Documentation should be kept up-to-date with the latest changes in the project. Outdated documentation can be misleading and frustrating for users and contributors.

@jdwilkin4
Copy link
Contributor

jdwilkin4 commented Dec 19, 2023

I think this is another good article for open source documentation
https://www.cmsdrupal.com/blog/anatomy-great-open-source-documentation-how-document-your-projects-github

As for API documentation, I think covering tools like swagger would be a good option
https://swagger.io/

For the developer documentation, maybe we could focus more on contribution guidelines and development practice because I feel like the other points you mentioned were covered in the setup section.

Thoughts? 😃

@BekahHW
Copy link
Member Author

BekahHW commented Jan 11, 2024

As for API documentation, I think covering tools like swagger would be a good option swagger.io

For the developer documentation, maybe we could focus more on contribution guidelines and development practice because I feel like the other points you mentioned were covered in the setup section.

Thoughts? 😃

Totally agree. The more we write, the more I see overlap in different sections.

@adiati98
Copy link
Member

Is Developer Documentation the same with Community Documentation? Something like what we have in VC handbook and resources?

@BekahHW BekahHW closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants