diff --git a/_deprecated/cel2/operators/migrate-node.mdx b/_deprecated/cel2/operators/migrate-node.mdx index f0f87f7ad..5dd2c818d 100644 --- a/_deprecated/cel2/operators/migrate-node.mdx +++ b/_deprecated/cel2/operators/migrate-node.mdx @@ -130,7 +130,7 @@ When the hardfork block number is reached, complete the migration using either D ### Hardware Requirements -- Make sure you have enough storage to accomodate 2x the pre-hardfork chaindata. Chaindata size can vary, so please double check your node. +- Make sure you have enough storage to accommodate 2x the pre-hardfork chaindata. Chaindata size can vary, so please double check your node. - We recommend using local storage for the source and destination datadirs. - 16GB+ RAM recommended diff --git a/_deprecated/cel2/operators/run-node.mdx b/_deprecated/cel2/operators/run-node.mdx index a4590b76b..1dadb4418 100644 --- a/_deprecated/cel2/operators/run-node.mdx +++ b/_deprecated/cel2/operators/run-node.mdx @@ -43,7 +43,7 @@ See the [README](https://github.com/celo-org/celo-l2-node-docker-compose/blob/ma **Docker Desktop on MacOS** -You will most likely need to increase the virtual disk limit in order to accomodate the chaindata directory. This can be done by opening Docker Desktop, going to Settings -> Resources -> Advanced and increasing the disk image size. +You will most likely need to increase the virtual disk limit in order to accommodate the chaindata directory. This can be done by opening Docker Desktop, going to Settings -> Resources -> Advanced and increasing the disk image size. ### Running a Full Node diff --git a/_deprecated/what-is-celo/joining-celo/code-of-conduct.mdx b/_deprecated/what-is-celo/joining-celo/code-of-conduct.mdx index f888f883f..23e25316d 100644 --- a/_deprecated/what-is-celo/joining-celo/code-of-conduct.mdx +++ b/_deprecated/what-is-celo/joining-celo/code-of-conduct.mdx @@ -1,4 +1,4 @@ --- title: Code of Conduct -url: https://github.com/celo-org/website/blob/master/src/content/code-of-conduct.md +url: https://celo.org/code-of-conduct --- \ No newline at end of file diff --git a/_deprecated/what-is-celo/joining-celo/index.mdx b/_deprecated/what-is-celo/joining-celo/index.mdx index f76476f28..443e0dbef 100644 --- a/_deprecated/what-is-celo/joining-celo/index.mdx +++ b/_deprecated/what-is-celo/joining-celo/index.mdx @@ -44,7 +44,7 @@ Follow to stay updated with the latest news about Celo. - [Celo on X](https://x.com/Celo) - [Celo Devs on X](https://x.com/CeloDevs) - [cLabs on X](https://x.com/cLabs) -- [Warpcast](https://warpcast.com/~/users/celo) +- [Farcaster](https://farcaster.xyz/celo) - [Reddit](https://www.reddit.com/r/celo/) - [GitHub](https://github.com/celo-org/celo-monorepo) - [Medium Blogs](https://medium.com/@celoorg) diff --git a/_deprecated/what-is-celo/using-celo/manage/self-custody.mdx b/_deprecated/what-is-celo/using-celo/manage/self-custody.mdx index 32b774006..66ae906e9 100644 --- a/_deprecated/what-is-celo/using-celo/manage/self-custody.mdx +++ b/_deprecated/what-is-celo/using-celo/manage/self-custody.mdx @@ -432,4 +432,4 @@ Finally, request that the `ReleaseGold` contract transfer an amount to your bene celocli releasecelo:withdraw --contract $CELO_RG_ADDRESS --useLedger --value ``` -To vote with any CELO in your beneficiary account, you'll want to register it as a Locked CELO Acccount, authorize a new vote signing key for it, then lock CELO. \ No newline at end of file +To vote with any CELO in your beneficiary account, you'll want to register it as a Locked CELO Account, authorize a new vote signing key for it, then lock CELO. \ No newline at end of file diff --git a/contribute-to-celo/builders.mdx b/contribute-to-celo/builders.mdx index 2ac4e8a85..a093ef830 100644 --- a/contribute-to-celo/builders.mdx +++ b/contribute-to-celo/builders.mdx @@ -1,28 +1,23 @@ --- -title: Celo Builders -sidebarTitle: "Builders" +title: Builders --- Whether you're just starting or are an experienced developer, Celo offers a variety of ways for you to engage and grow your projects. ---- - ## Builders in the Celo Ecosystem -The Celo Builder Community is a global network of developers, entrepreneurs, and enthusiasts dedicated to building a regenerative digital economy that promotes prosperity for all. By joining, you'll have the opportunity to create onchain apps and tools that drive financial inclusion and support sustainable development on a global scale. +The Celo Builder Community is a global network of developers, entrepreneurs, and enthusiasts dedicated to building a regenerative digital economy that promotes prosperity for all. By joining, you'll have the opportunity to create onchain apps and tools that drive financial inclusion and support sustainable development on a global scale. Make sure to check out the local nodes to connect with builders in your region and attend networking events. ## How to Get Involved There are several ways to get started as a builder on Celo: -* **Join the Builder Community**: Connect with like-minded individuals on platforms like [Discord](https://discord.com/invite/celo) and the [Celo Forum](https://forum.celo.org/). You'll find channels dedicated to everything from smart contract development to mobile-first dApp creation. +* [**Sign up to Proof of Ship**](https://celo-devs.beehiiv.com/subscribe): Prove their impact, showcase progress, and earn rewards. Your onchain reputation unlocks access to grants, retro funding, airdrops, and other funding opportunities. -* **Participate in Hackathons**: Hackathons are an excellent way to challenge your skills, collaborate with other developers, and potentially win rewards for innovative solutions. Find ecosystem events on our community [event platform](https://celo.stand.lemonade.social/events). +* **Join the Builder Community**: Connect with like-minded individuals on platforms like [Discord](https://discord.com/invite/celo) and the [Celo Forum](https://forum.celo.org/). You'll find channels dedicated to everything from smart contract development to mobile-first dApp creation. -* **Contribute to Open Source Projects**: You can [contribute](/contribute-to-celo/contributors/overview) directly to Celo’s open-source codebase or build complementary projects. +* **Join the office hour**: Office Hours are an excellent way to learn about opportunities in the ecosystem, get feedback on your project and connect with the community. Find ecosystem events on our community [event platform](https://celo.stand.lemonade.social/events). * **Apply for Grants**: Celo has grants programs, like [Prezenti](https://www.prezenti.xyz/) and [Celo Public Goods](https://www.celopg.eco/) which supports projects that align with its mission to provide financial services to the next billion people. * **Apply for an Accelerator**: Check out [Celo Camp](https://www.celocamp.com/), the accelerator focused on the Celo ecosystem. If you are not yet at that stage, they also offer [Startup Pathway](https://startup-pathway.mykajabi.com/) a program, that leads you through your first steps to becoming a founder. - -* **Access Exclusive Resources**: [Register as a Celo Builder](https://docs.google.com/forms/d/e/1FAIpQLSemO5Kbf8fzq70AtiZEPRkk040MmpmmyhRqeurAwuVWUg63tQ/viewform) to gain access to resources and support available to active builders on Celo. diff --git a/contribute-to-celo/code-of-conduct.mdx b/contribute-to-celo/code-of-conduct.mdx index f888f883f..23e25316d 100644 --- a/contribute-to-celo/code-of-conduct.mdx +++ b/contribute-to-celo/code-of-conduct.mdx @@ -1,4 +1,4 @@ --- title: Code of Conduct -url: https://github.com/celo-org/website/blob/master/src/content/code-of-conduct.md +url: https://celo.org/code-of-conduct --- \ No newline at end of file diff --git a/contribute-to-celo/community-rpc-nodes/registering-as-rpc-node.mdx b/contribute-to-celo/community-rpc-nodes/registering-as-rpc-node.mdx index a069ce7cb..0a16df387 100644 --- a/contribute-to-celo/community-rpc-nodes/registering-as-rpc-node.mdx +++ b/contribute-to-celo/community-rpc-nodes/registering-as-rpc-node.mdx @@ -5,8 +5,6 @@ sidebarTitle: "Register as a Community RPC Node" Step-by-step instructions on how to register a RPC node on chain to be eligible for rewards. ---- - ****Terminology**** diff --git a/contribute-to-celo/community-rpc-nodes/validator-rpc-faq.mdx b/contribute-to-celo/community-rpc-nodes/validator-rpc-faq.mdx index d703c3be1..8c8605e82 100644 --- a/contribute-to-celo/community-rpc-nodes/validator-rpc-faq.mdx +++ b/contribute-to-celo/community-rpc-nodes/validator-rpc-faq.mdx @@ -44,7 +44,7 @@ No, there will no longer be any validator nodes on the L2. -Rewards are limited to validators who register as a community RPC provider. There is a proposal in draft that will outline all thhe details on the monitoring. +Rewards are limited to validators who register as a community RPC provider. There is a proposal in draft that will outline all the details on the monitoring. diff --git a/contribute-to-celo/contributors/code-contributors.mdx b/contribute-to-celo/contributors/code-contributors.mdx index 2a27b055c..affca70d1 100644 --- a/contribute-to-celo/contributors/code-contributors.mdx +++ b/contribute-to-celo/contributors/code-contributors.mdx @@ -7,14 +7,12 @@ import {ColoredText} from "/snippets/ColoredText.jsx"; How to contribute to open source projects and further the growth of the Celo ecosystem. ---- - ## How to Contribute Contributing to the Celo ecosystem through open-source projects is a valuable way to support public goods and connect with the community. Whether you're new to open-source or an experienced contributor, the guidelines below will help you get started. -For quick questions, check the docs or create a ticket in the [Celo Discord](https://discord.com/invite/celo). Please avoid filing an issue on GitHub just to ask a question; using the resources above will provide faster responses. +For quick questions, chat with the assistant in the docs or reach out in the [Celo Discord](https://discord.com/invite/celo). Please avoid filing an issue on GitHub just to ask a question; using the resources above will provide faster responses. ### Prerequisites diff --git a/contribute-to-celo/contributors/documentation-contributors.mdx b/contribute-to-celo/contributors/documentation-contributors.mdx index 6784e7e20..906869313 100644 --- a/contribute-to-celo/contributors/documentation-contributors.mdx +++ b/contribute-to-celo/contributors/documentation-contributors.mdx @@ -5,8 +5,6 @@ og:description: How to contribute to the Celo documentation and help improve the Help improve the Celo ecosystem by contributing to documentation and educational resources. ---- - import {YouTube} from '/snippets/YouTube.jsx'; ## Why Documentation Matters @@ -30,14 +28,7 @@ There are many ways to improve Celo documentation, regardless of your technical - Protocol specifications and architecture guides - Integration guides and code samples -### 2. User Guides and Tutorials - -- Step-by-step tutorials for beginners -- How-to guides for specific tasks -- Troubleshooting guides and FAQs -- Explainer articles for key concepts - -### 3. Documentation Maintenance +### 2. Documentation Maintenance - Update outdated information - Fix broken links and references @@ -50,12 +41,11 @@ There are many ways to improve Celo documentation, regardless of your technical To edit an existing page in the documentation: -1. Navigate to the page you want to edit at [docs.celo.org](/) -2. Click **Edit this page** at the bottom of the page -3. Make your changes directly on GitHub -4. Write a clear commit message describing your changes -5. Select "Create a new branch and start a pull request" -6. Describe your changes in the Pull Request (PR) +1. Fork the [Celo Docs repository](https://github.com/celo-org/docs) +2. Create a branch naming it after the changes you want to make +3. Write a clear commit message describing your changes +4. Create a Pull Request (PR) +6. Describe your changes in the PR 7. Tag appropriate reviewers 8. Wait for approval and for the site build checks to pass before merging @@ -66,7 +56,7 @@ To add a new page to the documentation: 1. Fork the [Celo Docs repository](https://github.com/celo-org/docs) 2. Add or delete pages in the appropriate location 3. Create a PR with your changes for the live version of the site -4. Update the "sidebars.js" file in the main folder: +4. Update the "docs.json" file in the main folder: - This file controls the navigation menu on the left side of the docs site - Add or remove the appropriate files from the list diff --git a/contribute-to-celo/contributors/overview.mdx b/contribute-to-celo/contributors/overview.mdx index b19462313..3dea7da1b 100644 --- a/contribute-to-celo/contributors/overview.mdx +++ b/contribute-to-celo/contributors/overview.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Overview" og:description: Join a community of developers, designers, dreamers, and doers building prosperity for everyone. --- -Celo is open source and welcomes participation from everyone. We strive to fulfill our [Community Tenets](https://celo.org/community) by being inclusive and empowering. All contributors must abide by Celo's [Code of Conduct](https://celo.org/code-of-conduct). +Celo is open source and welcomes participation from everyone. We strive to be inclusive and empowering. All contributors must abide by Celo's [Code of Conduct](https://celo.org/code-of-conduct). ## Ways to Contribute @@ -35,15 +35,6 @@ For effective contributions: - Explain dependencies and breaking changes - Include relevant tests and documentation updates -## Tutorial Contributions - -Share your Celo experience through blog posts: - -- Create files in the [blog directory](https://github.com/celo-org/docs/tree/main/blog) using format `YYYY-MM-DD-post-name.md` -- Include proper front matter (title, description, author info) -- Use `` to define post summaries -- For images, create a folder with the same naming convention containing your post (as index.md) and assets - For questions or discussions, use the [Celo Forum](https://forum.celo.org/) or [Discord](https://chat.celo.org/). \ No newline at end of file diff --git a/contribute-to-celo/index.mdx b/contribute-to-celo/index.mdx index 613ec41a3..43143bf99 100644 --- a/contribute-to-celo/index.mdx +++ b/contribute-to-celo/index.mdx @@ -6,28 +6,23 @@ sidebarTitle: "Joining Celo" Explore the many ways to engage with the Celo ecosystem and contribute to its growth. ---- - Welcome to the Celo Ecosystem! Whether you're a user, developer, founder, or contributor, there are numerous ways to engage and make a meaningful impact. This guide will help you explore the various opportunities available within the Celo community, from using innovative applications to contributing to open-source projects, and participating in governance. Dive in to discover how you can be a part of Celo's mission to create a more inclusive financial system. ### As a User -- [**Explore Projects on Celo:**](/showcase) Start using and engaging with Celo apps. -- [**Follow updates from the Celo Foundation on Medium**](https://medium.com/@celoorg) +- [**Explore Projects on Celo:**](https://celo.org/ecosystem) Start using and engaging with Celo apps. +- [**Follow updates from the Celo Foundation on Twitter**](https://x.com/Celo) ### As a Builder -- [**Register as an active Celo builder:**](https://docs.google.com/forms/d/e/1FAIpQLSemO5Kbf8fzq70AtiZEPRkk040MmpmmyhRqeurAwuVWUg63tQ/viewform) Access exclusive resources and support. +- **Register your project** in our [ecosystem database](https://www.karmahq.xyz/community/celo) and get ready to apply for [ecosystem builder and grant programs.](https://www.celopg.eco/programs) - [**Join our builder community:**](/contribute-to-celo/builders) Connect with other builders in the ecosystem. - [**Contribute to open source projects:**](/contribute-to-celo/contributors/code-contributors) Help grow Celo by contributing to key projects. - [**Get involved in a local chapter:**](/contribute-to-celo/daos) Attend in-person workshops for mentoring and support. - [**Participate in Celo Public Goods:**](https://www.celopg.eco/) Explore ongoing funding rounds. -- [**Get your page added**](https://github.com/celo-org/docs/blob/main/src/data/users.tsx) to our [**dApp showcase page**](/showcase). -- [**Introduce your project**](https://forum.celo.org/) in the [**Celo Forum**](https://forum.celo.org/) in the founders' category. +- **Introduce your project** in the [**Celo Forum**](https://forum.celo.org/) in the founders' category. - [**Apply to Celo Camp:**](https://www.celocamp.com/) Join the accelerator focused on scaling apps on Opera MiniPay. -- [**Engage with Celo DAOs:**](/contribute-to-celo/daos) Gain user feedback, access networking opportunities, and validate your project. -- [**Apply for Prezenti Grants:**](https://www.prezenti.xyz/) Explore grant opportunities. -- Check out community resources for helpful tips to raise capital. +- **Explore grant opportunities:** Apply for [Prezenti Grants](https://www.prezenti.xyz/) . ### As a Contributor @@ -45,14 +40,13 @@ Follow to stay updated with the latest news about Celo. - [Celo on X](https://x.com/Celo) - [Celo Devs on X](https://x.com/CeloDevs) - [cLabs on X](https://x.com/cLabs) -- [Warpcast](https://warpcast.com/~/users/celo) +- [Farcaster](https://farcaster.xyz/celo) - [Reddit](https://www.reddit.com/r/celo/) -- [GitHub](https://github.com/celo-org/celo-monorepo) +- [GitHub](https://github.com/celo-org) - [Medium Blogs](https://medium.com/@celoorg) - [LinkedIn](https://www.linkedin.com/company/celo-foundation) - [Instagram](https://www.instagram.com/celoorg/) -- [YouTube](https://youtube.com/channel/UCCZgos_YAJSXm5QX5D5Wkcw) -- [Twitch](https://www.twitch.tv/celoorg) +- [YouTube](https://www.youtube.com/@CeloOrg) ## Discussions diff --git a/contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils.mdx b/contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils.mdx index 8936f8508..b30bd62a6 100644 --- a/contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils.mdx +++ b/contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils.mdx @@ -49,11 +49,11 @@ For all releases: - Each package’s `CHANGELOG.md` file, as mentioned above - Github releases page, as mentioned above -- [Discord](https://chat.celo.org): #developer-chat, #mainnet, and #sdk +- [Discord](https://chat.celo.org): #developer-news For major releases: -- Twitter: [@CeloDevs](https://x.com/CeloDevs) +- Twitter: [@cLabs](https://x.com/cLabs) - Mailing list: cLabs’ Tech Sync - [Celo Forum](https://forum.celo.org/) @@ -88,8 +88,3 @@ Vulnerabilities in any of these releases should be disclosed according to the [s - @celo/mobile - Dappkit relies on this - Celocli - All the packages under the ["SDK" folder](https://github.com/celo-org/developer-tooling/tree/master/packages/sdk) -- These all rely on each other quite a bit, so triple-check that these packages weren’t affected by a change in another. - -## Dependents - -- Celocli -- All the packages under the ["SDK" folder](https://github.com/celo-org/developer-tooling/tree/master/packages/sdk) \ No newline at end of file diff --git a/contribute-to-celo/release-process/blockchain-client.mdx b/contribute-to-celo/release-process/blockchain-client.mdx index 8323c8a52..c0712f7e5 100644 --- a/contribute-to-celo/release-process/blockchain-client.mdx +++ b/contribute-to-celo/release-process/blockchain-client.mdx @@ -98,4 +98,4 @@ If the issue is exploitable and mitigations are not readily available, a patch s ## Vulnerability Disclosure -Vulnerabilities in `celo-blockchain` releases should be disclosed according to the [security policy](https://github.com/celo-org/celo-blockchain/blob/master/SECURITY.md)e \ No newline at end of file +Vulnerabilities in `celo-blockchain` releases should be disclosed according to the [security policy](https://github.com/celo-org/celo-blockchain/blob/master/SECURITY.md). \ No newline at end of file diff --git a/contribute-to-celo/release-process/index.mdx b/contribute-to-celo/release-process/index.mdx index 7c677376e..f16464250 100644 --- a/contribute-to-celo/release-process/index.mdx +++ b/contribute-to-celo/release-process/index.mdx @@ -4,8 +4,6 @@ sidebarTitle: "Overview" og:description: Overview of the release process for updates to the Celo platform. --- - - Overview of the release process for updates to the Celo platform. diff --git a/home/manage/self-custody.mdx b/home/manage/self-custody.mdx index d5b67a5c1..a4ae254d2 100644 --- a/home/manage/self-custody.mdx +++ b/home/manage/self-custody.mdx @@ -433,4 +433,4 @@ Finally, request that the `ReleaseGold` contract transfer an amount to your bene celocli releasecelo:withdraw --contract $CELO_RG_ADDRESS --useLedger --value ``` -To vote with any CELO in your beneficiary account, you'll want to register it as a Locked CELO Acccount, authorize a new vote signing key for it, then lock CELO. \ No newline at end of file +To vote with any CELO in your beneficiary account, you'll want to register it as a Locked CELO Account, authorize a new vote signing key for it, then lock CELO. \ No newline at end of file diff --git a/infra-partners/operators/migrate-node.mdx b/infra-partners/operators/migrate-node.mdx index cc959454a..3b5ca0856 100644 --- a/infra-partners/operators/migrate-node.mdx +++ b/infra-partners/operators/migrate-node.mdx @@ -130,7 +130,7 @@ When the hardfork block number is reached, complete the migration using either D ### Hardware Requirements -- Make sure you have enough storage to accomodate 2x the pre-hardfork chaindata. Chaindata size can vary, so please double check your node. +- Make sure you have enough storage to accommodate 2x the pre-hardfork chaindata. Chaindata size can vary, so please double check your node. - We recommend using local storage for the source and destination datadirs. - 16GB+ RAM recommended diff --git a/infra-partners/operators/run-node.mdx b/infra-partners/operators/run-node.mdx index 24356ddcc..5987fcd8a 100644 --- a/infra-partners/operators/run-node.mdx +++ b/infra-partners/operators/run-node.mdx @@ -43,7 +43,7 @@ See the [README](https://github.com/celo-org/celo-l2-node-docker-compose/blob/ma **Docker Desktop on MacOS** -You will most likely need to increase the virtual disk limit in order to accomodate the chaindata directory. This can be done by opening Docker Desktop, going to Settings -> Resources -> Advanced and increasing the disk image size. +You will most likely need to increase the virtual disk limit in order to accommodate the chaindata directory. This can be done by opening Docker Desktop, going to Settings -> Resources -> Advanced and increasing the disk image size. ### Running a Full Node