After some consideration, I'm changing my vote to 0, because all aforementioned issues are minor and should not be considered as release blockers.
Thank you again for the site rework! On Tue, Jan 27, 2026 at 11:33 AM Aleksandr Polovtsev < [email protected]> wrote: > Sorry, forgot to put a -1 vote. > > On Tue, Jan 27, 2026 at 11:31 AM Aleksandr Polovtsev < > [email protected]> wrote: > >> Michael, >> >> First of all, thanks for the great work, the website looks much better. >> However, I've stumbled upon several minor issues: >> >> 1. "Resources" tab has a "blog" link which literally points to the next >> tab, also called "Blog". I think this may be redundant; >> 2. >> https://ignite.apache.org/suggested-site/features/architectural-foundation/ >> contains the "Memory-First Storage" section, which is very confusing to me. >> It talks about Raft for AIPERSIST and "version chains for microsecond-level >> access" for AIMEM, what does that even mean? >> 3. I've noticed that depending on the page, the links in the header can >> be completely different (and also broken). For example, go to >> https://ignite.apache.org/suggested-site/features/storage and then try >> to open any of the links from the header. >> 4. The text at the start of the >> https://ignite.apache.org/arch/multi-tier-storage.html looks weird, as >> if the font size is incorrect, because it looks like a very long header; >> 5. https://ignite.apache.org/arch/native-persistence.html has a >> configuration example, but it comes from Ignite 2, which may be confusing >> for Ignite 3 users; It also talks about WAL, which is an Ignite 2 feature. >> This is a common problem for the website, actually, because, for example, >> on some pages we mention Raft and storage engines (not present in Ignite >> 2), while on the others we mention Ignite 2 features. >> 6. https://ignite.apache.org/our-community.html#faq has a "Report An >> Issue" section which leads to Ignite 2's repository, there's no link to >> Ignite 3 repository; >> 7. Some links in the "Features" tab lead to pages on the website, while >> others lead directly to documentation (like Continuous Queries), probably >> that's a WIP. >> >> On Mon, Jan 26, 2026 at 6:35 PM Michael Aglietti <[email protected]> >> wrote: >> >>> Igniters, >>> >>> The proposed Ignite website and Ignite 3.1.0 documentation sites are >>> ready: >>> https://ignite.apache.org/suggested-site/ >>> >>> Thank you to everyone who provided feedback. The complete list of >>> feedback issues resolved: >>> https://github.com/apache/ignite-website/pull/309 >>> >>> Note: There are some interactions between the nav bar, the site builder, >>> docs URLs and the URL rewrite rules that are not resolvable wile the >>> proposed site is in the "proposed-site sub-directory" of the main site. URL >>> and link issues will be resolved when the site is moved to the production >>> location. >>> >>> This release updates the ignite-website from PUG to Docusaurus and the >>> Ignite 3 documentation from Jekyll to Docusaurus. >>> >>> Changes to the Ignite Website: >>> >>> Replatformed the website from PUG to Docusaurus with an updated >>> infrastructure, navigation, and component architecture. Updated the >>> homepage with ASF 2025 branding, restructured the Use Cases and Features >>> sections for Ignite 3, and implemented a blog system with tag filtering. >>> >>> Changes to Ignite 3 Documentation: >>> >>> Migrated the documentation from Jekyll/AsciiDoc to Docusaurus/MDX, >>> enabling modern documentation features. Reorganized the content into five >>> top-level sections (Getting Started, Understand, Develop, Configure and >>> Operate, SQL). >>> >>> Changes to Ignite 2 Documentation: >>> >>> No changes were made to the Ignite 2 docs, they remain in >>> Jekyll/AsciiDoc. >>> >>> The vote is formal, see voting guidelines: >>> https://www.apache.org/foundation/voting.html >>> >>> - +1 - to accept the suggested Apache Ignite Website rework >>> - 0 - don't care either way >>> - -1 - DO NOT accept the suggested Apache Ignite Website rework (explain >>> why) >>> >>> This vote is open until Thursday January 29, 2026, 08:00 UTC. >>> >>> Thank you, >>> >>> Michael Aglietti >> >> >> >> -- >> With regards, >> Aleksandr Polovtsev >> > > > -- > With regards, > Aleksandr Polovtsev > -- With regards, Aleksandr Polovtsev
