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

[BUG][WEBSITE] Inconsistent naming between URL and repo #2499

Open
ShalokShalom opened this issue Oct 26, 2023 · 5 comments
Open

[BUG][WEBSITE] Inconsistent naming between URL and repo #2499

ShalokShalom opened this issue Oct 26, 2023 · 5 comments
Labels
feature-need/important-longterm Feature: Important over the long term but may not be staffed May need multiple releases to complete kind/content-architecture Categorizes issue as PR as related to the presented structure of documentation. kind/enhancement Enhancement to an existing feature

Comments

@ShalokShalom
Copy link

ShalokShalom commented Oct 26, 2023

Describe the bug

I came here to fix a small bug but left wondering where the respective file is to be found.

Reproduction steps

  1. Go to https://o3de.org/overview/#key-concept
  2. Wonder where the "overview" directory is in the repo.
  3. Wonder where the "key concept" file is.
  4. See that the only available "key concept.md" file does show different content.

Expected behavior

Repo mirrors the URL structure of the website.

Screenshots

This is the actual issue, I came here to fix:

Screenshot_20231026_114848

I am pretty sure, the measurement unit is km² and not km.

Other information

Wonderful, that this engine is open source, you guys rock :)

@ShalokShalom ShalokShalom added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 26, 2023
@ShaunaGordon ShaunaGordon added kind/enhancement Enhancement to an existing feature feature-need/important-longterm Feature: Important over the long term but may not be staffed May need multiple releases to complete kind/content-architecture Categorizes issue as PR as related to the presented structure of documentation. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 28, 2024
@ShaunaGordon
Copy link
Contributor

This inconsistency has to do with how the original builder went about doing it. In short, they put the main site content into the layouts and partials in the Hugo system. This makes the content very hard to find in some places.

This issue will probably get fixed as part of larger architectural changes.

@ShalokShalom
Copy link
Author

So we dont know, where this part of the source is right now?

@ShaunaGordon
Copy link
Contributor

I don't know where it is offhand, myself, but what I mean is that non-docs site content isn't necessarily in markdown files, but rather in HTML files in the layouts folder.

@ShalokShalom
Copy link
Author

I guess someone could just parse it with ripgrep

@ShaunaGordon
Copy link
Contributor

@Naomi-Wash Pretty sure this is a main site thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-need/important-longterm Feature: Important over the long term but may not be staffed May need multiple releases to complete kind/content-architecture Categorizes issue as PR as related to the presented structure of documentation. kind/enhancement Enhancement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants