fwdekker.com
/
error-pages
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Error pages for my website. https://fwdekker.com/error/404.html
7 Commits 1 Branch 0 Tags 549 KiB
JavaScript 52.3%
Nunjucks 47.7%
Go to file
Florine W. Dekker ee6a427a0a
Migrate to npm and use 11ty 
Fixes #2. Fixes #3.
 		2021-05-08 16:38:50 +02:00
src/main Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
.editorconfig Fix formatting of pages 2021-03-22 20:48:38 +01:00
.eleventy.js Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
.gitattributes Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
.gitignore Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
Gruntfile.js Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
LICENSE Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
README.md Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
package-lock.json Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00
package.json Migrate to npm and use 11ty 2021-05-08 16:38:50 +02:00

README.md

Error pages

The error pages used on fwdekker.com (and probably some related domains as well).

Development

Requirements

Setting up

# Install dependencies (only needed once)
$> npm ci

Building

# Build the blog in `dist/` for development
$> npm run dev
# Build the blog in `dist/` for deployment
$> npm run deploy

You may need to change the pathprefix option of Eleventy when using WebStorm so that the root of the blog is changed to /error-pages/dist/ instead of /.