Tailwind, side barr, add new component button, layour of route

2020-12-26 02:22:37 +02:00
parent b700f6bb07
commit ba06a0001a
27 changed files with 1753 additions and 636 deletions
@@ -85,7 +85,7 @@ This is the heart of your Sapper app. There are two kinds of routes — *pages*,

 There are three simple rules for naming the files that define your routes:

-* A file called `src/routes/about.svelte` corresponds to the `/about` route. A file called `src/routes/blog/[slug].svelte` corresponds to the `/blog/:slug` route, in which case `params.slug` is available to the route
+* A file called `src/routes/about.svelte` corresponds to the `/about` route. A file called `src/routes/blog/[id].svelte` corresponds to the `/blog/:id` route, in which case `params.id` is available to the route
 * The file `src/routes/index.svelte` (or `src/routes/index.js`) corresponds to the root of your app. `src/routes/about/index.svelte` is treated the same as `src/routes/about.svelte`.
 * Files and directories with a leading underscore do *not* create routes. This allows you to colocate helper modules and components with the routes that depend on them — for example you could have a file called `src/routes/_helpers/datetime.js` and it would *not* create a `/_helpers/datetime` route.