Again, purely personal opinion. I think first making the environment run before editing is the more natural way. For example, it reassures the contributor that everything works BEFORE the editing. If you like the other order more, feel free to drop this commit!
1.4 KiB
Setting up Astro with Extensions for local development
Follow these steps to set up Astro with Starlight and additional extensions:
-
Install Node.js and npm
Ensure you have Node.js and npm installed on your system. You can download them from nodejs.org.
-
Fork the documentation-coolify repository and open the folder in a code editor
-
Install Dependencies
Run the following command inside the local repository:
npm install -
Optional: Install the Astro and MDX VS Code extension
Install the Astro and MDX VS Code extension to get syntax highlighting and other useful features:
-
Run your Astro site
Start the development server by running the following command inside the local repository:
npm run devThis will start a local server and give you a URL to preview your changes.
-
Create your contribution
Either edit a markdown file in the
src/content/docs/directory or create a new.mdxfile in thesrc/content/docs/directory and start writing your docs article. -
Create a Pull Request
Create a new pull request from your forked repository to the main documentation-coolify repository.