+1. Thanks! вт, 27 янв. 2026 г., 09:22 Pavel Tupitsyn <[email protected]>:
> +1 (binding) > > Excellent work! > > 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 >
