npm ci npm run dev
Other useful stuff: CSS-modules can be used out of the box? Let's try.
Astro has an and component that can be used as such:
import myImage from "src/path/to/image.jpg";
<Image src={myImage} ..otherProps /> <Picture src={myImage} ..otherProps />
But the annyoing part is that each image has to be imported like above, and these can only be used in an astro component, or passed to a React component as a child.
Currently I just use full sized images everywhere. To help with the old bandwidth I have converted them to webp with ImageMagick.
Convert all images in a directory to a compress .webp: mogrify -format webp -quality 80 *.jpg (https://www.bartvandersanden.com/blog/2022/07/03/webp-imagick/)
I think I had a like an ALBUM_SRC folder somewhere that was synced to this repo? How do I get images to here again?
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.