|
1 | | -# iExec Tools documentation |
| 1 | +# iExec Documentation |
2 | 2 |
|
3 | | -This is the source repository of the [iExec documentation](https://docs.iex.ec) |
| 3 | +## π Prerequisites |
4 | 4 |
|
5 | | -## Prerequisites |
| 5 | +- **Node.js**: Version 22 or higher |
| 6 | +- **npm**: Comes bundled with Node.js |
6 | 7 |
|
7 | | -- Node 22 |
| 8 | +## βοΈ Configuration |
8 | 9 |
|
9 | | -## Run app |
| 10 | +### Environment Variables (Optional) |
10 | 11 |
|
| 12 | +Some features of the application require environment variables. This |
| 13 | +configuration is optional and only needed if you plan to work with Hello World |
| 14 | +pages. |
| 15 | + |
| 16 | +Create a `.env` file at the root of the project using the provided |
| 17 | +`.env.example` as a template: |
| 18 | + |
| 19 | +```bash |
| 20 | +cp .env.example .env |
| 21 | +``` |
| 22 | + |
| 23 | +Then fill in the required values: |
| 24 | + |
| 25 | +```env |
| 26 | +VITE_REOWN_PROJECT_ID=your_project_id_here |
11 | 27 | ``` |
| 28 | + |
| 29 | +#### Getting your VITE_REOWN_PROJECT_ID |
| 30 | + |
| 31 | +To obtain your `VITE_REOWN_PROJECT_ID`, follow these steps: |
| 32 | + |
| 33 | +1. Go to [https://dashboard.reown.com/](https://dashboard.reown.com/) |
| 34 | +2. Create an account if you don't have one already |
| 35 | +3. Once logged in, click on "Create Project" or "New Project" |
| 36 | +4. Fill in your project information: |
| 37 | + - Project name |
| 38 | + - Description (optional) |
| 39 | + - Website URL (optional) |
| 40 | +5. Once the project is created, copy the "Project ID" displayed in the project |
| 41 | + details |
| 42 | +6. Paste this ID in your `.env` file as the value for `VITE_REOWN_PROJECT_ID` |
| 43 | + |
| 44 | +## π Getting Started |
| 45 | + |
| 46 | +### Installation |
| 47 | + |
| 48 | +Install the project dependencies: |
| 49 | + |
| 50 | +```bash |
12 | 51 | npm install |
| 52 | +``` |
| 53 | + |
| 54 | +### Development Server |
| 55 | + |
| 56 | +Start the development server: |
| 57 | + |
| 58 | +```bash |
13 | 59 | npm run dev |
14 | 60 | ``` |
15 | 61 |
|
16 | | -## Contributing |
| 62 | +The documentation site will be available at `http://localhost:3000` (or the port |
| 63 | +shown in your terminal). |
| 64 | + |
| 65 | +### Building for Production |
| 66 | + |
| 67 | +To build the project for production: |
| 68 | + |
| 69 | +```bash |
| 70 | +npm run build |
| 71 | +``` |
| 72 | + |
| 73 | +## π€ Contributing |
| 74 | + |
| 75 | +We welcome contributions to improve the iExec documentation! Please follow these |
| 76 | +steps to contribute: |
| 77 | + |
| 78 | +### 1. Fork the Repository |
| 79 | + |
| 80 | +Fork this repository and ensure you're working on the `main` branch: |
| 81 | + |
| 82 | +[](https://github.com/iExecBlockchainComputing/documentation/fork) |
| 83 | + |
| 84 | +### 2. Set Up Your Development Environment |
| 85 | + |
| 86 | +1. Clone your forked repository: |
| 87 | + |
| 88 | + ```bash |
| 89 | + git clone https://github.com/YOUR_USERNAME/documentation.git |
| 90 | + cd documentation |
| 91 | + ``` |
| 92 | + |
| 93 | +2. Install dependencies: |
| 94 | + |
| 95 | + ```bash |
| 96 | + npm install |
| 97 | + ``` |
| 98 | + |
| 99 | +3. Start the development server: |
| 100 | + ```bash |
| 101 | + npm run dev |
| 102 | + ``` |
| 103 | + |
| 104 | +### 3. Make Your Changes |
| 105 | + |
| 106 | +1. Create a new branch for your feature/fix: |
| 107 | + |
| 108 | + ```bash |
| 109 | + git checkout -b feature/your-feature-name |
| 110 | + ``` |
| 111 | + |
| 112 | +2. Make your changes to the documentation |
| 113 | +3. Test your changes locally to ensure they work as expected |
| 114 | + |
| 115 | +### 4. Submit Your Changes |
| 116 | + |
| 117 | +1. Stage and commit your changes with a descriptive message: |
17 | 118 |
|
18 | | -To keep the contribution process smooth, please read this small guide. |
| 119 | + ```bash |
| 120 | + git add . |
| 121 | + git commit -m "Add: descriptive commit message" |
| 122 | + ``` |
19 | 123 |
|
20 | | -### Fork |
| 124 | +2. Push your changes to your forked repository: |
21 | 125 |
|
22 | | -Fork the repo and be sure to be on `main` branch |
| 126 | + ```bash |
| 127 | + git push origin feature/your-feature-name |
| 128 | + ``` |
23 | 129 |
|
24 | | -[](https://github.com/iExecBlockchainComputing/documentation/fork) |
| 130 | +3. Open a pull request from your feature branch to our `main` branch |
25 | 131 |
|
26 | | -### Contribute |
| 132 | +### 5. Review Process |
27 | 133 |
|
28 | | -Apply your changes on your forked branch, stage them and commit them with a |
29 | | -descriptive commit message. |
| 134 | +> **π‘ Tips:** |
| 135 | +> |
| 136 | +> - You can open a draft pull request and mark it as "Ready for review" once |
| 137 | +> you're satisfied with the preview |
| 138 | +> - All pull requests are reviewed by our team before being merged |
| 139 | +> - Feel free to ask questions in the pull request if you need clarification |
30 | 140 |
|
31 | | -Push your changes to your forked branch. |
| 141 | +## π License |
32 | 142 |
|
33 | | -### PR time |
| 143 | +This project is part of the iExec ecosystem. Please refer to the main iExec |
| 144 | +repositories for licensing information. |
34 | 145 |
|
35 | | -Open a pull request from your forked branch to our `main` branch. |
| 146 | +## π Support |
36 | 147 |
|
37 | | -> _**Tips:**_ |
38 | | -> You can open a draft pull request and set it to "Ready for review" once you |
39 | | -> are happy with the preview. Opened pull requests will be reviewed by the team |
40 | | -> and merged once approved. |
| 148 | +- π [Documentation](https://docs.iex.ec) |
| 149 | +- π¬ [Discord Community](https://discord.com/invite/pbt9m98wnU) |
| 150 | +- π |
| 151 | + [Issue Tracker](https://github.com/iExecBlockchainComputing/documentation/issues) |
0 commit comments