- Node.js: Version 22 or higher
- npm: Comes bundled with Node.js
- Vale (optional): For documentation linting and quality checks
We use Vale to maintain high-quality documentation standards. Vale checks your writing for clarity, consistency, and adherence to our style guidelines, helping us maintain a coherent tone of voice, accurate terminology, and overall editorial quality across the project.
macOS:
brew install Vale/tap/vale
Linux (Snap):
snap install vale
Windows:
choco install vale
# Download and install external configuration sources
vale sync
# Check all documentation files
vale src/
# Check specific files
vale src/get-started/helloWorld/1-overview.md
# Get detailed output
vale --output=line src/
# Generate comprehensive report with statistics
vale --output=line src/ > vale-report.txt 2>&1
Our Vale configuration uses the Google & Vale writing style guide, which helps ensure:
- Clear and concise language
- Consistent terminology
- Professional tone
- Accessibility best practices
Some features of the application require environment variables. This configuration is optional and only needed if you plan to work with Hello World pages.
Create a .env
file at the root of the project using the provided
.env.example
as a template:
cp .env.example .env
Then fill in the required values:
VITE_REOWN_PROJECT_ID=your_project_id_here
To obtain your VITE_REOWN_PROJECT_ID
, follow these steps:
- Go to https://dashboard.reown.com/
- Create an account if you don't have one already
- Once logged in, click on "Create Project" or "New Project"
- Fill in your project information:
- Project name
- Description (optional)
- Website URL (optional)
- Once the project is created, copy the "Project ID" displayed in the project details
- Paste this ID in your
.env
file as the value forVITE_REOWN_PROJECT_ID
Install the project dependencies:
npm install
Start the development server:
npm run dev
The documentation site will be available at http://localhost:3000
(or the port
shown in your terminal).
To build the project for production:
npm run build
We welcome contributions to improve the iExec documentation!
📖 For detailed contribution guidelines, component usage, and best practices, please see our CONTRIBUTING.md guide.
- Fork this repository
- Clone your fork and install dependencies (
npm install
) - Create a feature branch (
git checkout -b feature/your-feature-name
) - Make your changes and test locally (
npm run dev
) - Submit a pull request