This is a Docusaurus artifact that I wasn’t able to work around easily. There are multiple places that the URLs are manipulated when the site is served. This issue happens when you navigate into a page and then use the top-menu to navigate to another internal page. Docusaurus adds an additional suggested-site to the URL. This is only an issue for the review period when the site is served from the /suggested-site directory.
When you encounter this URL issue, please edit the URL by hand to remove the duplicate suggested-site. This issue only seems to happen with the ignite-website pages and does not affect the Ignite 2 or Ignite 3 documentation. For example: - Incorrect: https://ignite.apache.org/suggested-site/suggested-site/community - Correct: `https://ignite.apache.org/suggested-site/community <https://ignite.apache.org/suggested-site/community%60>` Sorry for the confusion. Michael On Jan 13, 2026 at 9:08:31 AM, Mirza Aliev <[email protected]> wrote: > In addition, > > I noticed a navigation issue on the suggested site. > > If I click the Blog button and open link [1], then try to navigate using > any of the top-menu dropdowns (for example Community/Start Contributing [2] > or Resources/Get Started [3]), those links lead to a 404 page for me. > > [1] https://ignite.apache.org/suggested-site/blog/ > [2] > > https://ignite.apache.org/suggested-site/suggested-site/community#contributing > [3] > > https://ignite.apache.org/suggested-site/suggested-site/resources#get-started > > вт, 13 янв. 2026 г. в 18:47, Mirza Aliev <[email protected]>: > > Michael, > > > Thank you for the great work on the update! > > > I might be missing something, but it looks like the new version [1] no > > longer includes the detailed tables with node configuration parameters and > > their descriptions. > > In the previous version of the documentation [2], these tables were very > > helpful and easy to reference. > > > I expected to see the same level of detail in the new docs [1]. Was this > > information moved elsewhere, or is it something that’s still in progress? > > > Seems like the same is applicable for the cluster configuration [3] > > > [1] > > > https://ignite.apache.org/suggested-site/docs/ignite3/3.1.0/configure-and-operate/reference/node-configuration#configuration-parameters > > [2] > > > https://ignite.apache.org/docs/ignite3/latest/administrators-guide/config/node-config#configuration-parameters > > [3] > > > https://ignite.apache.org/suggested-site/docs/ignite3/3.1.0/configure-and-operate/reference/cluster-configuration#configuration-parameters > > > вт, 13 янв. 2026 г. в 13:30, Pavel Tupitsyn <[email protected]>: > > > > Michael, > > > > > > Thank you for the proposal! Glad to see the Markdown migration. > > > > > > 1. Please share links to the code changes > > > 2. Not sure about "Fast OR Consistent? Choose Both" text on the main > > > page. It is not clear anymore what the page is about at a glance, I > > > would keep "Distributed Database" there one way or another. > > > > > > On Mon, Jan 12, 2026 at 7:54 PM Michael Aglietti <[email protected]> > > > wrote: > > > > > > > > Update, I mistakenly set the wrong voting date. Here is the correct > > > schedule: > > > > > > > > Proposal Date: January 12, 2026 > > > > Voting Date: January 26, 2026 > > > > Release Date: February 2, 2026 > > > > > > > > Sorry for the confusion. > > > > > > > > Best, > > > > > > > > Michael Aglietti > > > > > > > > > On Jan 12, 2026, at 11:49 AM, Michael Aglietti <[email protected]> > > > wrote: > > > > > > > > > > Dear Ignite Community! > > > > > > > > > > Apache Ignite 3 has been out for close to a year, I would like to > > > suggest a rework of the website to account for the new version. > > > > > > > > > > The website is about 5 years old now, and there were multiple > > > releases of both Ignite 2 and Ignite 3 that are not accounted for, and > the > > > website uses a pug source file format that is hard to maintain and edit. > > > > > > > > > > I suggest migrating both the website frontend and the documentation > > > to the more modern Docusaurus (https://docusaurus.io/) format. > > > > > > > > > > This allows us to switch to a unified markdown format, and use a more > > > modern and simpler build process. > > > > > > > > > > I prepared drafts for the changes in both documentation and website > > > that would showcase the switch as a hidden subsection of the main site > > > available here: > > > > > > > > > > https://ignite.apache.org/suggested-site/ > > > > > > > > > > Both drafts are ready for review and with community approval can be > > > merged and published. > > > > > > > > > > Proposed timeline: > > > > > > > > > > Proposal Date: January 12, 2026 > > > > > Voting Date: December 26, 2026 > > > > > Release Date: February 2, 2026 > > > > > > > > > > Best, > > > > > Michael Aglietti > > > > > > > > > >
