Fix: Docusaurus Build by Upgrading

[GatienBoquet]

What?

• Upgraded Docusaurus to the latest version.
• Updated dependencies to ensure compatibility with the new Docusaurus version.
• Adjusted configuration settings in docusaurus.config.js to align with the updated version requirements.

Why?

Deployments on the web are currently failing, and changes made to the docs are not reflecting on the actual website. Upgrading Docusaurus is intended to resolve these build failures and improve the stability and performance of our documentation site. Additionally, ensuring the Algolia app_id is correctly configured is crucial for the search functionality.

How?

• Upgraded Docusaurus by modifying the version in the package.json file.
• Updated all necessary dependencies to match the new Docusaurus requirements.
• Made required adjustments to the configuration file (docusaurus.config.js) to support the upgraded version.

Regression

• Fonts: The old fonts are not working with the new version, so they were deleted. Please let me know if you still want to use the old fonts, and we can explore alternative solutions to reintegrate them.

Testing?

• Verified successful site build with the upgraded Docusaurus version.
• Checked that all existing documentation pages render correctly.
• Confirmed that the main functionality of the site is intact post-upgrade.

Request for Additional Information

@nandorojo, I need the actual app_id of Algolia to update the search configuration in docs/docusaurus.config.js. Please provide this information so that we can ensure the search functionality is correctly configured.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
moti	❌ Failed (Inspect)			Aug 8, 2024 9:59pm

[GatienBoquet]

Build still fail for some reason.

@nandorojo can you check the vercel logs ?

[nandorojo]

i think the issue is the mode version. just pushed a change

[GatienBoquet]

Great it got deployed on the preview :)