alexjsteffen / swyxkit

An opinionated blog starter for SvelteKit + Tailwind + Netlify. Refreshed for 2022!

Home Page:https://swyxkit.netlify.app/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

A lightly opinionated starter for Svelte projects:

Feel free to rip out these opinions as you see fit of course.

Live Demo

See https://swyxkit.netlify.app/ (see Deploy Logs)

screenshot of swyxkit in action

screenshot of swyxkit in action

Users in the wild

Key Features and Design Considerations:

Setup

npx degit https://github.com/sw-yx/swyxkit
export GH_TOKEN=your_gh_token_here # can skip if just trying out this repo casually
npm install
npm run start

You should be able to deploy this project straight to Netlify as is, just like this project is.

Deploy to Netlify

Personalization Configuration

As you become ready to seriously adopt this, remember to configure /lib/siteConfig.js - just some hardcoded vars i want you to remember to configure.

export const SITE_URL = 'https://swyxkit.netlify.app';
export const GH_USER_REPO = 'sw-yx/swyxkit'; // used for pulling github issues and offering comments
export const REPO_URL = 'https://github.com/' + GH_USER_REPO;
export const SITE_TITLE = 'SwyxKit';
export const SITE_DESCRIPTION = "swyx's default SvelteKit + Tailwind starter";
export const DEFAULT_OG_IMAGE =
	'https://user-images.githubusercontent.com/6764957/147861359-3ad9438f-41d1-47c8-aa05-95c7d18497f0.png';
export const MY_TWITTER_HANDLE = 'swyx';
export const MY_YOUTUBE = 'https://youtube.com/swyxTV';

Of course, you should then go page by page (there aren't that many) and customize some of the other hardcoded items, for example

  • the Newsletter component needs to be wired up to a newsletter service (I like buttondown, tinyletter, and revue)
  • page Cache-Control policy and SvelteKit maxage
  • site favicons (use https://realfavicongenerator.net/ to make all the variants and stick it in /static)
  • (if migrating content from previous blog) setup Netlify redirects at /static/_redirects

This blog uses GitHub as a CMS - if you are doing any serious development at all, you should give the GH_TOKEN env variable to raise rate limit from 60 to 5000.

When deploying, don't forget to set it in Netlify: https://app.netlify.com/sites/YOUR_SITE/settings/deploys#environment

Optimizations to try after you are done deploying

Further Reading

You can read:

Acknowledgements

Todos

  • implement etag header for github api
  • store results in netlify build cache
  • separate hydration path for mobile nav (so that we could hydrate=false some pages)
  • custom components in MDX, and rehype plugins

About

An opinionated blog starter for SvelteKit + Tailwind + Netlify. Refreshed for 2022!

https://swyxkit.netlify.app/

License:MIT License


Languages

Language:Svelte 66.1%Language:JavaScript 27.0%Language:CSS 4.4%Language:HTML 2.6%