Skip to content

Modernize ActiveMQ website: migrated to Hugo#172

Open
kenliao94 wants to merge 6 commits intoapache:mainfrom
kenliao94:new_website
Open

Modernize ActiveMQ website: migrated to Hugo#172
kenliao94 wants to merge 6 commits intoapache:mainfrom
kenliao94:new_website

Conversation

@kenliao94
Copy link
Contributor

@kenliao94 kenliao94 commented Feb 24, 2026

This PR modernize the existing ActiveMQ website in two different dimensions:

  • It migrates to Hugo to do the static site generation
  • It modifies the UI to use more modern looking fonts and style, while keeping a similar layout and same URLs

@kenliao94 kenliao94 changed the title [WIP] Modernize ActiveMQ website Modernize ActiveMQ website: migrated to Hugo Mar 2, 2026
@kenliao94 kenliao94 marked this pull request as ready for review March 2, 2026 08:12
Copy link
Member

@jbonofre jbonofre left a comment

Choose a reason for hiding this comment

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

That's great ! Thanks a lot @kenliao94 !

As discussed, I agree with the plan:

  1. Use Hugo with the same content
  2. Some update on the look'n feel
  3. An iterating large effort to update the content and use versioned documentation

Some notes about this PR:

  1. I would update the README.md file to provide instruction for Hugo (build, test, publication), including using Hugo Docker image.
  2. AGENTS.md seems not directly related to this PR, but I'm fine to include it there. I guess you used AI to assist you there. That makes perfect sense.
  3. In support.md, I have issues about the duplicate url: content.
  4. hugo/.hugo_build.lock should not be in the PR (local build environment file). It should be added to the .gitignore.
  5. The layout doesn't render nicely on my browser. I'm investigating why.

I will do a larger review later today/tomorrow.

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.

2 participants