// Ordinarily, you'd generate this data from markdown files in your // repo, or fetch them from a database of some kind. But in order to // avoid unnecessary dependencies in the starter template, and in the // service of obviousness, we're just going to leave it here. // This file is called `_posts.js` rather than `posts.js`, because // we don't want to create an `/blog/posts` route — the leading // underscore tells Sapper not to do that. const posts = [ { title: 'What is Sapper?', slug: 'what-is-sapper', html: `

First, you have to know what Svelte is. Svelte is a UI framework with a bold new idea: rather than providing a library that you write code with (like React or Vue, for example), it's a compiler that turns your components into highly optimized vanilla JavaScript. If you haven't already read the introductory blog post, you should!

Sapper is a Next.js-style framework (more on that here) built around Svelte. It makes it embarrassingly easy to create extremely high performance web apps. Out of the box, you get:

Code-splitting, dynamic imports and hot module replacement, powered by webpack
Server-side rendering (SSR) with client-side hydration
Service worker for offline support, and all the PWA bells and whistles
The nicest development experience you've ever had, or your money back

It's implemented as Express middleware. Everything is set up and waiting for you to get started, but you keep complete control over the server, service worker, webpack config and everything else, so it's as flexible as you need it to be.

` }, { title: 'How to use Sapper', slug: 'how-to-use-sapper', html: `

Step one

Create a new project, using degit:

npx degit "sveltejs/sapper-template#rollup" my-app
			cd my-app
			npm install # or yarn!
			npm run dev

Step two

Go to localhost:3000. Open my-app in your editor. Edit the files in the src/routes directory or add new ones.

Step three

...

Step four

Resist overdone joke formats.

` }, { title: 'Why the name?', slug: 'why-the-name', html: `

In war, the soldiers who build bridges, repair roads, clear minefields and conduct demolitions — all under combat conditions — are known as sappers.

For web developers, the stakes are generally lower than those for combat engineers. But we face our own hostile environment: underpowered devices, poor network connections, and the complexity inherent in front-end engineering. Sapper, which is short for Svelte app maker, is your courageous and dutiful ally.

` }, { title: 'How is Sapper different from Next.js?', slug: 'how-is-sapper-different-from-next', html: `

Next.js is a React framework from Zeit, and is the inspiration for Sapper. There are a few notable differences, however:

It's powered by Svelte 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 src/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
Links are just <a> elements, rather than framework-specific <Link> components. That means, for example, that this link right here, despite being inside a blob of HTML, works with the router as you'd expect.

` }, { title: 'How can I get involved?', slug: 'how-can-i-get-involved', html: `

We're so glad you asked! Come on over to the Svelte and Sapper repos, and join us in the Discord chatroom. Everyone is welcome, especially you!

` } ]; posts.forEach(post => { post.html = post.html.replace(/^\t{3}/gm, ''); }); export default posts;