astro/examples/blog-multiple-authors
Fred K. Schott affcd04f0f
stop building, bundling, and transforming public/ files (#1210)
* stop bundling public/ files

* update www and examples
2021-08-25 11:51:04 -07:00
..
public stop building, bundling, and transforming public/ files (#1210) 2021-08-25 11:51:04 -07:00
src cleanup example favicons 2021-08-16 14:34:08 -07:00
.gitignore update the blog example (#565) 2021-06-28 15:29:16 -07:00
.npmrc update the blog example (#565) 2021-06-28 15:29:16 -07:00
astro.config.mjs Add zod schema validation (#1198) 2021-08-23 14:07:03 -07:00
CHANGELOG.md update the blog example (#565) 2021-06-28 15:29:16 -07:00
package.json Version Packages (#1217) 2021-08-24 16:11:51 -04:00
README.md add dev script, switch documentation from advising start to dev script (#1141) 2021-08-18 22:07:08 -07:00
tsconfig.json [ci] yarn format 2021-08-13 23:32:55 +00:00

Astro Starter Kit: Blog with Multiple Authors

npm init astro -- --template blog-multiple-authors

🧑‍🚀 Seasoned astronaut? Delete this file. Have fun!

Features:

  • SEO-friendly setup with canonical URLs and OpenGraph data
  • Full Markdown support
  • RSS 2.0 generation
  • Sitemap.xml generation

🚀 Project Structure

Inside of your Astro project, you'll see the following folders and files:

/
├── public/
│   ├── robots.txt
│   └── favicon.ico
├── src/
│   ├── components/
│   │   └── Tour.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.

🧞 Commands

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:3000
npm run build Build your production site to ./dist/

👀 Want to learn more?

Feel free to check our documentation or jump into our Discord server.