docs: rearrange docs structure and prepare for future outline#2051
Open
docs: rearrange docs structure and prepare for future outline#2051
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Contributor
📝 WalkthroughWalkthroughThis PR restructures the ENSNode documentation site by implementing a new Starlight Astro integration with organized sidebar topics, creating numerous new documentation pages, and consolidating route mappings from legacy component-specific paths ( ChangesDocumentation Site Restructuring with Starlight Integration
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related issues
Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Greptile SummaryThis PR restructures the ENSNode documentation site by reorganising content into four top-level topic areas — "Build with ENS", "Self-host ENSNode", "Reference", and "ENSNode components" — and splitting the monolithic
Confidence Score: 4/5Safe to merge after fixing three broken internal links introduced by the directory rename from deploying/ to self-host/ and the ENSIndexer path restructure. Two links in self-host/index.mdx still point to the removed /docs/deploying/* path, and one link in self-host/docker.mdx points to the old /ensindexer/usage/configuration route — all three will 404 for users on the live site. The rest of the restructure looks correct. docs/ensnode.io/src/content/docs/docs/self-host/index.mdx and docs/ensnode.io/src/content/docs/docs/self-host/docker.mdx contain the broken links that need fixing before merging. Important Files Changed
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.memory-bank/tasks/1777-new-docs/readme.md:
- Line 135: Replace the inline note "Need help of `@shrugs` with that because I
dont have full context about what omnigraph can do" with a clear TODO that (1)
corrects the typo to "don't", (2) creates or links to a tracking issue or
checklist entry for completing the "cookbook recipes" section, and (3)
explicitly requests review/input from `@shrugs` (or another owner) on Omnigraph
capabilities so the recipes can be authored; reference the document section
title "cookbook recipes" and the technology name "Omnigraph" so reviewers can
find the context.
- Line 96: The fenced code blocks containing outline lists (the one that begins
with "1. Build with ENS ← Journey A (default landing)" and the other
similar outline blocks) are missing language specifiers; update each opening
fence from ``` to ```text for all four outlined blocks so the markdown linter
accepts them (i.e., change the triple-backtick lines that start those
outline/code sections to include the language specifier "text").
- Around line 76-77: Replace the wordy and ungrammatical sentence "My assumption
is that we have 2 usecases for user to read our documentation" with a clear,
grammatical alternative such as "There are two use cases for users to read our
documentation" (or "We have two use cases for users reading our documentation");
update the numeral "2" to the word "two" and split "usecases" into "use cases"
and change "user" to "users" to fix agreement and clarity.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 7909679b-4495-4733-b324-f6136d8b1de9
📒 Files selected for processing (1)
.memory-bank/tasks/1777-new-docs/readme.md
lightwalker-eth
approved these changes
May 5, 2026
Member
lightwalker-eth
left a comment
lightwalker-eth
left a comment
There was a problem hiding this comment.
@sevenzing Very excited for this. This is a high impact high priority. Reviewed and shared suggestions with feedback. Let's execute this!
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (3)
.memory-bank/tasks/1777-new-docs/readme.md (3)
154-154:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix typo and track TODO (previously flagged).
The inline note still contains "dont" (should be "don't") and represents an unresolved content gap that should be tracked.
Proposed fix
-Need help of `@shrugs` with that because I dont have full context about what omnigraph can do +Need help of `@shrugs` with that because I don't have full context about what omnigraph can doConsider creating a tracking task or checklist item for completing the cookbook recipes section with input from
@shrugson ENS Omnigraph capabilities.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.memory-bank/tasks/1777-new-docs/readme.md at line 154, Fix the inline typo "dont" to "don't" in the readme note and replace the unresolved inline comment with a tracked TODO: add a clear checklist or task entry (e.g., "TODO: consult `@shrugs` on ENS Omnigraph capabilities and finish cookbook recipes") so the gap is visible and assignable; update the note in .memory-bank/tasks/1777-new-docs/readme.md where the inline comment appears and ensure it references `@shrugs` and the specific topic ("ENS Omnigraph capabilities / cookbook recipes") so it can be followed up.
97-98:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix grammar and clarity issues (previously flagged).
This sentence still contains the issues flagged in the previous review:
- "My assumption is that we have" is unnecessarily wordy
- "usecases" should be "use cases" (two words)
- "for user" should be "for users"
✏️ Proposed fix
-My assumption is that we have 2 usecases for user to read our documentation +We have two use cases for users reading our documentation🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.memory-bank/tasks/1777-new-docs/readme.md around lines 97 - 98, Replace the wordy and ungrammatical sentence "My assumption is that we have 2 usecases for user to read our documentation" with a clear, corrected version—change "2" to "two", "usecases" to "use cases", and "for user" to "for users"; for example, update the README sentence to "There are two use cases for users to read our documentation" (or equivalent concise phrasing) so grammar and clarity are fixed.
120-120: 🧹 Nitpick | 🔵 Trivial | 💤 Low valueAdd language specifiers to fenced code blocks (previously flagged).
The markdown linter still flags missing language specifiers on the fenced code blocks at lines 120, 128, 169, and 189. Add
textas the language specifier to satisfy the linter and improve rendering.Example fix
-``` +```text 1. Build with ENS ← Journey A (default landing) 2. Self-host ENSNode ← Journey B 3. Reference ← terminology, REST API, Subgraph API, ENSAdmin (folded in) ```Apply the same pattern to lines 128, 169, and 189.
Also applies to: 128-128, 169-169, 189-189
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.memory-bank/tasks/1777-new-docs/readme.md at line 120, There are several fenced code blocks missing language specifiers; update each of the flagged triple-backtick blocks by adding the language tag "text" (i.e., change ``` to ```text) for the four occurrences of fenced code in the README so the markdown linter is satisfied and rendering improves; search for the plain ``` fence instances in the README and replace them with ```text for each block that contains plaintext lists or examples.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.memory-bank/tasks/1777-new-docs/readme.md:
- Line 104: The sentence "A3. **Custom services on ENSDb** — builders running or
consuming ENSDb to build custom ENS services on top of ENSDb. To access ENSDb
you need your own ENSNode via `Journey B`" is missing terminal punctuation after
the inline code; update that sentence to end with a period (or appropriate
punctuation) after `Journey B` so the paragraph is properly punctuated, locating
the text by the heading "A3. **Custom services on ENSDb**" and the inline code
token `Journey B`.
- Line 16: Rewrite the sentence that currently reads "Resolution on the ENS
Omnigraph is on the roadmap" to a positive, forward-looking statement
highlighting the benefit and novelty of combining indexed state and resolution
in one typed API; update the paragraph mentioning "ENS Omnigraph", "indexed
state and resolution converge in one typed surface", and the roadmap to instead
emphasize that ENS Omnigraph will soon provide integrated resolver values,
reverse resolution, and identity-style queries—framing this as an exciting
advancement that unifies indexed state and resolution into a single typed
developer experience.
---
Duplicate comments:
In @.memory-bank/tasks/1777-new-docs/readme.md:
- Line 154: Fix the inline typo "dont" to "don't" in the readme note and replace
the unresolved inline comment with a tracked TODO: add a clear checklist or task
entry (e.g., "TODO: consult `@shrugs` on ENS Omnigraph capabilities and finish
cookbook recipes") so the gap is visible and assignable; update the note in
.memory-bank/tasks/1777-new-docs/readme.md where the inline comment appears and
ensure it references `@shrugs` and the specific topic ("ENS Omnigraph capabilities
/ cookbook recipes") so it can be followed up.
- Around line 97-98: Replace the wordy and ungrammatical sentence "My assumption
is that we have 2 usecases for user to read our documentation" with a clear,
corrected version—change "2" to "two", "usecases" to "use cases", and "for user"
to "for users"; for example, update the README sentence to "There are two use
cases for users to read our documentation" (or equivalent concise phrasing) so
grammar and clarity are fixed.
- Line 120: There are several fenced code blocks missing language specifiers;
update each of the flagged triple-backtick blocks by adding the language tag
"text" (i.e., change ``` to ```text) for the four occurrences of fenced code in
the README so the markdown linter is satisfied and rendering improves; search
for the plain ``` fence instances in the README and replace them with ```text
for each block that contains plaintext lists or examples.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 33ef5f1f-c001-4d9b-85a8-65600aded25f
📒 Files selected for processing (1)
.memory-bank/tasks/1777-new-docs/readme.md
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 8
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/ensnode.io/src/content/docs/docs/build-with-ens/omnigraph/cookbook.mdx (1)
1-11: 🧹 Nitpick | 🔵 Trivial | ⚡ Quick winConsider deferring placeholder pages or hiding from navigation.
This page contains only a "Coming Soon" notice with no actual content. Since the PR is marked as Draft, consider:
- Preferred approach: Wait to add this page until the content is ready
- Alternative: If the page structure must be committed now, add
draft: trueto the frontmatter to hide it from production navigation:--- title: Cookbook description: Ready-to-use ENS Omnigraph query recipes. draft: true ---The "check back next week" message may become stale and misleading if the timeline changes.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/ensnode.io/src/content/docs/docs/build-with-ens/omnigraph/cookbook.mdx` around lines 1 - 11, This page is a placeholder with only a "Coming Soon" notice; either remove the page until content is ready or hide it from production by adding draft: true to the frontmatter (update the YAML block in the file that currently defines title and description) and remove/modify the "check back next week" sentence to avoid stale timelines; ensure the frontmatter now includes draft: true so the page is excluded from production navigation.docs/ensnode.io/src/content/docs/docs/self-host/index.mdx (1)
30-36:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUpdate LinkCard hrefs to use new route structure.
Lines 30 and 36 reference
/docs/deploying/dockerand/docs/deploying/terraform, which no longer exist. The correct routes are/docs/self-host/dockerand/docs/self-host/terraform(which do exist). No redirects are configured inastro.config.mjsfor these old paths.Proposed fix
-<LinkCard title="Deploy with Docker" href="/docs/deploying/docker" /> +<LinkCard title="Deploy with Docker" href="/docs/self-host/docker" /> ### Deploying with Terraform An example Terraform deployment reference is available, showing an example of deploying the full ENSNode suite on Render with AWS managed domain names. -<LinkCard title="Deploy with Terraform" href="/docs/deploying/terraform" /> +<LinkCard title="Deploy with Terraform" href="/docs/self-host/terraform" />🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/ensnode.io/src/content/docs/docs/self-host/index.mdx` around lines 30 - 36, Update the two LinkCard components that still point to the removed paths by changing their href props from "/docs/deploying/docker" and "/docs/deploying/terraform" to the new routes "/docs/self-host/docker" and "/docs/self-host/terraform" respectively; locate the LinkCard elements (title="Deploy with Docker" and title="Deploy with Terraform") and update only the href strings so the links point to the existing pages.
♻️ Duplicate comments (2)
docs/ensnode.io/src/content/docs/docs/build-with-ens/migrate-from-subgraph.mdx (1)
1-11: 🧹 Nitpick | 🔵 Trivial | ⚡ Quick winConsider deferring placeholder pages or hiding from navigation.
This migration guide placeholder has the same concern as the Cookbook page. Given that users transitioning from the ENS Subgraph would likely seek this documentation, publishing a placeholder without content may create frustration.
Consider the same options:
- Defer adding this page until migration content is ready
- Mark as draft using frontmatter:
draft: true🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/ensnode.io/src/content/docs/docs/build-with-ens/migrate-from-subgraph.mdx` around lines 1 - 11, The placeholder migration page is published empty and should be hidden until content is ready: update the page frontmatter by adding draft: true (or remove it from navigation/menus) so the page is not rendered in site navigation, or alternatively defer committing the file until the migration content is ready; target the document's frontmatter fields (e.g., title, description) and set draft: true to prevent publication.docs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/enssdk.mdx (1)
1-11: 🧹 Nitpick | 🔵 Trivial | ⚡ Quick winConsider deferring placeholder pages or hiding from navigation.
This is the third placeholder page with identical structure. While this pattern suggests intentional navigation structure creation, the same recommendation applies: either defer until content is ready or mark as draft to avoid publishing incomplete documentation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/enssdk.mdx` around lines 1 - 11, This placeholder docs page titled "enssdk (TypeScript)" should be marked as a draft or removed from the published navigation to avoid exposing incomplete content; update the frontmatter of enssdk.mdx to include a draft flag (e.g., draft: true) or otherwise remove it from the docs navigation/build configuration so the page remains hidden until content like createEnsNodeClient, gql.tada examples, and normalization utilities are ready for publication.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/ensnode.io/config/integrations/starlight/sidebar-topics/reference.ts`:
- Around line 43-45: Rename the MDX file that currently contains the typo and
update the sidebar link to match: change the file named
indexing-ens-compabile-onchain-names.mdx to
indexing-ens-compatible-onchain-names.mdx, then update the sidebar entry whose
link value is "/docs/reference/indexing-ens-compabile-onchain-names" to
"/docs/reference/indexing-ens-compatible-onchain-names" so the label "Indexing
ENS-Compatible Names" is consistent with the corrected filename and link; ensure
any imports or references to the old filename are updated accordingly.
In `@docs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/ensdb.mdx`:
- Line 7: Replace the time-sensitive callout text "Check back next week" with
neutral or explicit wording; locate the callout containing the string "Check
back next week" and change it to either "Check back soon" or an explicit date
(e.g., "Updated: YYYY-MM-DD") so the content doesn't age, and ensure the
surrounding sentence/CTA remains grammatically correct after the change.
In
`@docs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/enskit.mdx`:
- Line 10: The opening sentence is a fragment; reword it into a complete
sentence that clearly states the page purpose. Replace the fragment with a full
sentence that mentions enskit (the React toolkit for ENS) and what the page
covers (for example: setup with providers, the useOmnigraphQuery hook, and
working examples from the enskit-react-example app) so readers immediately
understand the scope.
In `@docs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/index.mdx`:
- Line 7: Replace the relative-time phrase "Check back next week" with a
timeless alternative (e.g., "Check back for updates" or "Content coming soon")
in the integrations page content so the message won't age; locate the string
"Check back next week" in the integrations page (the line containing "We're
actively working on this page right now. Check back next week for full
content!") and update it to a neutral, evergreen phrasing.
In
`@docs/ensnode.io/src/content/docs/docs/components/ensdb/integrations/ensnode.mdx`:
- Line 3: Update the page frontmatter description string that currently reads "A
directory of reference implementation of the ENSDb standard." to use the plural
form "reference implementations" so it becomes "A directory of reference
implementations of the ENSDb standard."; locate and edit the description entry
in the frontmatter (the line starting with description:) and replace the
singular noun accordingly.
In `@docs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/api.mdx`:
- Line 20: Remove the trailing slashes from internal markdown links that end
with "/docs/components/ensrainbow/concepts/label-sets-and-versioning/" and
"/docs/components/ensrainbow/usage/troubleshooting/" so they match the site's
trailingSlash: "never" setting; update the two link targets in the text to
"/docs/components/ensrainbow/concepts/label-sets-and-versioning" and
"/docs/components/ensrainbow/usage/troubleshooting" (and scan the same file for
any other internal links that end with a slash and strip it similarly).
In `@docs/ensnode.io/src/content/docs/docs/reference/index.mdx`:
- Line 11: Summary: The index description mentions "the roadmap" but no roadmap
exists; either link or remove it. Edit the sentence "Browse terminology, the
roadmap, REST and legacy Subgraph surfaces, and contributing guides." in
index.mdx: either replace "the roadmap" with a proper internal link/card to the
roadmap page (e.g., markdown/MDX link to the roadmap route) or remove "the
roadmap" from the list so the line reads "Browse terminology, REST and legacy
Subgraph surfaces, and contributing guides." Ensure the phrasing and punctuation
remain consistent with surrounding copy.
In
`@docs/ensnode.io/src/content/docs/docs/reference/mainnet-registered-subnames-of-subregistries.mdx`:
- Line 11: Replace the misspelled word "Regsitry" with "Registry" in the
sentence containing "example.base.eth being registered on both the mainnet
Regsitry and Basenames" so the user-facing text reads "...registered on both the
mainnet Registry and Basenames"; ensure the surrounding Markdown and link to
"Shadow Registry" remain unchanged.
---
Outside diff comments:
In `@docs/ensnode.io/src/content/docs/docs/build-with-ens/omnigraph/cookbook.mdx`:
- Around line 1-11: This page is a placeholder with only a "Coming Soon" notice;
either remove the page until content is ready or hide it from production by
adding draft: true to the frontmatter (update the YAML block in the file that
currently defines title and description) and remove/modify the "check back next
week" sentence to avoid stale timelines; ensure the frontmatter now includes
draft: true so the page is excluded from production navigation.
In `@docs/ensnode.io/src/content/docs/docs/self-host/index.mdx`:
- Around line 30-36: Update the two LinkCard components that still point to the
removed paths by changing their href props from "/docs/deploying/docker" and
"/docs/deploying/terraform" to the new routes "/docs/self-host/docker" and
"/docs/self-host/terraform" respectively; locate the LinkCard elements
(title="Deploy with Docker" and title="Deploy with Terraform") and update only
the href strings so the links point to the existing pages.
---
Duplicate comments:
In
`@docs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/enssdk.mdx`:
- Around line 1-11: This placeholder docs page titled "enssdk (TypeScript)"
should be marked as a draft or removed from the published navigation to avoid
exposing incomplete content; update the frontmatter of enssdk.mdx to include a
draft flag (e.g., draft: true) or otherwise remove it from the docs
navigation/build configuration so the page remains hidden until content like
createEnsNodeClient, gql.tada examples, and normalization utilities are ready
for publication.
In
`@docs/ensnode.io/src/content/docs/docs/build-with-ens/migrate-from-subgraph.mdx`:
- Around line 1-11: The placeholder migration page is published empty and should
be hidden until content is ready: update the page frontmatter by adding draft:
true (or remove it from navigation/menus) so the page is not rendered in site
navigation, or alternatively defer committing the file until the migration
content is ready; target the document's frontmatter fields (e.g., title,
description) and set draft: true to prevent publication.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 6f122dcd-b330-4d43-9c3c-2cea5b89c3ea
📒 Files selected for processing (97)
docs/ensnode.io/astro.config.mjsdocs/ensnode.io/config/integrations/starlight.tsdocs/ensnode.io/config/integrations/starlight/index.tsdocs/ensnode.io/config/integrations/starlight/sidebar-topics/build-with-ens.tsdocs/ensnode.io/config/integrations/starlight/sidebar-topics/components.tsdocs/ensnode.io/config/integrations/starlight/sidebar-topics/index.tsdocs/ensnode.io/config/integrations/starlight/sidebar-topics/reference.tsdocs/ensnode.io/config/integrations/starlight/sidebar-topics/self-host.tsdocs/ensnode.io/src/components/molecules/HeaderButtons.tsxdocs/ensnode.io/src/components/overrides/Hero.astrodocs/ensnode.io/src/content/docs/docs/build-with-ens/ai-llm.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/ensv2-readiness.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/hosted-instances.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/index.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/ensdb.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/enskit.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/enssdk.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/index.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/integrations/raw-graphql.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/migrate-from-subgraph.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/omnigraph/cookbook.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/omnigraph/index.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/omnigraph/schema-reference.mdxdocs/ensnode.io/src/content/docs/docs/build-with-ens/why-ensnode.mdxdocs/ensnode.io/src/content/docs/docs/components/ensadmin/contributing/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensadmin/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensadmin/overview/what-is-ensadmin.mdxdocs/ensnode.io/src/content/docs/docs/components/ensapi/contributing/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensapi/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensapi/reference/api-reference.mdxdocs/ensnode.io/src/content/docs/docs/components/ensapi/usage/configuration.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/concepts/database-schemas.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/concepts/glossary.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/concepts/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/integrations/ensnode.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/integrations/future-possibilities.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/usage/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/usage/sdk.mdxdocs/ensnode.io/src/content/docs/docs/components/ensdb/usage/sql.mdxdocs/ensnode.io/src/content/docs/docs/components/ensindexer/concepts/startup-sequence.mdxdocs/ensnode.io/src/content/docs/docs/components/ensindexer/contributing/creating-a-plugin.mdxdocs/ensnode.io/src/content/docs/docs/components/ensindexer/contributing/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensindexer/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensindexer/usage/configuration.mdxdocs/ensnode.io/src/content/docs/docs/components/ensindexer/usage/management.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/architecture.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/creating-files.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/data-model.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/glossary.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/label-sets-and-versioning.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/performance.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/typescript-interfaces.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/unknown-labels.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/concepts/versioning.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/contributing/building.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/contributing/cli-reference.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/contributing/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/contributing/local-development.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/contributing/service-management.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/contributing/system-requirements.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/deploying/docker.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/deploying/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/deploying/railway.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/faq.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/api.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/available-label-sets.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/client-sdk.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/configuration.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/hosted-ensrainbow-instances.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/index.mdxdocs/ensnode.io/src/content/docs/docs/components/ensrainbow/usage/troubleshooting.mdxdocs/ensnode.io/src/content/docs/docs/components/index.mdxdocs/ensnode.io/src/content/docs/docs/reference/contributing/building.mdxdocs/ensnode.io/src/content/docs/docs/reference/contributing/index.mdxdocs/ensnode.io/src/content/docs/docs/reference/contributing/prs.mdxdocs/ensnode.io/src/content/docs/docs/reference/contributing/releases.mdxdocs/ensnode.io/src/content/docs/docs/reference/contributing/rest-api-docs.mdxdocs/ensnode.io/src/content/docs/docs/reference/index.mdxdocs/ensnode.io/src/content/docs/docs/reference/mainnet-registered-subnames-of-subregistries.mdxdocs/ensnode.io/src/content/docs/docs/reference/querying-best-practices.mdxdocs/ensnode.io/src/content/docs/docs/reference/rest-api.mdxdocs/ensnode.io/src/content/docs/docs/reference/roadmap.mdxdocs/ensnode.io/src/content/docs/docs/reference/subgraph-legacy/subgraph-dependents.mdxdocs/ensnode.io/src/content/docs/docs/reference/subgraph-legacy/with-ensjs.mdxdocs/ensnode.io/src/content/docs/docs/reference/subgraph-legacy/with-viem.mdxdocs/ensnode.io/src/content/docs/docs/reference/terminology.mdxdocs/ensnode.io/src/content/docs/docs/reference/what-is-ensnode.mdxdocs/ensnode.io/src/content/docs/docs/reference/what-is-the-ens-subgraph.mdxdocs/ensnode.io/src/content/docs/docs/running/ens-test-env.mdxdocs/ensnode.io/src/content/docs/docs/running/index.mdxdocs/ensnode.io/src/content/docs/docs/self-host/docker.mdxdocs/ensnode.io/src/content/docs/docs/self-host/index.mdxdocs/ensnode.io/src/content/docs/docs/self-host/terraform.mdxdocs/ensnode.io/src/styles/starlight.css
💤 Files with no reviewable changes (3)
- docs/ensnode.io/src/content/docs/docs/running/index.mdx
- docs/ensnode.io/config/integrations/starlight.ts
- docs/ensnode.io/src/content/docs/docs/running/ens-test-env.mdx
sevenzing
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
in this PR I just moved a lot of content to align with new outlined described in ensnode.io docs improvements #2068
Content almost isnt modified, we will do it in next PR's
Screenshots