Skip to content

feat: remove Korean page#160

Closed
DennisPitallano wants to merge 0 commit intoDigiByte-Core:masterfrom
DennisPitallano:master
Closed

feat: remove Korean page#160
DennisPitallano wants to merge 0 commit intoDigiByte-Core:masterfrom
DennisPitallano:master

Conversation

@DennisPitallano
Copy link
Copy Markdown
Contributor

@DennisPitallano DennisPitallano commented Jan 17, 2026

  • issue Remove Korean language from DigiByte .org #158
    preview: https://dg-bio.vercel.app/
    This pull request removes support for the Korean language (ko) across the website. The changes ensure that Korean is no longer available as a language option in the language menus and is also removed from the sitemap, so it will not appear in search engine alternate language listings.

Most important changes:

Language menu updates:

  • Removed the Korean (ko) language option from the desktop language menu in langmenu/desktop.html.
  • Removed the Korean (ko) language option from the mobile language menu in langmenu/mobile.html.

Routing and sitemap updates:

  • Removed references to Korean (ko) in the sitemap (sitemap.xml), so search engines will no longer see it as an available alternate language. This includes removing the <xhtml:link rel="alternate" hreflang="ko" ... /> entries throughout the file. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
  • Updated the language router in js/languagerouter.js to remove ko from the list of supported languages for routing.

Copy link
Copy Markdown
Member

@DGBNOOB DGBNOOB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Summary — Remove Korean Page (61fda55)

Files changed: 5

Thank you for adding the vercel.app preview link — it made it much easier to review the changes. The most visible update is in the language dropdown menu, where the Korean (ko) option has been removed. It previously appeared between ja and zh. Beyond this visual confirmation, I did not perform functional testing; my review focused solely on the file changes.

Files Updated

  • js/languagerouter.js — Korean route removed
  • ko/index.html — deleted
  • langmenu/desktop.html — Korean entry removed
  • langmenu/mobile.html — Korean entry removed

I wasn’t entirely sure about the sitemap.xml changes, so I asked Copilot for a summary. This was the explanation:


🧩 Summary of the sitemap.xml Change (PR #160)

The pull request removes the Korean-language page (/ko/) from the DigiByte.org sitemap, aligning with the overall goal of fully removing the Korean page from the website.

🔍 What actually changed

  • One deletion: the <url> entry referencing /ko/ was removed.
  • One addition: the sitemap was updated to reflect the remaining supported languages.
  • No other structural changes were made.

🧭 Why this matters

  • Search engines will no longer index the Korean page.
  • The sitemap remains accurate and avoids SEO issues such as dead links.
  • This change is consistent with the removal of /ko/index.html and the Korean entries in the language menus and languagerouter.js.

I expected this update to be more involved than simply deleting ko/index.html, and that turned out to be true. Dennis, thank you again for handling this. I could have attempted it with AI assistance, but I wouldn’t have been confident that all references were removed cleanly or that search engines would stop indexing the page.

Recommendation: Approve — cACK

Copy link
Copy Markdown
Member

@ycagel ycagel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cACK. Thank you Dennis!

@ycagel
Copy link
Copy Markdown
Member

ycagel commented Jan 17, 2026

Are you able to resolve the conflicts @DennisPitallano?

@DennisPitallano
Copy link
Copy Markdown
Contributor Author

new PR #162

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants