-
Notifications
You must be signed in to change notification settings - Fork 810
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
Upgrade Docsy #3382
Upgrade Docsy #3382
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Kalaiselvi84 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@markmandel
Could you please share your thoughts? |
Let's see what the preview looks like! |
Build Succeeded 👏 Build Id: 6d614fcf-28b4-4661-9233-d128a53475d6 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
With this approach - did you attempt to resolve the issues within the .md files? If so, where did you end up? |
Followed all the Migrate to hugo modules instructions except this command
All the targets passed successfully, after resolving the error. However, the Agones site's front page doesn't appear as expected, |
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.
Seems like some CSS changes in our custom landing page.
How's you CSS? 😃
@@ -3,3 +3,5 @@ module github.com/agones/agones/site | |||
go 1.20 |
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.
Apache header please.
@@ -17,7 +17,7 @@ title = "Agones" | |||
enableRobotsTXT = true | |||
|
|||
# Hugo allows theme composition (and inheritance). The precedence is from left to right. | |||
theme = ["docsy"] | |||
theme = ["github.com/google/docsy", "github.com/google/docsy/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.
Should we delete the layouts/docsy
folder as well?
@@ -30,7 +30,7 @@ List of items to do for upgrading to {version_1} {version_2} {version_3} | |||
- [ ] Regenerate Kubernetes resource includes (e.g. ObjectMeta, PodTemplateSpec) | |||
- [ ] Start a cluster with `make gcloud-test-cluster` (this cluster will use Kubernetes {version_2}), uninstall agones using `helm uninstall agones -n agones-system`, and then run `make gen-embedded-openapi` and `make gen-install` | |||
- [ ] Update documentation for creating clusters and k8s API references to align with the above clusters versions and the k8s API version | |||
- [ ] `site/config.toml` | |||
- [ ] `site/hugo.toml` |
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.
Is this value in the hugo.toml? Looks like it's still in config.toml?
Please let me know the required changes. Will do it🙂 |
Sounds good - will check out the preview and see what the differences are! |
Build Failed 😱 Build Id: 1b9c72e8-0a15-4871-b9e3-eb4c20aa6e89 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: 937c2611-38d2-4d6e-b66c-d5af5fd1c66c To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
That's a weird one:
Not seen that before as a flake. Happened on generic-1.27 |
Build Succeeded 👏 Build Id: ae51576a-9b9b-4504-b9ae-d6c38098840d The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
This is getting really close! |
The current change looks good in the smaller screen. However, if we increase the gap between the tools, the bigger screen will look good, but the smaller screen will look messy. Share your thoughts please.. |
Are we planning to keep the |
I'm not convinced that was the issue specifically. I'd still like to keep the docsy folder as it allows us to make patches to docsy without having to first get them pushed upstream. |
This reverts commit 8c189bb.
Build Succeeded 👏 Build Id: 4594ea63-ed8f-4a4f-841e-b89063dd1d16 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Sorry I should have asked a clarifying question: In this PR we using the theme It looks like we migrated to using Hugo modules? If that's the case, then yeah - delete the docsy folder if we're not using it anymore. Sorry, I should have asked that first. |
Yes, migrated to Hugo modules: https://www.docsy.dev/docs/updating/convert-site-to-module/. However, the |
Why does it need it? Seems like it shouldn't be required anymore? |
Will delete it. This is not necessary as we are initially cleaning up the working directory in build script? |
Well if we're not using that folder for anything for generating the website, then we don't need the folder 👍🏻 The build script doesn't affect any of this - the updated version uses whatever is latest from |
I've attempted various alignment methods for the Agones title, description, and asciinema-player on the landing page. While the alignment appears satisfactory on a laptop screen, it doesn't translate as well to larger screens. For reference, here are the different alignment methods I've tried with Based on the latest preview available at https://c28c58b-dot-preview-dot-agones-images.appspot.com/, the alignment seems acceptable on both screens. Should we proceed with this current configuration? WDYT? |
Build Succeeded 👏 Build Id: e86f756c-9e64-40d1-aa95-a34100dc2fd9 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
I think I might need to download this and see what playing around with the CSS rules will do 😃 A couple of things of note if you have some good ideas on (and so I don't forget), and are probably the biggest issues I see: In the headerThe "AGONES" should be bold. This is what the current website looks like: Should be a case of setting the font weight appropriately. Front pageThat big gap between the console and the "Host, Run and Scale dedicated game servers on Kubernetes" There are some other layout differences, but nothing I think we need to be huge blockers on. Only other thought - the Community Page (preview) seems to have the wide layout. We could check the source code there to see how they are doing that (if we want to go wide that is). |
I believe I might be overlooking a detail. I attempted to use the command However, I received the following error:
I've ignored this error because the error message indicates that |
Curious - why? 😃 |
I've corrected the error and included the appropriate go.mod and go.sum files in the latest PR. Apologies for the oversight.. |
Filed Kalaiselvi84#325 against your branch, that I believe fixes all the issues. PTAL and let me know if you see anything missing! |
Closing this PR, since the task has been completed in another PR: #3417 |
What type of PR is this?
/kind cleanup
What this PR does / Why we need it:
Which issue(s) this PR fixes:
Closes #
Special notes for your reviewer: