Hi team, We have a Docusaurus-based website in https://activemq-proposal.netlify.app/. There were some discussions around which stack to use in https://github.com/apache/activemq/issues/2101. Docusaurus has a client-side search plugin, which was one of the nice-to-haves. Matt and I discussed we should have some validation that a new website still respect the same URLs as the existing one (so all the links and bookmarks out there still work, same with search engines), yesterday I prototyped an automatic validation, I will update the PR for the Docusarus website before EOW.
I know there are many static website platforms, I'm ok if the community decides for something else. But the Docusaurus is pretty much done. Sérgio Em ter., 3 de nov. de 2026 às 11:25, Matt Pavlovich via dev < [email protected]> escreveu: > As we are starting to keep a cadence going on releases, I thought it might > be good to settle on the website tech stack update. > > I know Sergio has some working sites out there with updated stacks and > features. > > Given the good cadence and updates, I think it would make sense to get the > new website tech stack settled, so as we need new documentation on features > and releases we are doing it on the new site, vs having to continue to pull > forward the changes to the website update PRs. > > Thoughts? > > -Matt Pavlovich > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > >
