This template is open-source software licensed under the GPL-3.0 license. You are free to fork, modify, and use it in your projects.
Originally created by Michael Andreuzza. Modified, extended, and redistributed by Bektur Aslan with added sections and updated UI/UX for broader usage.
Now we are using only a CSS file. It's called global.css and it's located in the src/styles folder. Now we are eimporting Tailwind CSS on the same file instead of using the tailwind.config.cjs file. Like this:
// Importing Tailwind CSS
@import "tailwindcss";
// Importing Tailwind plugins
@plugin "@tailwindcss/typography";
@plugin "@tailwindcss/forms";Then to add your styles you will use the @theme directive. Like this:
@theme {
/* Your CSS goes here, see how styles are written on the global.css file */
}Remember this is just in Alpha version, so you can use it as you want. Just keep an eye on the changes that Tailwind CSS is going to make.
Inside of your Astro project, you'll see the following folders and files:
/
├── public/
├── src/
│ └── 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: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 |
Feel free to check Astro's documentation
Maintained & updated by Bektur Aslan. Contributions welcome.
De Meta Pixel, consentlogica, UTM-behoud en conversie-events voor de SOLA
funnel staan beschreven in docs/meta-conversion-tracking.md.
Use this checklist after deploy when validating duplicate-host/canonical issues.
pnpm buildrg -n "rel=\"canonical\"" dist/weekenden/exercise-is-medicine/index.html dist/weekenden/bewustwording-connectie/index.html
Expected behavior for non-www URLs:
- first response should be 301 or 308
- response headers should include:
Location: https://www.solatravel.be/weekenden/exercise-is-medicine(for the first URL)Location: https://www.solatravel.be/weekenden/bewustwording-connectie(for the second URL)
Useful commands:
curl -I -sS https://solatravel.be/weekenden/exercise-is-medicine | sed -n '1,20p'curl -I -sS https://solatravel.be/weekenden/bewustwording-connectie | sed -n '1,20p'
- Open
https://solatravel.be/weekenden/exercise-is-medicine. Expected:301or308redirect tohttps://www.solatravel.be/weekenden/exercise-is-medicine. - Open
https://solatravel.be/weekenden/bewustwording-connectie. Expected:301or308redirect tohttps://www.solatravel.be/weekenden/bewustwording-connectie. - Open
https://www.solatravel.be/weekenden/exercise-is-medicine/. Expected:301or308redirect tohttps://www.solatravel.be/weekenden/exercise-is-medicine. - Open
https://www.solatravel.be/weekenden/bewustwording-connectie/. Expected:301or308redirect tohttps://www.solatravel.be/weekenden/bewustwording-connectie. - In Chrome DevTools → Network:
- enable Preserve log
- enable Disable cache
- verify the initial request returns 301/308 and includes a
Locationheader to the expected non-slash orwwwURL.
- Set
www.solatravel.beas Primary domain - Attach
solatravel.beas an additional domain - Enable Redirect to Primary Domain (if available)