Migrating Hugo modules and Discourse data updates worflows

[MuhammadAashirAslam]

Replaces the obsolete submodule updater with automated Hugo Module synchronization using go.mod and go.sum. Updates the Discourse news and FAQ data workflows for Hugo’s static/assets paths, and removes the retired submodule workflow.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/workflows/update-hugo-modules.yml:1

• The retired workflow is still the documented update path: content/docs/docs-meta/overview.md:136-151 tells contributors to manage submodules and links directly to update-submodules.yml, while README.md:22-28 also instructs them to update submodules. Once this workflow is deleted, that link is dead and following the documented process will not update the Hugo modules. Please migrate these instructions to module.toml/go.mod and the new workflow as part of this change.

name: Update Hugo modules

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Suppressed comments (1)

static/js/forum-fetch.js:4

• This does not provide subpath support with the current inclusion: content/docs/fundamentals/faq.md:33 loads the file as /js/forum-fetch.js, which the browser resolves from the origin root before this code can execute. Use a Hugo/base-path-aware script URL as well; otherwise the FAQ loader still never loads when the site is hosted below a subpath.

const siteRoot = new URL("../", document.currentScript.src);