Skip to main content

Crowdloan Front End Template

  • Team Name: 10Clouds Sp. z o.o.
  • Payment Address: 0xa79aa9572c7e1f8909fcc9674d676b73d5a71faa (aUSD)
  • Level: 2

Project Overview πŸ“„β€‹

Responding to RFP:


A front-end white-label template for teams to use to easily build their Polkadot Crowdloan websites.

Project Details​

The overall objective of this project is to provide a white-label solution to teams to be able to plug into and offer all the information users need to contribute to their Crowdloan. In essence, it's a collection of:

  1. Project information
  2. Rewards Schema
  3. Current contributions
  4. Time left in Crowdloan and competition
  5. Contribute CTA
  6. After the Crowdloan

All of the above should be done style agnostic so that the project can plug their own look and feel into the site. (as per RFP)

Ecosystem Fit​

Defined by RFP

Team πŸ‘₯​

Team members​

  • Product Delivery Manager - Jedrzej Wencka
  • Tech Lead - Aleksander Krasnicki
  • React - Maciej Topor
  • Design Lead - Krzysztof Juszczyk
  • UX & Product Designer - PaweΕ‚ PoteraΕ‚a


  • Registered Address: ul. Chmielna 73, 00-801 Warsaw, Poland
  • Registered Legal Entity: 10Clouds Sp. z o.o. (Ltd.)

Team's experience​

The team was involved in creating an internal NFT Marketplace white-label ( As the name suggests it's a website that allows mint and trade NFTs between users. It is strongly inspired by OpenSea and follows the same lazy minting pattern. After login with Metamask user can customize the profile, create collections, and start lazy-minting NFTs. The website contains extensive search/filters for collections and NFTs. An NFT can be created as Open for offers which means another user can offer a price for which they want to buy it and the owner can accept any of them. The other way of selling is the β€žBuy now" option which allows you to sell NFTs for a set, fixed price. In both scenarios, the NFT is minted during the sale process and transferred to the new owner.

The app is written in Next.js on the front-end and contains our own Smart Contracts currently deployed on Goerli testnet, and the Backend is written in Python with GraphQL. We have our own subgraph created in The Graph to aggregate the information about events emitted from our contracts (to update the UI accordingly).

Team Code Repos​

Team LinkedIn Profiles (if available)​

Development Status πŸ“–β€‹

We are currently in a very initial phase of gathering benchmarks for the approach and setting the general approach to deliver an experience that fits the target audience.

From our initial research we came to the conclusion that the solution should follow these traits:

Using a Jamstack approach & Webflow template​

We aim to provide front-end templates that can be used with one major static site generator (SSG). This follows similar approaches like Github Pages templates for projects that contain the most important information and link-stubs to make it easy for Github projects to present themselves.

The Jamstack will allow us to leverage the vast community behind it for future involvement of customisations and ports to other SSGs as is evidenced by the activities of these communities who are eager to port interesting templates to their SSG of choice.

In addition to this we plan to create a Webflow template variant for teams who are more comfortable with it. Optionally we can also publish the Figma design as a basis for custom layouts by the community.

One Page approach​

We will also suggest a One Page or Single Page approach that, while still having the option for a menu, presents all information in one page as the name suggests. This has the following advantages:

  • Most simple approach for projects. Projects often underestimate the effort to create content and at the same time keep certain information to a digestible length
  • Less scope allows more variants. If we limit the scope to a single page, we can more easily provide additional template designs that follow the structure but still give some individuality for each project.

SSG support (Jamstack only)​

We aim to start with the support of Astro, a popular React-based choice for SSGs, with a vast community of its own. An initial survey of the Parity community should be done to see whether these assumptions match and should be revised.

When it comes to other SSGs, the ports can either be motivated by further grants or left to the community of open source volunteers. As mentioned before, there is an intrinsic motivation of each SSG’s community to port popular templates.

Deployment choices (Jamstack only)

The Jamstack approach allows the community to use virtually every popular way of hosting the project sites. We are assessing whether it is beneficial to include a β€œDeploy to Netlify” button in the projects as well to lower the initial barrier. However, projects will be able to deploy their pages to (but not be limited):

  • Netlify
  • Github Pages
  • Gitlab Pages
  • Vercel
  • Cloudflare
  • AWS S3 (and similar solutions)

Easy to get started​

We’re assuming that the approach is also a familiar way for the Parity community to get started with their project pages. It’s as simple as fork, customize, deploy.

For parts of the community who are less comfortable with the Jamstack approach we will provide a Webflow template as well.

Illustrative Examples​

Development Roadmap πŸ”©β€‹


  • Total Estimated Duration: 4-5 weeks
  • Full-Time Equivalent (FTE): 2 (Product Designer & React Developer) + Support Team (PDM, Leads, UX Designer)
  • Total Costs: 30,000 USD

Milestone 1​

  • Estimated duration: 4-5 weeks
  • FTE: 2 (as above)
  • Costs: 30,000 USD
0a.LicenseMIT or TBD
0b.DocumentationFor both approaches (Webflow & Jamstack) we provide how-to guides. Jamstack will be documented in the Github repo.
0c.ArticleWe will publish an article presenting the templates and how to use them.
1a.BenchmarkingDesign research of existing Crowdloan pages and other one pages designs, like Github project pages templates.
This will allow us to synthesize viable options of the page designs
1b.Design Direction PrototypeAiming to create as many medium to high-fidelity dd prototypes as possible that allows the Grants team and the community to have an input on the design direction
The aim is to have the prototypes at 25%-50% completeness, to see major components/features and the general design direction. This way we don't waste time on dismissed design directions.
The designs should follow good practices in general without requiring additional research
1c.Repo SetupRepo setup incl. base libraries/frameworks, initial technical documentation. Undesigned base scaffold. Allows the implementation to be simplified by forking
2.Jamstack implementation in AstroOne (1) chosen design direction

Minimum sections:
- Project information
- Rewards Schema
- Current contributions
- Time left in Crowdloan and competition
- Contribute CTA
- After the Crowdloan

Implemented as One Page Design
3.Webflow implementationOne (1) chosen design direction

Minimum sections:
- Project information
- Rewards Schema
- Current contributions
- Time left in Crowdloan and competition
- Contribute CTA
- After the Crowdloan
Out of the scope: integrate contribution flow and polkaskan table due to Webflow technical limitations (users of template may still try to implement that on their own way)

Implemented as One Page Design
4.Figma Template PublishingAllows to use it for other solutions

Future Plans​

When provided with the initial set of templates and their usage instructions, we envision the following:

  • Creating a hub repo that also uses a Jamstack approach to give a list of available templates, allowing the community to preview the templates easily and contribute templates or forks to other SSGs in a convenient place The hub could also include:
  • Good content practices partially provided by our team of UX writers
    • FAQs
    • Tips and Tricks taken from successful Crowdloans

Additional Information βž•β€‹

How did you hear about the Grants Program?

Multiple contact people from Parity (e.g. Alberto Navarro or Richard Casey).

Work we have already done

We contributed to Devnet support SLA for parachains.