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

Official Documentation #581

Closed
14 tasks done
daniel-farina opened this issue Nov 10, 2021 · 2 comments
Closed
14 tasks done

Official Documentation #581

daniel-farina opened this issue Nov 10, 2021 · 2 comments
Assignees
Labels
C:docs Improvements or additions to documentation

Comments

@daniel-farina
Copy link
Contributor

daniel-farina commented Nov 10, 2021

I'm starting this issue to track the best way to create the official documentation for Osmosis. Ideally, I think all documentation should live inside a /docs folders inside the main osmosis repo. If you were to clone the repo, all docs are right in there. No dependencies. I believe Tendermint does this with vue-press but we could look into other alternatives.

Recent Updates

First POC is live. We made a fork of the main Osmosis repo for now. We will create a PR once we are close to finalizing the docs branch.

Contributors

@daniel-farina
@czarcas7ic

Todo

@ValarDragon @sunnya97 Please let us know if you have any questions or concern about the proposed documentation site.

We are tracking this documentation effort here:
https://github.com/orgs/osmosis-labs/projects/1/views/10

Thanks!

@daniel-farina daniel-farina added the C:docs Improvements or additions to documentation label Nov 10, 2021
@daniel-farina daniel-farina self-assigned this Nov 10, 2021
@daniel-farina
Copy link
Contributor Author

I started the process of moving ALL known documentation from Gitbooks & and Github into a single Vuepress documentation folder. This will be 100% Markdown living inside a repo (The main Osmosis chain repo for example) which then could be served from docs.osmosis.zone. I created a blank vue-press site from scratch so that the front-end team can customize anyway they wish. This will allow us to have a coherent place where all documentation lives as well as a place for the open source community to make changes via pull requests. I will finish up a concept/poc and then share it with the team to do a review and approval.
This is the same way Tendermint & Cosmos writes documentation. Gitbook is nice but it’s not open source and less community driven. I'll keep this issue updated.

Suggestions are welcomed!

@czarcas7ic
Copy link
Member

A lot of our focus is going to be both completing incomplete and/or incorrect documentation as well as splitting technical and non technical knowledge articles as to not overwhelm newcomers. Let us know if you agree with the intent/vision for the product.

@daniel-farina daniel-farina mentioned this issue Nov 21, 2021
4 tasks
@daniel-farina daniel-farina added this to the 2021 - December Milestone milestone Nov 30, 2021
@daniel-farina daniel-farina removed this from the 2021-12 Milestone milestone Dec 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:docs Improvements or additions to documentation
Projects
Archived in project
Development

No branches or pull requests

2 participants