Skip to content

Luke/ibc#2294

Merged
jcstein merged 1 commit intodocs-glow-upfrom
luke/ibc
Nov 6, 2025
Merged

Luke/ibc#2294
jcstein merged 1 commit intodocs-glow-upfrom
luke/ibc

Conversation

@lukecd
Copy link
Copy Markdown
Contributor

@lukecd lukecd commented Nov 5, 2025

this PR

  • Adds an overview for IBC
  • Reworks the menu structure, moving some items from BUILD to LEARN
  • Adds some placeholder items in LEARN just to give that section some "meat", but the whole menu flow is still up for discussion. Placeholders were just added to help show the bridging in context.

@lukecd lukecd requested a review from jcstein November 5, 2025 10:10
Comment thread .github/workflows/preview.yaml Dismissed
Comment thread .github/workflows/preview.yaml Dismissed
Comment thread .github/workflows/preview.yaml Dismissed
Comment on lines +49 to +52
- name: Export static HTML
run: yarn next export

- name: Deploy preview

Check failure

Code scanning / CodeQL

Checkout of untrusted code in a privileged context Critical

Potential execution of untrusted code on a privileged workflow (
pull_request_target
)
Comment thread .github/workflows/lint.yaml Dismissed
Comment thread .github/workflows/preview.yaml Dismissed
Comment thread .github/workflows/preview.yaml Dismissed
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @lukecd, I'm Gemini Code Assist1! 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 represents a significant architectural shift for the documentation site, migrating the entire platform from VitePress to a Next.js/Nextra framework. This change involves a complete restructuring of the content, introducing new top-level sections like 'Learn,' 'Build,' and 'Operate,' and laying the groundwork for a more dynamic and modular documentation experience. The existing documentation content has been largely replaced with new files reflecting this new structure, including an overview for IBC and a Go client tutorial.

Highlights

  • Documentation Platform Migration: The entire documentation site has been migrated from VitePress to a Next.js/Nextra framework, representing a significant architectural overhaul.
  • Content Structure Rework: The menu and content organization have been completely restructured into new top-level categories: 'Learn', 'Build', and 'Operate'.
  • New IBC Overview: An overview page for Inter-Blockchain Communication (IBC) with Celestia has been added, explaining its purpose and how bridging works.
  • Go Client Tutorial: A new tutorial for the Celestia Go client has been introduced, guiding users through submitting and retrieving blobs without running a full node.
  • Twinkle Integration Guide: A guide for using Twinkle, a hosted API service, to post and retrieve blobs on Celestia has been added.
  • Placeholder Content for Expansion: Numerous placeholder pages have been added across the new 'Learn', 'Build', and 'Operate' sections to outline future content and illustrate the new menu flow.
Ignored Files
  • Ignored by pattern: .github/workflows/** (8)
    • .github/workflows/build.yml
    • .github/workflows/deploy.yml
    • .github/workflows/latest_tags.yml
    • .github/workflows/link-check.yml
    • .github/workflows/lint.yaml
    • .github/workflows/preview.yaml
    • .github/workflows/preview.yml
    • .github/workflows/spellcheck.yml
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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request marks a significant migration of the documentation site from VitePress to Next.js with Nextra, alongside a restructuring of the content. While this is a major step forward, my review has identified several critical and high-severity issues that need attention. These include a misconfigured 'Edit this page' link, broken image references, incorrect component syntax that will lead to rendering errors, and the removal of important contributor information from the README. I've also noted some medium-severity concerns regarding dark mode support for the logo and the use of beta dependencies, which could affect stability. Addressing these points will be crucial for ensuring the new documentation site is fully functional, maintainable, and user-friendly.

Comment thread README.md
[![Discord](https://img.shields.io/discord/638338779505229824)](https://discord.com/invite/celestiacommunity)
[![License](https://img.shields.io/badge/License-Apache2.0-green.svg)](https://www.apache.org/licenses/LICENSE-2.0)
[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/celestiaorg/docs)
This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The new README.md is the default from create-next-app. The old README contained valuable information for contributors, including contribution guidelines and documentation standards. This information should be preserved, either by updating the new README or by moving the content to a CONTRIBUTING.md file. Removing it entirely makes it harder for new contributors to get started.

Comment on lines +248 to +250
:::tip
For QuickNode: `CELE_DA_URL` uses `https://` and no port, while `CELE_CORE_GRPC` uses a port (e.g. `:9090`) and no `https://` prefix.
:::
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The ::::tip syntax is from VitePress and is not supported in Nextra. This will cause a rendering error. Please use the <Callout> component instead, and ensure it's imported at the top of the file with import { Callout } from 'nextra/components'.

<Callout type="info">
For QuickNode: `CELE_DA_URL` uses `https://` and no port, while `CELE_CORE_GRPC` uses a port (e.g. `:9090`) and no `https://` prefix.
</Callout>

Comment thread app/layout.tsx
banner={banner}
navbar={navbar}
pageMap={await getPageMap()}
docsRepositoryBase="https://github.com/shuding/nextra/tree/main/docs"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The docsRepositoryBase is pointing to a Nextra example repository. This will cause the "Edit this page" link to point to the wrong location. It should be updated to point to this project's repository.

Suggested change
docsRepositoryBase="https://github.com/shuding/nextra/tree/main/docs"
docsRepositoryBase="https://github.com/celestiaorg/docs/tree/main"


## How bridging works

![IBC technical diagram](/img/ibc-diagram.png)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This image path points to /img/ibc-diagram.png, but the image file does not appear to be included in the pull request. This will result in a broken image. Please ensure the image is added to the public/img/ directory.

Comment thread app/layout.tsx
Comment on lines +21 to +28
<Image
src="/logo-light.svg"
alt="Celestia"
width={140}
height={32}
priority
style={{ height: 'auto' }}
/>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The logo is hardcoded to the light version (logo-light.svg), which will not have good visibility in dark mode. The previous VitePress configuration supported separate light and dark mode logos. A similar mechanism should be implemented here. You could use a component that renders different SVGs based on the theme, or use CSS to switch between two images.

You can use IBC to bridge assets between Celestia-native chains along with other chains.

<Callout type="info">
Celestia uses relayers to forward packets between chains. Relayers are processes that can be run by anyone which constantly scan for outbound packets on one chain and submits these packets alongside corresponding proofs on the destination chain. This doc covers using IBC to bridge assets, we also [have docs on how to run a relayer](TODO).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This link is a placeholder (TODO). Please update it to point to the correct documentation for running a relayer.


![IBC technical diagram](/img/ibc-diagram.png)

**TEMPOARY DIAGRAM, WELL HAVE YONI REDO IN CELESTIA STYLE IN THE FUTURE**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There are a couple of typos in this placeholder note. TEMPOARY should be TEMPORARY, and WELL should be WE'LL.

**TEMPORARY DIAGRAM, WE'LL HAVE YONI REDO IN CELESTIA STYLE IN THE FUTURE**

Comment thread app/page.mdx
Comment on lines +3 to +33
<div style={{textAlign: 'center', fontFamily: "'Comic Sans MS', cursive", background: 'linear-gradient(45deg, #ff00ff, #00ffff, #ffff00)', padding: '20px', border: '5px dashed #ff0000', margin: '20px'}}>

<img src="/underConstruction.png" alt="Under Construction Mammoth" style={{maxWidth: '100%', height: 'auto', margin: '20px 0'}} />

<h2 style={{color: '#ff0000', textShadow: '2px 2px 4px #000000', fontSize: '2em', margin: '20px 0'}}>
🔥 CELESTIA DOCS ARE BEING BUILT 🔥
</h2>

<p style={{fontSize: '1.2em', color: '#0000ff', background: '#ffff00', padding: '10px', border: '3px solid #ff0000', margin: '20px'}}>
<strong>⚠️ WARNING: This site is under heavy construction! ⚠️</strong><br/>
Our mammoth construction crew is working hard to bring you the best docs ever!<br/>
Please check back soon for the full experience! 🦣
</p>


<div style={{background: '#ffff00', color: '#ff0000', padding: '10px', border: '3px solid #0000ff', margin: '20px', fontWeight: 'bold'}}>
🎵 <span>COMING SOON TO A BROWSER NEAR YOU!</span> 🎵
</div>

<div style={{textAlign: 'center', margin: '30px 0'}}>
<a href="/learn" style={{background: '#ff00ff', color: '#ffffff', padding: '10px 20px', textDecoration: 'none', border: '3px solid #000000', fontWeight: 'bold', margin: '10px', display: 'inline-block'}}>📚 LEARN</a>
<a href="/build" style={{background: '#00ffff', color: '#000000', padding: '10px 20px', textDecoration: 'none', border: '3px solid #000000', fontWeight: 'bold', margin: '10px', display: 'inline-block'}}>🛠️ BUILD</a>
<a href="/operate" style={{background: '#ffff00', color: '#000000', padding: '10px 20px', textDecoration: 'none', border: '3px solid #000000', fontWeight: 'bold', margin: '10px', display: 'inline-block'}}>⚙️ OPERATE</a>
</div>

<div style={{background: '#ff0000', color: '#ffffff', padding: '15px', border: '5px solid #ffff00', margin: '20px', textAlign: 'center'}}>
<h3 style={{margin: '0'}}>🦣 MAMMOTH CONSTRUCTION CREW 🦣</h3>
<p style={{margin: '10px 0 0 0', fontSize: '0.9em'}}>Building the future of modular blockchains, one pixel at a time!</p>
</div>

</div> No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This page uses a lot of inline styles, which can be difficult to maintain. For better separation of concerns and reusability, consider moving these styles to a dedicated CSS file and using classes instead.

@jcstein jcstein changed the base branch from main to docs-glow-up November 5, 2025 17:47
# Using Twinkle to post and retrieve blobs on Celestia

[Twinkle](https://t.tech/) is a hosted API service that lets you interact with Celestia's data availability layer without running your own node. With an API key, you can post and retrieve blobs on Celestia.
[Twinkle](https://t.tech/) is a hosted API service that lets you interact with Celestia's data availability layer without running your own node. With an API key, you can post and retrieve blobs on Celestia and pay for storage using a credit card.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm starting to see credit card as a huge benefit

Comment thread app/learn/TIA/_meta.js
@@ -0,0 +1,5 @@
export default {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i like this overview

@jcstein jcstein merged commit 05dffba into docs-glow-up Nov 6, 2025
4 checks passed
@jcstein jcstein deleted the luke/ibc branch November 6, 2025 16:48
@jcstein
Copy link
Copy Markdown
Member

jcstein commented Nov 7, 2025

@lukecd, I just realized this has a google doc in it with markdown, which is hard to edit in the docs. is this in review elsewhere before being put into code?

https://github.com/celestiaorg/docs/blob/docs-glow-up/app/learn/features/private-da/page.mdx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants