4 |
5 | **Once a project's first milestone has been accepted**, we intend to help teams acknowledge their grant publicly while observing the foundation’s guidelines.
6 |
7 | To that end, we’ve created a badge for grant recipients. This is available for download in four formats under [web3.foundation/grants/badge](https://web3.foundation/grants/badge).
8 |
9 | *Before you begin using the badge, please note the following points:*
10 |
11 | - Use of the Grants Program badge is reserved for [Level 2 and 3 grants](https://github.com/w3f/Grants-Program/blob/master/README.md#level_slider-levels).
12 | - Grants are awarded **for specific projects**, not to teams in general as a blanket endorsement.
13 | - Web3 Foundation and its grants program **don’t broker partnerships or joint ventures**, or cosign wholesale any external team’s work. Bearing that in mind, **the badge should only be displayed in project-specific contexts.**
14 | - Please **do**: display the badge
15 | - in a GitHub repository that contains code connected with the grant project,
16 | - on any project-specific webpage **that specifically concerns the deliverables completed as part of the grant**, or
17 | - when appropriate, in a tweet or blog post announcing your grant in a project-specific context.
18 | - Please **don’t**:
19 | - display the badge on your team or project's landing page,
20 | - use the badge before your first milestone has been accepted,
21 | - add it to any social media profiles, or
22 | - use it in any other context that could misrepresent your relationship with the Web3 Foundation.
23 |
24 |
25 | Also, please don't use the **name or logo of the Web3 Foundation** in any context that could misrepresent your relationship with Web3 Foundation. Infringement of these guidelines can result in an immediate annulment of the grant.
26 |
27 | In case of any questions, please don’t hesitate to reach out to us at grantsPR@web3.foundation.
28 |
--------------------------------------------------------------------------------
/docs/Support Docs/grant_guidelines_per_category.md:
--------------------------------------------------------------------------------
1 | # Grant Guidelines for Most Popular Grant Categories
2 |
3 | While we ask teams to provide details of their envisioned solution, we are aware that precise implementation might slightly differ from the initial specification. Should there be large deviations from the original plan, please communicate this to the Grants Team ahead of time.
4 |
5 | The list below serves only as a guide and is not exhaustive.
6 |
7 | ## Runtime Modules/Chains
8 |
9 | ### Applies to
10 |
11 | - Building/extending a Substrate pallet
12 |
13 | ### Requirements
14 |
15 | - List the publicly exposed methods
16 | - For each method, specify (to the best of present knowledge):
17 | - Method signature (incl. parameters with their types, return type)
18 | - Short description (code template)
19 | - Runtime Storage defined by your module
20 | - [Use case diagram](https://www.wikiwand.com/en/Use_case_diagram) with e.g. UML or SysML (or similar tool demonstrating how external users/system components interact with one another)
21 |
22 |
23 | ## Development Tools
24 |
25 | ### Applies to
26 |
27 | - CLI tools
28 | - IDE / IDE plugin
29 |
30 | ### Requirements
31 |
32 | - State what programming language you'll use
33 | - Describe the commands that you want to make available to the users:
34 | - Name
35 | - Parameters
36 | - Result (value returned / file created or modified / application started etc.)
37 |
38 |
39 | ## UI Development
40 |
41 | ### Applies to
42 |
43 | - Building a web application with front-end components
44 | - Developing a mobile app
45 |
46 | ### Requirements
47 |
48 | - Provide mockups and/or wireframes (e.g. Figma)
49 | - List frameworks & tools for development & testing (e.g. React Native, Angular)
50 |
51 | ## Backend Development
52 |
53 | ### Applies to
54 |
55 | - Building a service/mobile app/webapp that relies on a back-end component
56 |
57 | ### Requirements
58 |
59 | - State what language & framework you'll use (e.g. python with Django, Rust with Rocket)
60 | - Define your database requirements and which system you'll use
61 | - Choose how & where will your backend be hosted (cloud provider, IPFS, localhost?)
62 | - Consider scaling & how you plan to handle it
63 | - Consider CI/CD
64 | - If you are (planning on) hosting the backend yourself, consider adding a [security.txt](https://securitytxt.org/) file so people can get in touch with you regarding (potential) security issues
65 | - Provide a link to your Github repository if you already have the structure in place
66 |
67 |
68 | ## Cryptography
69 |
70 | ### Applies to
71 |
72 | - New crypto library
73 | - Extending existing library's functionalities
74 |
75 | ### Requirements
76 |
77 | - Specify what programming language you'll use
78 | - Provide any publications/papers you will base your work on
79 | - Research other crypto libraries providing similar functionalities. State whether/how you plan to use their work. If they don't suit your needs, provide a detailed explanation why and what's missing
80 | - List any existing crypto libraries that you will use as reference implementation (e.g. in a different language)
81 |
82 | ## Research
83 |
84 | ### Applies to
85 |
86 | - Research projects
87 |
88 | ### Requirements
89 |
90 | - Specify the problem(s) that you want to investigate, and why these are important.
91 | - Declare the research questions/hypothesis.
92 | - State the methodology that will be applied.
93 | - Explain how the data will be collected and the analysis procedures.
94 | - Outline the expected results and how they would be double-checked by the grants team (reproducibility of the data analysis).
95 | - Research for relevant related work or declare how the literature review will be conducted.
96 | - Research and declare the intended venue for results publication and the timeline for publication.
97 |
--------------------------------------------------------------------------------
/docs/Support Docs/polkadot_stack.md:
--------------------------------------------------------------------------------
1 | # Open Source Polkadot Stack
2 |
3 | This document has been deprecated in favour of the [Open Source Polkadot Stack as part of the Polkadot Wiki](https://wiki.polkadot.network/docs/build-open-source).
4 |
--------------------------------------------------------------------------------
/docs/contribute.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 9
3 | title: 🫶 Contribute
4 | ---
5 |
6 | The W3F Grants Program aims to be as open and accessible as possible. If you are interested in contributing or getting involved, there are several ways you can do that:
7 |
8 | - 📋 We are open to **milestone evaluations** from third parties. If you are particularly interested in a certain project, or particularly knowledgeable on a relevant subject, feel free to comment on any [open grant applications](https://github.com/w3f/Grants-Program/issues?q=is%3Aopen+label%3A%22ready+for+review%22+sort%3Aupdated-desc), or have a look at the [open pull requests on our milestone delivery repository](https://github.com/w3f/Grant-Milestone-Delivery/pulls) and [submit your own evaluation](https://github.com/w3f/Grant-Milestone-Delivery#ballot_box_with_check-external-evaluations).
9 |
10 | - 🔍 If you find that there is something missing in our ecosystem (a tool, a project, infrastructure, etc.) that we could help fund, please [submit a **Request For Proposals (RFP)**](https://github.com/w3f/Grants-Program/blob/master/README.md#mailbox_with_mail-suggest-a-project). If writing an RFP seems too daunting a task, feel free to [submit it as an issue on our Github repository](https://github.com/w3f/Grants-Program/issues) so anyone can contribute.
11 |
12 | - 🤝 Join us! Check out [our current **job openings**](https://web3.bamboohr.com/jobs/) and apply! If there currently is no suitable job listed, don't hesitate to apply regardless or [reach out](./help.md) if you have any questions.
13 |
14 | We strive to continue improving our grants program and are always open to feedback. If you would like to share any suggestions or criticism, please reach out to us on [Github](https://github.com/w3f/Grants-Program) or [Matrix](https://matrix.to/#/!XpynPDLusWUWfDpaqr:matrix.org?via=web3.foundation&via=matrix.org)!
15 |
--------------------------------------------------------------------------------
/docs/funding.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 8
3 | title: 🪙 Alternative Funding
4 | ---
5 |
6 | :::tip
7 | For an overview of funding initiatives, ecosystem support and implementation partners, also check https://web3.foundation/funding-support.
8 | :::
9 |
10 | Some funding sources might be more and some less suitable for your project throughout its various stages. We encourage you to explore alternative funding options listed below. Please note, however, that you should not seek to fund the **same scope of work** from multiple sources and that any team found doing so will have its Web3 Foundation support terminated.
11 |
12 | :::note
13 | If you are unsure about what's the best next step for you and your project, consider signing up for the [Polkadot Alpha Program](https://polkadot.network/development/alpha/).
14 | :::
15 |
16 | ### Treasury
17 |
18 | The treasury is a pot of on-chain funds collected through transaction fees, slashing, staking inefficiencies, etc. The funds held in the treasury can be spent on spending proposals. Both [Polkadot](https://polkadot.network/) and [Kusama](https://kusama.network/) offer everyone the opportunity to apply for funding via the treasury. See:
19 |
20 | - [Treasury Bounties](https://polkadot.subsquare.io/treasury/bounties)
21 | - [Polkadot Treasury Guide](https://docs.google.com/document/d/1IZykdp2cyQavcRyZd_dgNj5DcgxgZR6kAqGdcNARu1w)
22 | - [Kusama Treasury Guide](https://docs.google.com/document/d/1p3UQUjph5t8TVaWnTkfrI5mE-BABnM9Xvtuhdlhl6JE)
23 |
24 | ### Hackathons
25 |
26 | From time to time, Web3 Foundation and/or Parity organise hackathons to promote quick prototyping of Polkadot related ideas. We highly encourage you to participate in these hackathons. Bear in mind, however, that you cannot submit the **same work** for a hackathon and the Grants Program. If you have worked or are planning to work on a project for a hackathon, your grant application should either propose a different set of features or otherwise build on top of your hackathon work. The same applies in reverse, although that will likely be less common.
27 |
28 | The best way to find out about upcoming hackathons is by following Polkadot on the various social channels, such as Element or Twitter.
29 |
30 | ### Other Grant or Bounty Programs
31 |
32 | Below is a list of other grant and bounty programs in the Polkadot/Substrate ecosystem:
33 |
34 | - [Acala Ecosystem Program](https://acala.network/ecosystem-program)
35 | - [Aleph Zero Funding Program](https://alephzero.org/ecosystem-funding-program)
36 | - [Avail Uncharted Grants](https://github.com/availproject/avail-uncharted/blob/main/grants/grants.md)
37 | - [Darwinia Grants Program](https://github.com/ringecosystem/collaboration)
38 | - [Decentralized JAM](https://jam.web3.foundation/)
39 | - [HydraDX Grants and Bounties](https://immunefi.com/bug-bounty/hydration/information/)
40 | - [ink!ubator](https://use.ink/ubator/)
41 | - [Moonbeam Grants Program](https://moonbeam.foundation/grants/)
42 | - [Moondance Labs Ecosystem Funding Program](https://www.moondancelabs.com/ecosystem-grants-w3f)
43 | - [peaq Ecosystem Grant Program](https://www.peaq.network/grant-program)
44 | - [Polkadot Open Source Developer Grants Bounty](https://github.com/PolkadotOpenSourceGrants)
45 | - [SubQuery Developer Guild](https://github.com/subquery/developer-guild)
46 | - [Pendulum / Amplitude Grant Programs](https://pendulumchain.org/ecosystem-grant)
47 | - [Polkadot Assurance Legion](https://polkadotassurance.com/)
48 |
--------------------------------------------------------------------------------
/docs/help.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 7
3 | title: 💡 Help
4 | ---
5 |
6 |
7 | ### Real-time Conversation
8 |
9 | - [Matrix channel for **grant-related questions and activities**](https://matrix.to/#/!XpynPDLusWUWfDpaqr:matrix.org?via=web3.foundation&via=matrix.org). Head over there to ask grants-related questions, share your experience with other applications and grantees, or simply hang out:
10 | - Program-specific Matrix channels for the [**Decentralized Futures Program**](https://matrix.to/#/#df:web3.foundation) and the [**JAM Prize**](https://matrix.to/#/#jam:polkadot.io):
11 | - For **technical questions**, check out the Polkadot Developer Support groups on [Telegram](https://t.me/substratedevs) and [Matrix](https://matrix.to/#/#substratedevs:matrix.org).
12 | - We also have general purpose Matrix channels and spaces for discussions on **Web3** and **Polkadot**. Join the conversation!
13 | - [Web3 Foundation Chat](https://matrix.to/#/#w3f:matrix.org)
14 | - [Polkadot Space](https://matrix.to/#/#polkadot:web3.foundation)
15 | - [Kusama Space](https://matrix.to/#/#kusama:web3.foundation)
16 |
17 | ### Additional Information
18 |
19 |
20 |
21 | | 
| 
| 
| 
| 
|
22 | | :-: | :-: | :-: | :-: | :-: |
23 | | [W3F Website](https://web3.foundation) | [W3F Twitter](https://twitter.com/web3foundation) | [W3F Medium](https://medium.com/web3foundation) | [Polkadot Wiki](https://wiki.polkadot.network/en/) | [W3F YouTube](https://www.youtube.com/channel/UClnw_bcNg4CAzF772qEtq4g) |
24 |
25 |
26 |
--------------------------------------------------------------------------------
/docs/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | draft: true
3 | ---
4 |
5 |
--------------------------------------------------------------------------------
/docs/introduction.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Introduction
3 | ---
4 |
5 | # 👋 Introduction
6 |
7 | As part of our commitment to promoting the Web3 ecosystem, we offer a comprehensive grants program focused on funding software development and research efforts related to **Polkadot and Kusama**. For more information about the Web3 Foundation, please visit the [About page](https://web3.foundation/about/) on our website.
8 |
9 | The following pages describe the scope, intentions and processes behind the W3F Grants Program. Please familiarize yourself and, if you have a project you would like to present, [apply!](process.md)
10 |
--------------------------------------------------------------------------------
/docs/maintenance.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 6
3 | title: 🛠️ Maintenance Grants
4 | ---
5 |
6 |
7 |
8 | Maintenance Grants are yet another idea to get involved with the Polkadot community. If you are a user of an open-source library that has gone out of date, or you simply want to work on small new features/fix bugs in these repos, we can support your contributions via a grant. We are happy to award rolling grants on a monthly basis, as long as the work done within each time period is performed to a quality standard deemed satisfactory by the grant evaluators.
9 |
10 | ## Application Process
11 |
12 | The process of applying for a Maintenance Grant is similar to what was already outlined above, but instead of defining very detailed deliverables for each milestone upfront, we will ask you to specify, where possible:
13 |
14 | - the repo(s) that need maintenance,
15 | - outline of why the specific project should continue being supported,
16 | - broad overview of the features/bugs that need development contributions,
17 | - an assurance that the current project owners are willing to review/accept your contributions (a note here: if you're fully taking over the project, it would make more sense for the current owners to transfer the repository to your organisation. If you can't get in touch with them, you may, of course, work on a fork), and
18 | - max budget per month.
19 |
20 | Then, at the end of each month, you will need to provide a comprehensive report of the work done, including the list of issues/bugs/pull requests worked on, time spent on each of these & finally the associated cost. It is quite likely that the time allocation & cost will vary from month to month, depending on the nature of the project you're contributing to. The delivery process and format should follow that of a typical [milestone delivery](https://github.com/w3f/Grant-Milestone-Delivery#mailbox-milestone-delivery-process), as will the processing of the payment.
21 |
22 | ## Notes
23 |
24 | - Maintenance grants, as the name suggests, are meant to allow teams/individuals to maintain a certain project, and not to continue its development or implement larger features. Please use the traditional application process for this purpose.
25 | - The 1-month timeframe is just a guideline. If you find it unsuitable for you or the chosen project for any reason, feel free to adjust as seen fit and point this out in your application.
26 | - Please bear in mind that the Grants Committee might be stricter in accepting maintainers when compared to typical grants, mostly selecting for applicants with proven experience in the relevant tech stacks.
27 | - Maintenance Grants are only awarded for fixed timeframes. The requested duration needs to be specified in the application.
28 |
29 | ## Help
30 |
31 | - For a list of previously accepted maintenance grants, see the `applications/maintenance` folder in our grants repository.
32 | - For a list of ways to reach us and ask questions, see our [Help page](help.md).
33 |
--------------------------------------------------------------------------------
/docs/office-hours.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 7
3 | title: 💼 Office Hours
4 | ---
5 |
6 | **Ecosystem Funding Office Hours** are a chance to ask the W3F Ecosystem Funding team questions regarding a specific project, a (potential) grant application or about funding opportunities in general. It offers
7 |
8 | - **general guidance** regarding the various grants programs and prizes,
9 | - some quick **initial feedback** about project ideas, RFPs, roadmaps, etc. and
10 | - help how to navigate the ecosystem and to find the right resources.
11 |
12 | [Apply for Office Hours](https://forms.gle/54xkiqU37WwdN9UR6) if you
13 |
14 | - want to find out what kind of **support** there might be available for your needs,
15 | - need **feedback** before submitting an application or
16 | - look for help finding other **resources** you might need.
17 |
18 | Applying is as simple as giving us a brief outline of the project or questions you would like to discuss and your availabilities. To do so, please fill out the [Office Hours form](https://forms.gle/54xkiqU37WwdN9UR6). We will then follow up with an invitation to book a 30-minute call with one of our Ecosystem Development team members. Be as specific as possible, so we can help you as efficiently as possible.
19 |
20 | :::tip
21 | Please note: Office Hours is **not** a chance to _pitch_ your project, especially since the various programs and prizes have different evaluation criteria and decision makers and only a small subset of the Ecosystem Development team will participate in the call.
22 |
23 | :::
24 |
--------------------------------------------------------------------------------
/docs/process.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Apply
3 | ---
4 |
5 | :::tip
6 | Check out the [Polkadot Alpha Program](https://polkadot.network/development/alpha/) for all kinds of ecosystem support opportunities.
7 |
8 | :::
9 | If you are certain you want to apply for a W3F grant, head straight to our [application process documentation](Process/how-to-apply.md). Alternatively, the flowchart below outlines where we think the grants program fits in relation to other popular funding opportunities.
10 |
11 | ## Funding Opportunities Overview
12 |
13 | ```mermaid
14 | flowchart LR
15 | A(Project Focus)
16 | A -->|Development| B[Stage of Development]
17 | A -->|Research| C[Grants Program]
18 | A -->|Other| D[Business model exists]
19 | B -->|Existing POC| E[Treasury or Decentralized Futures]
20 | B -->|No POC| F[Grants Program]
21 | D -->|No|H[Treasury]
22 | D -->|Yes|J[Decentralized Futures]
23 | style C stroke:#e83e8c,stroke-width:2px,stroke-dasharray: 5 5
24 | style E stroke:#e83e8c,stroke-width:2px,stroke-dasharray: 5 5
25 | style F stroke:#e83e8c,stroke-width:2px,stroke-dasharray: 5 5
26 | style H stroke:#e83e8c,stroke-width:2px,stroke-dasharray: 5 5
27 | style J stroke:#e83e8c,stroke-width:2px,stroke-dasharray: 5 5
28 |
29 | click C "Process/how-to-apply" "Apply now"
30 | click F "Process/how-to-apply" "Apply now"
31 | click H "https://wiki.polkadot.network/docs/en/learn-treasury" "https://wiki.polkadot.network/docs/en/learn-treasury" _blank
32 | click J "https://futures.web3.foundation/" "https://futures.web3.foundation/" _blank
33 | ```
34 |
35 | For a longer list and a description of the programs listed below, check out [our page on alternative funding opportunities](funding.md).
36 |
--------------------------------------------------------------------------------
/docs/referral-program.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 7
3 | title: 💰 Referral Program
4 | ---
5 |
6 | We give away 500 USD, payable in USDC on Polkadot AssetHub, to each referral of a successful grant application by _anyone having previously worked on a Web3 Foundation grant_ or _a [Polkadot Ambassador](https://wiki.polkadot.network/docs/ambassadors)_. Web3 Foundation and Parity employees do not qualify for the program, even if they previously worked on a grant.
7 |
8 | In order to be eligible for the referral bonus, the application itself must contain the name of the [Polkadot Ambassador](https://wiki.polkadot.network/docs/ambassadors) or the GitHub account of the grantee as well as the payment address and currency of choice for the referral bonus (see the [application template](https://github.com/w3f/Grants-Program/blob/master/applications/application-template.md)).
9 |
--------------------------------------------------------------------------------
/docs/suggesting.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 5
3 | title: 📬 Suggesting a Project
4 | ---
5 |
6 |
7 |
8 | If you think that we should support the development of certain tools or projects that aren't in the Polkadot/Kusama [tech stack](https://wiki.polkadot.network/docs/build-open-source), feel free to submit a suggestion ("Request for Proposal") using the process described below. We are particularly interested in supporting projects that could be leveraged by other builders in our ecosystem.
9 |
10 | For a list of previous Requests for Proposal and their status, see our [separate RFP page below](./rfps.md).
11 |
12 | **Submit an idea:**
13 |
14 | If you have an idea for a project or would like to highlight an area in which you'd like to see teams build, but lack the technical background to create a detailed outline, you're welcome to open an [issue](https://github.com/w3f/Grants-Program/issues/new) or add it to the [tech stack](https://wiki.polkadot.network/docs/build-open-source) as a potentially interesting project. We will review your suggestion and, if necessary, will create an RFP based on it and reach out to teams able to build it.
15 |
16 | **Submit an RFP (Request for Proposals):**
17 |
18 | Ideas generally have better chances of being implemented if they're presented in a project outline format that can be picked up straight away by a team, so if you have a good concept of the milestones required to bring your project to life, you can follow the process below and directly submit an RFP:
19 |
20 | 1. [Fork](https://github.com/w3f/Grants-Program/fork) this repository.
21 | 2. In the newly created fork, create a copy of the suggestion template ([`rfps/suggestion-template.md`](https://github.com/w3f/Grants-Program/blob/master/docs/RFPs/suggestion-template.md)) inside the [`rfps`](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) folder. Make sure you create a new file and copy the [contents](https://github.com/w3f/Grants-Program/blob/master/docs/RFPs/suggestion-template.md) of the template into the new one, and _do not modify the template file directly._
22 | 3. Name the file after your idea: `project_name.md`.
23 | 4. Fill out the template with the project details. Please include as many details as possible.
24 | 5. Once you're done, create a pull request in **our** main [Grants-Program repository](https://github.com/w3f/Grant-Milestone-Delivery/blob/master/README.md). The pull request should only contain _one new file_—the Markdown file you created from the template.
25 | 6. You will see the same template as for creating an application. Please replace it with [the RFP PR template](https://github.com/w3f/Grants-Program/blob/master/.github/PULL_REQUEST_TEMPLATE/rfp_pr_template.md).
26 | 7. The RFP will be accepted and merged as soon as it receives three approvals from [W3F Grants Committee](./Introduction/team.md#w3f-grants-committee) members.
27 |
--------------------------------------------------------------------------------
/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "grants",
3 | "version": "0.0.0",
4 | "private": true,
5 | "scripts": {
6 | "docusaurus": "docusaurus",
7 | "start": "docusaurus start",
8 | "build": "docusaurus build",
9 | "swizzle": "docusaurus swizzle",
10 | "deploy": "docusaurus deploy",
11 | "clear": "docusaurus clear",
12 | "serve": "docusaurus serve",
13 | "write-translations": "docusaurus write-translations",
14 | "write-heading-ids": "docusaurus write-heading-ids"
15 | },
16 | "dependencies": {
17 | "@docusaurus/core": "^3.5.2",
18 | "@docusaurus/mdx-loader": "^3.5.2",
19 | "@docusaurus/preset-classic": "^3.5.2",
20 | "@docusaurus/theme-mermaid": "^3.5.2",
21 | "@mdx-js/react": "^3.0.0",
22 | "@svgr/webpack": "^7.0.0",
23 | "clsx": "^1.1.1",
24 | "file-loader": "^6.2.0",
25 | "katex": "^0.16.9",
26 | "mermaid": "^10.8.0",
27 | "prettier": "^2.6.2",
28 | "pretty-quick": "^3.1.3",
29 | "prism-react-renderer": "^2.1.0",
30 | "react": "^18.2.0",
31 | "react-countup": "^6.4.0",
32 | "react-dom": "^18.2.0",
33 | "rehype-katex": "^7.0.0",
34 | "remark-math": "^6.0.0",
35 | "semver": "^7.5.4",
36 | "url-loader": "^4.1.1"
37 | },
38 | "resolutions": {
39 | "semver": "^7.5.4",
40 | "trim": "^0.0.3",
41 | "got": "13.0.0"
42 | },
43 | "browserslist": {
44 | "production": [
45 | ">0.5%",
46 | "not dead",
47 | "not op_mini all"
48 | ],
49 | "development": [
50 | "last 1 chrome version",
51 | "last 1 firefox version",
52 | "last 1 safari version"
53 | ]
54 | }
55 | }
56 |
--------------------------------------------------------------------------------
/sidebars.js:
--------------------------------------------------------------------------------
1 | /**
2 | * Creating a sidebar enables you to:
3 | - create an ordered group of docs
4 | - render a sidebar for each doc of that group
5 | - provide next/previous navigation
6 |
7 | The sidebars can be generated from the filesystem, or explicitly defined here.
8 |
9 | Create as many sidebars as you want.
10 | */
11 |
12 | // @ts-check
13 |
14 | const sidebars = {
15 | docs: [
16 | {
17 | type: 'html',
18 | className: 'sidebar-title',
19 | value: 'Basic Information',
20 | defaultStyle: true,
21 | },
22 | {
23 | type: 'category',
24 | label: '👋 Introduction',
25 | link: {type:'doc', id:'docs/introduction'},
26 | items: [{type: 'autogenerated', dirName: 'docs/Introduction'}]
27 | },
28 | {
29 | type: 'category',
30 | label: '📝 Application Process',
31 | link: {type:'doc', id:'docs/process'},
32 | items: [{type: 'autogenerated', dirName: 'docs/Process'}]
33 | },
34 | {
35 | type: 'doc',
36 | id:'docs/maintenance'
37 | },
38 | {
39 | type: 'html',
40 | value: '',
41 | },
42 | {
43 | type: 'html',
44 | className: 'sidebar-title',
45 | value: 'In Depth',
46 | defaultStyle: true,
47 | },
48 | {
49 | type: 'doc',
50 | id:'docs/help'
51 | },
52 | {
53 | type: 'doc',
54 | id:'docs/office-hours'
55 | },
56 | {
57 | type: 'doc',
58 | id:'docs/faq'
59 | },
60 | {
61 | type: 'doc',
62 | id:'docs/suggesting'
63 | },
64 | {
65 | type: 'doc',
66 | id:'docs/referral-program'
67 | },
68 | {
69 | type: 'html',
70 | value: '',
71 | },
72 | {
73 | type: 'html',
74 | className: 'sidebar-title',
75 | value: 'Beyond',
76 | defaultStyle: true,
77 | },
78 | {
79 | type: 'doc',
80 | id:'docs/funding'
81 | },
82 | {
83 | type: 'doc',
84 | id:'docs/contribute'
85 | },
86 | {
87 | type: 'doc',
88 | label: '📜 List of Grants',
89 | id:'applications/index'
90 | },
91 | {
92 | type: 'category',
93 | label: '🪧 Requests for Proposal',
94 | link: {type:'doc', id:'docs/rfps'},
95 | items: [{type: 'autogenerated', dirName: 'docs/RFPs'}]
96 | },
97 | {
98 | type: 'category',
99 | label: '🦮 Supporting Documents',
100 | items: [{type: 'autogenerated', dirName: 'docs/Support Docs'}]
101 | },
102 | ]
103 | };
104 |
105 | module.exports = sidebars;
106 |
--------------------------------------------------------------------------------
/src/components/HomepageFeatures.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import clsx from 'clsx';
3 | import styles from './HomepageFeatures.module.css';
4 | import CountUp from 'react-countup';
5 |
6 |
7 | const FeatureList = [
8 | {
9 | title: 1500,
10 | description: (
11 | <>applications
12 |
13 | ),
14 | },
15 | {
16 | title: 600,
17 | description: (
18 | <>projects funded
19 |
20 | ),
21 | },
22 | {
23 | title: 54,
24 | description: (
25 | <>countries
26 |
27 | ),
28 | },
29 | ];
30 |
31 | function Feature({Svg, title, description}) {
32 | return (
33 | | | | | |
22 | | :-: | :-: | :-: | :-: | :-: |
23 | | [W3F Website](https://web3.foundation) | [W3F Twitter](https://twitter.com/web3foundation) | [W3F Medium](https://medium.com/web3foundation) | [Polkadot Wiki](https://wiki.polkadot.network/en/) | [W3F YouTube](https://www.youtube.com/channel/UClnw_bcNg4CAzF772qEtq4g) |
24 |
25 |
34 |
41 | );
42 | }
43 |
44 | export default function HomepageFeatures() {
45 | return (
46 |
35 |
36 |
37 |
38 |
40 |
38 | {description}
39 |
48 |
54 |
49 | {FeatureList.map((props, idx) => (
50 |
53 |
38 | 
39 |
53 |
39 | {siteConfig.tagline}
40 |
41 | {links.map((link, index) => (
42 |
48 | {link.text}
49 |
50 | ))}
51 |
52 |