docs: clean up menu from sync

[jcstein]

Overview

1. removes onchaindb, livy, chopin from post/retrieve section
2. removes lazybridging
3. changes ibc and hyperlane to 2 distinct pages
4. removes unecessary page for "stacks" that causes dupilcate menu items

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines and updates the project's documentation by reorganizing menu structures and removing obsolete content. The primary goal is to enhance clarity and maintain accuracy within the documentation, making it easier for users to navigate and find relevant information. This involves both splitting existing topics for better granularity and eliminating pages that are no longer current or necessary.

Highlights

• Bridging Documentation Restructuring: The bridging section's navigation has been updated, splitting the "IBC / Hyperlane" entry into distinct "IBC" and "Hyperlane" options, each with its own dedicated page.
• Removal of Outdated Content: Several documentation pages and their corresponding menu entries have been removed, including "Lazybridging" from the bridging section, and "OnchainDB", "Livy", and "Chopin" from the post-retrieve-blob section, along with a standalone "Stacks" page.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request cleans up and refactors the documentation menu. It splits the 'IBC / Hyperlane' section into two, and removes several pages like 'Lazybridging', 'OnchainDB', 'Livy', 'Chopin', and 'Stacks'. The changes are mostly good, but there's a potential for a broken link due to the removal of the 'Stacks' page without updating its reference in the parent menu configuration. I've also pointed out a minor inconsistency in a page title.

[gemini-code-assist]

The removal of this page is likely to cause a broken link in the site's navigation. The parent directory's metadata file, app/build/_meta.js, still contains an entry for stacks: "Stacks". To prevent a broken link, you should also remove this entry from app/build/_meta.js.

[gemini-code-assist]

The page title 'IBC bridging' is slightly inconsistent with its menu entry 'IBC' (defined in app/build/bridging/_meta.js). For better consistency, and to align with the 'Hyperlane' page which has a matching title and menu entry, consider renaming this title to just 'IBC'.

# IBC