docs/edfp: new delegation program description#2049
Conversation
WalkthroughA new sidebar entry for the "Celestia Foundation Ecosystem Delegation Program" was added to the documentation configuration. Additionally, a comprehensive markdown document detailing the program's structure, eligibility, application process, and participation tracks was introduced under the community section. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Sidebar (Docs)
participant Delegation Program Doc
User->>Sidebar (Docs): Access Community section
Sidebar (Docs)->>User: Show "Foundation Ecosystem Delegation Program" link
User->>Delegation Program Doc: Open program documentation
Delegation Program Doc->>User: Display program overview, eligibility, tracks, and instructions
Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (10)
community/foundation-ecosystem-delegation-program.md (10)
3-24: Check Table of Contents accuracy.
The ToC entries align with section headings. Ensure that Vitepress’s slug rules handle special characters (e.g., "&", "/") correctly. For readability and to satisfy markdownlint MD058, consider adding a blank line before line 4 and after line 24.
25-31: Surround program overview table with blank lines.
To comply with markdownlint MD058 and improve readability, insert a blank line before the table at line 27 and after line 31. Additionally, you may standardize the month range to something like "Jul–Dec 2025" for conciseness.
34-46: Link Code of Conduct & hyphenate "post-mortem".
- Change "post mortem" to "post-mortem" for consistency.
- Hyperlink "Celestia.org Code of Conduct" to
/community/cocso readers can quickly access it.🧰 Tools
🪛 LanguageTool
[misspelling] ~40-~40: This expression is normally spelled as one or with a hyphen.
Context: ... 1, a public forum post with a detailed post mortem is required) | | Independence | Not ass...(EN_COMPOUNDS_POST_MORTEM)
53-55: Clarify the background section.
The description of the pilot duration and track selection is combined in one sentence. Splitting into two sentences—one for timeline and one for track requirements—would improve clarity.
58-85: Review Mamo-Users requirements & metrics.
- Ensure the "power user" definition is precise enough for reporting.
- Link "CC0" to the official Creative Commons page.
- Surround each table in this block with blank lines to satisfy MD058.
🧰 Tools
🪛 LanguageTool
[style] ~75-~75: The wording of this phrase can be improved.
Context: ...ates in Q&A, and responds to surveys to make products better | | Creates & Shares Content | Publ...(MAKE_STYLE_BETTER)
86-98: Enhance example submission formatting.
Add blank lines before and after the<details>block for readability. Consider shortening the<summary>text to “Example: Mamo-Users Track” for brevity.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
97-97: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
102-150: Revise Bootcamp & Mammothon guidelines.
- For accessibility, consider replacing "&" with "and" in headings.
- Link to any referenced hackathon or bootcamp resource pages.
- Surround all tables and code blocks with blank lines (MD058).
151-163: Consistent example formatting.
As with the previous track, insert blank lines around the<details>block and update the<summary>to “Example: Bootcamp & Mammothon Track” for consistency.🧰 Tools
--- ## R&D Rules & Requi...🪛 LanguageTool
[style] ~162-~162: This phrase is redundant. Consider writing “outcomes”.
Context: ...n-source all demo projects
• Publish final outcomes |(FINAL_END)
🪛 markdownlint-cli2 (0.17.2)
162-162: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
167-199: Clarify R&D track details.
- Define "CIPs" on first mention or link to the official CIP documentation.
- Link to sample public-goods tooling repositories if available.
- Surround tables with blank lines for markdownlint compliance.
201-227: Convert bold text to headings for examples.
Lines 204, 212, and 220 use bold emphasis as pseudo-headings (MD036). Convert them into markdown headings, for example:- **1. CIP: "Dynamic Data Availability Fees"** + #### 1. CIP: "Dynamic Data Availability Fees"This improves accessibility and lint compliance.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
204-204: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
212-212: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
220-220: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
226-226: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.vitepress/config.ts(1 hunks)community/foundation-ecosystem-delegation-program.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
community/foundation-ecosystem-delegation-program.md
[misspelling] ~40-~40: This expression is normally spelled as one or with a hyphen.
Context: ... 1, a public forum post with a detailed post mortem is required) | | Independence | Not ass...
(EN_COMPOUNDS_POST_MORTEM)
[style] ~75-~75: The wording of this phrase can be improved.
Context: ...ates in Q&A, and responds to surveys to make products better | | Creates & Shares Content | Publ...
(MAKE_STYLE_BETTER)
[style] ~162-~162: This phrase is redundant. Consider writing “outcomes”.
Context: ...n-source all demo projects
• Publish final outcomes |
(FINAL_END)
🪛 markdownlint-cli2 (0.17.2)
community/foundation-ecosystem-delegation-program.md
97-97: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
162-162: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
204-204: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
212-212: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
220-220: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
226-226: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
🔇 Additional comments (3)
.vitepress/config.ts (1)
863-866: Confirm sidebar link for new program.
The new "Celestia Foundation Ecosystem Delegation Program" entry is correctly placed under the Community section. Please verify that the filecommunity/foundation-ecosystem-delegation-program.mdexists at the specified path and that the sidebar link renders properly in the documentation preview.community/foundation-ecosystem-delegation-program.md (2)
1-2: Validate document title formatting.
The H1 heading clearly names the program. If you need a custom anchor, consider adding an explicit ID (e.g.,{#foundation-ecosystem-delegation-program}). Otherwise, confirm that Vitepress’s default slug generation matches your link targets.
49-52: Validate application form URL.
Please confirm that the Google Forms link is active and correct. Consider adding a note on expected confirmation or response time to set clear applicant expectations.
2 participants
Overview
This new program outlines the rules and description + a form for our applicants
Summary by CodeRabbit
New Features
Documentation