-
Notifications
You must be signed in to change notification settings - Fork 374
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
chore: trigger docs deploy #1801
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1801 +/- ##
========================================
Coverage 48.25% 48.25%
========================================
Files 408 409 +1
Lines 62338 62515 +177
========================================
+ Hits 30081 30168 +87
- Misses 29749 29824 +75
- Partials 2508 2523 +15 ☔ View full report in Codecov by Sentry. |
.github/workflows/deploy-docs.yml
Outdated
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.
rm netlify.toml
on this repo? :)
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.
+ rm -rf misc/docusaurus
;)
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 don't think we should be removing misc/docusaurus
, at least not until we have a preview deployment of ongoing docs/
or docusaurus
PRs. This is because this is currently the only way to preview how the change in the docs will look like while making it. Also, the sidebar ordering is done in the docusaurus folder.
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.
@leohhhn production has already been migrated to the repository gnolang/docs.gno.land.
So any changes in misc/docusaurus won't have any preview anymore. The search engine isn't developed here either.
IF there is missing stuff in gnolang/docs.gno.land, we must migrate them right now.
Keeping misc/docusaurus will only lead to confusions
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.
Here are two critical points regarding this PR:
- Markdown content & docusaurus config are coupled. They both combine to make the docs the way they are.
- People need to be able to preview the changes they are making to the docs in the docusaurus environment, not only in a simple markdown render.
I suggest we keep the working versions of both docs/
and misc/docusaurus
in the monorepo, and on each merge to master a CI copies over both folders to the docs.gno.land repo, and deploys over there.
If there is another way to fulfill both of the points above, please let me know.
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.
Ok, I know how to handle that, I'll work on it!
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.
@albttx
What's the status on this?
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.
Still a work in progress, i made improvement today
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.
@albttx Please reference the comment I left above before merging
https://github.com/gnolang/gno/pull/1801/files#r1532504955
@albttx What is the status of this PR? |
Hey @zivkovicmilos, if it's good for you, let's first merge this PR, as it is. I'll work on a solution on a separate pull request. |
1c94e98
to
6d8f766
Compare
link with : gnolang/docs.gno.land#21 |
Ok, so from what I understand:
@albttx can you please confirm that this is the setup? |
docs/sidebars.js
Outdated
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 JS.
yaml, whatever, but no JS.
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.
Just a reminder: The purpose of the docs
folder is to be embedded in gnoweb. See #522 (comment).
I suggest using simple filenames with prefixes, such as 000_hello_world.md
, 050_foo.md
, etc.
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 put a yaml file.
Maybe we can in another PR think to have a different solution using the markdown header to gathers the informations + prefixes as you mentionned.
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.
see my last comments.
docs/docker-compose.yml
Outdated
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.
Please delete this file from the repository. If necessary, relocate it to misc/, but I believe it's not essential.
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 was asked to get a dev env when developing on the docs website to have a preview.
https://github.com/gnolang/gno/pull/1801/files#r1532504955
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.
OK, but please, do it in the other repository.
The other repository should focus on docs.gno.land for development and production. It should include a command to "fetch docs/" from the main repository for both development and production purposes.
docs.gno.land is not a development tool linked to the monorepo. The docs/ folder should solely contain documentation, not web content, scripts, etc.
The thing to do in the current repo is to update gnoweb to embed docs/.
Hello @moul , i just updated following your request.
wdyt ? |
@@ -0,0 +1,27 @@ | |||
version: "3" |
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.
Why can't you simply move this file to the other repository?
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'm fine not having it... But i don't know if it's will be really confortable to get easy preview of the docs when working on it...
@leohhhn what do you think ?
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.
Read this: #1801 (comment)
If writing or previewing documents doesn't solely rely on having a basic editor and using the GitHub markdown preview, we must promptly remove the risky tool you've installed.
docs/sidebars.yml
Outdated
@@ -0,0 +1,146 @@ | |||
--- |
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.
It's not related to the docs. It's barely parseable by Gnoweb.
Please, consider my proposal to use numbered prefixes files and completely remove this file.
If you have valid reasons for not using my suggestion, please create a YAML file for documentation in the "docs/" directory. The file should contain only essential information relevant to docs/, editors, and gnoweb. Let's focus on what truly matters.
Everything related to docs.gno.land should be on the standalone website docs.gno.land, except for the .github/workflows trigger, in case a crontab is insufficient.
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 understand your position, i first update following your comment asking no js, or for json or yaml ( cf: #1801 (comment) )
But i guess the easiest solutions is to keep a .js file inside the gnolang/docs.gno.land repository and make a PR on the docs.gno.land repository when it's required to update the sidebars.
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.
The main issue is the existence of docs.gno.land. It's crucial to ensure that docs/ remains maintainable with an editor and GitHub. Imagine not having docs.gno.land. In such a case, managing page order should be done simply using markdown/filesystem in docs/. docs.gno.land should focus on theme, search engine, and deployment, without overshadowing the usefulness of the docs/ folder. Let's prioritize clarity in the docs/ folder.
Addresses #1801 (comment) Related with #1765 --------- Co-authored-by: Morgan <morgan@morganbaz.com>
This trigger the github action
netlify.yml
on gnolang/docs.gno.land when a merge is done on master and the docs/ folder have updates.I will need someone (cc: @moul ) to create and add a PAT to this repo secret 🙏🏼
EDIT:
This PR:
I'm currently working on a netlify preview, but it's a bit more complexe than expected, it will come in another PR.
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description