npm create astro@latest -- --template basics
🧑🚀 Seasoned astronaut? Delete this file. Have fun!
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:4321 |
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 |
Feel free to check our documentation or jump into our Discord server.
There are two contexts where development of a static site in the context of Noop can be really helpful. First, when integrating with any external services that require HTTPS for Oauth callback URLs Noop handles all the certificates locally.
Second, when you need to run a static site in the context of other local application APIs or web apps Noop can serve all of them using a routing scheme very similar to your production deployments. That is, it can serve multiple services (development processes) all on the same local domain.
That said, in the context of a single static site, development with workshop might be overkill.
To deploy a static website on Noop, connect this or any other repository with a .noop directory to your Cloud application. For a complete set of instructions see the Launch Astro Site Guide on the Noop blog.