ernest

kbin landingpage

Go to file

Michal Rzeszutek 1ce54c2783 Footer to bottom		2023-06-08 19:53:42 +02:00
.vscode	First Commit	2023-06-02 16:11:58 +02:00
public	Details Summary	2023-06-05 13:59:04 +02:00
src	Footer to bottom	2023-06-08 19:53:42 +02:00
.gitignore	First Commit	2023-06-02 16:11:58 +02:00
README.md	Mainpage Gradients	2023-06-04 22:51:39 +02:00
astro.config.mjs	Section Personalization XL	2023-06-02 23:41:04 +02:00
package-lock.json	First Commit	2023-06-02 16:11:58 +02:00
package.json	First Commit	2023-06-02 16:11:58 +02:00
tsconfig.json	First Commit	2023-06-02 16:11:58 +02:00

README.md

kbin Landingpage

Features:

✅ SEO-friendly with canonical URLs and OpenGraph data
✅ Sitemap support
✅ RSS Feed support
✅ Markdown & MDX support

🚀 Project Structure

A typical Astro structure:

├── public/
├── src/
│   ├── components/
│   ├── content/
│   ├── layouts/
│   └── pages/
├── astro.config.mjs
├── README.md
├── package.json
└── tsconfig.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.

The src/content/ directory contains "collections" of related Markdown and MDX documents. Use getCollection() to retrieve posts from src/content/blog/, and type-check your frontmatter using an optional schema. See Astro's Content Collections docs to learn more.

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/`
`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

👀 Want to learn more?

Check out Astro docs.