totole/sapper-template
1
0
Fork 0
mirror of https://github.com/kevin-DL/sapper-template.git synced 2026-01-16 12:04:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

create blog posts from markdown files

Browse Source
This commit is contained in:
Rich Harris
2018-07-27 14:28:32 -04:00
parent 29e6481559
commit 0fa6c9f7d7
10 changed files with 129 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
posts/how-is-sapper-different-from-next.md Normal file
View File

@@ -0,0 +1,11 @@
---
title: How is Sapper different from Next.js?
pubdate: 2018-07-19
---
[Next.js](https://github.com/zeit/next.js/) is a React framework from [Zeit](https://zeit.co), and is the inspiration for Sapper. There are a few notable differences, however:
* It's powered by [Svelte](https://svelte.technology) instead of React, so it's faster and your apps are smaller
* Instead of route masking, we encode route parameters in filenames. For example, the page you're looking at right now is `routes/blog/[slug].html`
* As well as pages (Svelte components, which render on server or client), you can create *server routes* in your `routes` directory. These are just `.js` files that export functions corresponding to HTTP methods, and receive Express `request` and `response` objects as arguments. This makes it very easy to, for example, add a JSON API such as the one [powering this very page](blog/how-is-sapper-different-from-next.json)
* Links are just `<a>` elements, rather than framework-specific `<Link>` components. That means, for example, that [this link right here](blog/how-can-i-get-involved), despite being inside a blob of HTML, works with the router as you'd expect.