Modernize ActiveMQ Website

[sergio-d-lemos]

Create a new website with a more modern look and feel and also aligned with other Apache projects. At least initially, the content should remain the same. This is also an apportunity for fixing broken links thare still linger here and there.

I think we should keep it simple and continue some sort of static website generator.

Open questions:

1. Should we use https://infra.apache.org/asf-pelican.html or use some other platform (Hugo, Jekyll, etc...) and some JS/CSS framework (Tailwind, Bootstrap, etc...).

[mattrpav]

@sergio-d-lemos dropping a couple mock-up screenshots, or links to a live demo site in this issue would be super helpful =)

edit: Also-- this issue should move to the activemq-website GH project.

[sergio-d-lemos]

Hey @mattrpav , what do you think: http://ec2-35-89-152-63.us-west-2.compute.amazonaws.com/

[sergio-d-lemos]

I'm experimenting using Docusaurus. I don't have a strong preference, but from the options listed in https://github.com/apache/apache-website-template Docusaurus seems the most modern one. Comparing to Jekyll, I think it is easier to work with NodeJS than Ruby.

The bulk of the content was migrated by Claude Code, then I did some modifications on top. The documentation still has broken links which I need to review an fix.

I think the documentation page looks good even out of the box, I just need to better organize the left navigation bar (for example: http://ec2-35-89-152-63.us-west-2.compute.amazonaws.com/components/classic/documentation/virtual-destinations)

WIP code is in https://github.com/sergio-d-lemos/activemq-website/tree/docusaurus

[jbonofre]

Just as reminder, we agreed on three steps:

1. Upgrading website to use a framework like Docusaurus or Jekyll. Docusaurus is fine for me.
2. No change on the content but on the look'n feel.
3. Work on the documentation/content. It would be great to have versioned documentation (like I do on Polaris) but not strictly required.

I like the mockups. So, I'm fine to move forward with Docusaurus.

By the way, The ASF has a couple of templates for Docusaurus if you wanna take a look.

[jbonofre]

Also, remember that the website is on activemq-website repo.
Are you proposing to move the website in the "main" repo?

[sergio-d-lemos]

@jbonofre @mattrpav Thanks for taking a look at the website. I can move the website to the main repo, I think we talked multiple times about it.

@jbonofre I will look into how to version the documentation. Also, my starting point was https://github.com/apache/apache-website-template/tree/docusaurus. Will continue the work this week

[sergio-d-lemos]

A little progress report, the current WIP website can now be found in https://github.com/sergio-d-lemos/activemq/tree/website/activemq-website.

Versioning is still missing, will add it next.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment if you think it's still relevant.

[sergio-d-lemos]

The fork in https://github.com/sergio-d-lemos/activemq/tree/website/activemq-website has now all the content migrated and is functional.

I continue to work on it: there are still some broken links, some cleanup to do and versioning is missing.

[jbonofre]

@sergio-d-lemos great! Let me do a new pass. Thanks!

[sergio-d-lemos]

Updated https://github.com/sergio-d-lemos/activemq/tree/website/activemq-website with the most up-to-date contents from activemq-website

[jbonofre]

@sergio-d-lemos thanks for the update. I'm back on it.

[mattrpav]

@sergio-d-lemos this is docusaurus, correct? I'm wondering what the benefits are v Hugo? Apache Camel is doing a refresh using Hugo and one of the things they have is text-based search over the static content.

Camel's new demo site:
ref: https://pr-1740--camel.netlify.app/