[GH-ISSUE #232] Lacking documentation and wiki #82

Closed
opened 2026-03-16 13:16:08 +03:00 by kerem · 6 comments
Owner

Originally created by @liyasthomas on GitHub (Oct 30, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/232

Originally assigned to: @liyasthomas, @NBTX on GitHub.

Is your feature request related to a problem? Please describe.
Accept the fact that postwoman.io have zero docs and wiki 😞

Describe the solution you'd like
Make the wiki, write the docs: https://github.com/liyasthomas/postwoman/wiki

Describe alternatives you've considered
Host docs on postwoman.io itself.

Additional context
Wiki is essential while adding new features, making any changes breaking changes, updating format/features etc.

Originally created by @liyasthomas on GitHub (Oct 30, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/232 Originally assigned to: @liyasthomas, @NBTX on GitHub. **Is your feature request related to a problem? Please describe.** Accept the fact that postwoman.io have zero docs and wiki 😞 **Describe the solution you'd like** Make the wiki, write the docs: https://github.com/liyasthomas/postwoman/wiki **Describe alternatives you've considered** Host docs on postwoman.io itself. **Additional context** Wiki is essential while adding new features, making any changes breaking changes, updating format/features etc.
Author
Owner

@nickpalenchar commented on GitHub (Oct 30, 2019):

I was just thinking about this. Don't want to add complexity too quickly, but gitbooks seem to produce great documentation. I need to do some research but I believe they can be hosted from a docs/ directory in github, and would be a part of VCS along the rest of the codebase (not to mention documentation edits would be a green square for a contributors github profile 😎 )

Of course just starting to write anything in the github wiki is easy for every/anyone to do, and could easily be moved over to gitbook later as it's all markdown

<!-- gh-comment-id:548133197 --> @nickpalenchar commented on GitHub (Oct 30, 2019): I was just thinking about this. Don't want to add complexity too quickly, but [gitbooks](https://www.npmjs.com/package/gitbook) seem to produce great documentation. I need to do some research but I believe they can be hosted from a `docs/` directory in github, and would be a part of VCS along the rest of the codebase (not to mention documentation edits would be a green square for a contributors github profile 😎 ) Of course just starting to write anything in the github wiki is easy for every/anyone to do, and could easily be moved over to gitbook later as it's all markdown
Author
Owner

@NBTX commented on GitHub (Oct 30, 2019):

You can use GitHub pages and that will work from a specific branch or a docs/ directory. But to add, another perk of GitHub pages would be that we could theme it as we please.

I definitely think we should use the GitHub Wiki as a draft for the docs.

<!-- gh-comment-id:548133738 --> @NBTX commented on GitHub (Oct 30, 2019): You can use GitHub pages and that will work from a specific branch or a docs/ directory. But to add, another perk of GitHub pages would be that we could theme it as we please. I definitely think we should use the GitHub Wiki as a draft for the docs.
Author
Owner

@liyasthomas commented on GitHub (Oct 31, 2019):

Will wirte Github Wiki first.

GitBook for build ✔️
GitHub pages for hosting ✔️

<!-- gh-comment-id:548161624 --> @liyasthomas commented on GitHub (Oct 31, 2019): Will wirte Github Wiki first. GitBook for build ✔️ GitHub pages for hosting ✔️
Author
Owner

@yubathom commented on GitHub (Oct 31, 2019):

This would be nice!

Maybe a vue based doc builder should be considered. I use vuepress for documentation and I think it is awesome. A helpful feature is the capability of it to load vue components in docs markdown. But agree that wiki is certainly a good start.

<!-- gh-comment-id:548202066 --> @yubathom commented on GitHub (Oct 31, 2019): This would be nice! Maybe a vue based doc builder should be considered. I use vuepress for documentation and I think it is awesome. A helpful feature is the capability of it to [load vue components in docs markdown](https://vuepress.vuejs.org/guide/using-vue.html#using-components). But agree that wiki is certainly a good start.
Author
Owner

@liyasthomas commented on GitHub (Oct 31, 2019):

How about we add a help [?] button on sections with link to its corresponding wiki pages as I finish docs.

<!-- gh-comment-id:548329404 --> @liyasthomas commented on GitHub (Oct 31, 2019): How about we add a help **[?]** button on sections with link to its corresponding wiki pages as I finish docs.
Author
Owner

@sabatesduran commented on GitHub (Nov 6, 2019):

I know you are using Firebase, but have you tried Netlify? Now with every commit you can build multiple sites 😄 (For free)

<!-- gh-comment-id:550392732 --> @sabatesduran commented on GitHub (Nov 6, 2019): I know you are using Firebase, but have you tried Netlify? Now with every commit you can build multiple sites :smile: (For free)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#82
No description provided.