-
Notifications
You must be signed in to change notification settings - Fork 37
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
docs: user documentation on github pages #195
Conversation
This PR is so big! Please, split it 😊 |
Codecov Report
@@ Coverage Diff @@
## main #195 +/- ##
=======================================
Coverage 55.81% 55.81%
=======================================
Files 44 44
Lines 2012 2012
=======================================
Hits 1123 1123
Misses 781 781
Partials 108 108 Continue to review full report at Codecov.
|
If you find any linguistic errors, if you have time for it, just commit to this branch. (around 97% of this is just copy-paste) |
This PR is so big! Please, split it 😊 |
8af36d9
to
3da9eb3
Compare
This PR is so big! Please, split it 😊 |
3da9eb3
to
46e26e0
Compare
This PR is so big! Please, split it 😊 |
@@ -0,0 +1,20 @@ | |||
# Dependencies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No entirely sure about using the top level userdocs/
directory. Personally, I think it should live under docs/
somewhere......but thats just a preference ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to check how others are using docusaurus and I found the Profiles repo as a good candidate to see how they are using it and they have a userdocs in the root. Other (non-weaveworks) public repos are using a website
top level directory.
Other than that, I like the separation of docs/
and the documentation website. This is not a document, it's an entire website and happens to use markdown, mostly, but can use japascript (node) and generate content. That would a bit weird to me if I open the docs directory and a see a lot of js files and markdown files with extra language elements in there (---
header, :::
blocks)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah i take the point about separation.
This is not a document, it's an entire website
Then perhaps website
or site
is more appropriate then?
tags: [release, announcement] | ||
--- | ||
|
||
# v0.1.0-alpha.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that we can have a blog with this 👍
This PR is so big! Please, split it 😊 |
1 similar comment
This PR is so big! Please, split it 😊 |
438dc8c
to
f8c3e4f
Compare
This PR is so big! Please, split it 😊 |
|
||
## Scalar Value Types | ||
|
||
| .proto Type | Notes | C++ | Java | Python | Go | C# | PHP | Ruby | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this table does not render all too nicely, the 2nd from left column is very squished so you get 1 word per line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-generated with protobuf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmmm 😕
sidebar_position: 5 | ||
--- | ||
|
||
# Interacting with the service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could add extra section here about simply building a client using the grpc methods
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sounds more like a "write documentation" than "Initial creation of documentation site"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha okay
This PR is so big! Please, split it 😊 |
3 similar comments
This PR is so big! Please, split it 😊 |
This PR is so big! Please, split it 😊 |
This PR is so big! Please, split it 😊 |
chill out github-action bot! |
This PR is so big! Please, split it 😊 |
Notice: This is more like an initial documentation site * Documentation site is powered by Docusaurus. * gRPC documentation is generated with `protoc-gen-doc`. * Getting started documentation is the as the quick-start guide, but with separate files, so it's easye to navigate and digest the content. It really needs a refactoring and we have to write a real user Getting Started docoument. * Enabled `blog` for now, we can turn it off if we don't want to use it. Created an example blog post about the v0.1.0-alpha.1 release. * CNAME: docs.flintlock.dev Docusaurus: https://docusaurus.io/ protoc-gen-doc: https://github.com/pseudomuto/protoc-gen-doc Fixes #85
* Apply suggestions from code review * Update proto + readme based on feedback * Remove ADR from the footer * Minor doc changes Co-authored-by: Claudia <[email protected]> Co-authored-by: Richard Case <[email protected]>
3173bde
to
ed461d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
happy with this as a starting point
What this PR does / why we need it:
protoc-gen-doc
.with separate files, so it's easye to navigate and digest the content.
It really needs a refactoring and we have to write a real user Getting
Started docoument.
blog
for now, we can turn it off if we don't want to use it.Created an example blog post about the v0.1.0-alpha.1 release.
main
on push.Tools:
Which issue(s) this PR fixes:
Fixes #85
Fixes #194
Special notes for your reviewer:
Notice: This is more like an initial documentation site.
Changed the workflow to run on this branch on push and it was able to deploy the documentation site: 61ef4be
Checklist: