Skip to content

Commit eaecd19

Browse files
fix: fix helloword page (#5)
Co-authored-by: Le-Caignec <[email protected]> Co-authored-by: Robin Le Caignec <[email protected]>
1 parent 78db297 commit eaecd19

31 files changed

+8961
-1538
lines changed

β€Ž.env.exampleβ€Ž

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
VITE_REOWN_PROJECT_ID=

β€Ž.vitepress/theme/Layout.vueβ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<script setup>
22
import DefaultTheme from 'vitepress/theme';
3-
import AskIaButton from './AskIaButton.vue';
3+
import AskIaButton from '../../src/components/AskIaButton.vue';
44
55
const { Layout } = DefaultTheme;
66
</script>

β€Ž.vitepress/theme/index.tsβ€Ž

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,29 @@
11
// https://vitepress.dev/guide/custom-theme
22
import type { Theme } from 'vitepress';
33
import DefaultTheme from 'vitepress/theme';
4-
import './style.css';
54
import TwoslashFloatingVue from '@shikijs/vitepress-twoslash/client';
65
import Layout from './Layout.vue';
76
import type { EnhanceAppContext } from 'vitepress';
87
import googleAnalytics from 'vitepress-plugin-google-analytics';
98
import 'virtual:group-icons.css';
109
import '@shikijs/vitepress-twoslash/style.css';
10+
import { QueryClient, VueQueryPlugin } from '@tanstack/vue-query';
11+
import { WagmiPlugin } from '@wagmi/vue';
12+
import { wagmiAdapter } from '../../src/utils/wagmiConfig';
13+
import './style.css';
1114

1215
export default {
1316
extends: DefaultTheme,
1417
Layout,
1518
enhanceApp({ app }: EnhanceAppContext) {
1619
app.use(TwoslashFloatingVue as any);
1720

21+
const queryClient = new QueryClient();
22+
23+
app.use(VueQueryPlugin, { queryClient });
24+
25+
app.use(WagmiPlugin, { config: wagmiAdapter.wagmiConfig });
26+
1827
googleAnalytics({
1928
id: 'GTM-P7KSD4T',
2029
});

β€Ž.vitepress/theme/style.cssβ€Ž

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,3 +136,15 @@ html {
136136
.aside .aside-container {
137137
@apply overflow-visible;
138138
}
139+
140+
html.dark .light-only {
141+
display: none !important;
142+
}
143+
144+
html:not(.dark) .dark-only {
145+
display: none !important;
146+
}
147+
148+
input {
149+
@apply w-full rounded-md border border-[var(--vp-c-divider)] bg-[var(--vp-c-bg-soft)] px-4 py-3 text-base text-[var(--vp-c-text-1)] transition focus:border-[var(--vp-c-brand-2)] focus:outline-none disabled:cursor-not-allowed disabled:opacity-70;
150+
}

β€ŽREADME.mdβ€Ž

Lines changed: 131 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,151 @@
1-
# iExec Tools documentation
1+
# iExec Documentation
22

3-
This is the source repository of the [iExec documentation](https://docs.iex.ec)
3+
## πŸ“‹ Prerequisites
44

5-
## Prerequisites
5+
- **Node.js**: Version 22 or higher
6+
- **npm**: Comes bundled with Node.js
67

7-
- Node 22
8+
## βš™οΈ Configuration
89

9-
## Run app
10+
### Environment Variables (Optional)
1011

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
1127
```
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
1251
npm install
52+
```
53+
54+
### Development Server
55+
56+
Start the development server:
57+
58+
```bash
1359
npm run dev
1460
```
1561

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+
[![fork-button](./src/public/fork-button.png)](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:
17118

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+
```
19123

20-
### Fork
124+
2. Push your changes to your forked repository:
21125

22-
Fork the repo and be sure to be on `main` branch
126+
```bash
127+
git push origin feature/your-feature-name
128+
```
23129

24-
[![fork-button](./public/fork-button.png)](https://github.com/iExecBlockchainComputing/documentation/fork)
130+
3. Open a pull request from your feature branch to our `main` branch
25131

26-
### Contribute
132+
### 5. Review Process
27133

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
30140
31-
Push your changes to your forked branch.
141+
## πŸ“„ License
32142

33-
### PR time
143+
This project is part of the iExec ecosystem. Please refer to the main iExec
144+
repositories for licensing information.
34145

35-
Open a pull request from your forked branch to our `main` branch.
146+
## πŸ†˜ Support
36147

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

Comments
Β (0)