powered by Astro + Fleek Starter Kit
In this project we are trying to build a specialized form of DAO, I called RnD-DAO, as in DAO for Research Team. The general characteristics is this DAO (in addition to the normal properties of DAO, e.g., governance, voting, etc) will have a mechanism to store digital assets (think of actively Money Generating NFT), mechanism to share earnings from the digital asset, mechanism to convert work (like finishing a task, into a stake in the DAO ownership). I guess that's going to be the decent goal for the limited timeframe.
As a prototype, I am aiming to make it into something like a 5-10 membered DAO, each member will have distict role (like funder, worker, admin, AI-Agents,etc.)
The goal is less about building from scratch but to integrate several great components that already out there for this purpose. For instance AragonOS is a great starting point for the general DAO, since all the basic functionalities are already available, the digital asset can be set to work/earn in platform such as Fetch's AgentVerse, or Ocean Data Marketplace, or in the Human case the TalenT Layer network, etc.
I am not so familiar with the Celestia capability in storing big amount of complex data, if internal data storage is not available, the ideal solution stack is to integrate with IPFS/Filecoin/Arweave.
Inside of your Astro project, you'll see the following folders and files:
/
├── public/
│ └── favicon.svg
├── src/
│ ├── components/
│ │ └── Card.astro
│ ├── layouts/
│ │ └── Layout.astro
│ └── pages/
│ └── index.astro
└── package.json
Astro looks for .astro
or .md
files in the src/pages/
directory. Each page is exposed as a route based on its file name.
There's nothing special about src/components/
, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.
Any static assets, like images, can be placed in the public/
directory.
All commands are run from the root of the project, from a terminal:
Command | Action |
---|---|
npm install |
Installs dependencies |
npm run dev |
Starts local dev server at localhost:3000 |
npm run build |
Build your production site to ./dist/ |
npm run preview |
Preview your build locally, before deploying |
npm run astro ... |
Run CLI commands like astro add , astro check |
npm run astro --help |
Get help using the Astro CLI |
You can configure this site deployment using Fleek CLI and running:
> fleek sites init
WARN! Fleek CLI is in beta phase, use it under your own responsibility
? Choose one of the existing sites or create a new one. ›
❯ Create a new site
It will prompt you for a name
, dist
directory location & build command
name
: How you want to name the sitedist
: The output directory where the site is located, for this template it'sdist
build command
: Command to build your site, this will be used to deploy the latest version either by CLI or Github Actions
After configuiring your fleek.json
file, you can deployt the site by running
fleek sites deploy
After running it you will get an output like this:
WARN! Fleek CLI is in beta, use it at your own discretion
> Success! Deployed!
> Site IPFS CID: QmP1nDyoHqSrRabwUSrxRV3DJqiKH7b9t1tpLcr1NTkm1M
> You can visit through the gateway:
> https://ipfs.io/ipfs/QmP1nDyoHqSrRabwUSrxRV3DJqiKH7b9t1tpLcr1NTkm1M
- Continuous Integration (CI):
fleek sites ci
Documentation. - Adding custom domains:
fleek domains create
Documentation.
This template has been configured to produce a static output.
// astro.config.mjs
import { defineConfig } from 'astro/config';
// https://astro.build/config
export default defineConfig({
output: 'static',
});
You can find more information about static builds in Astro Documentation
Feel free to check Astro documentation or jump into Astro's Discord server.