- Elm type safety plus even more!
- Missing Env variables as compiler warning
- Build time API data as compiler warning
- SEO as compiler warning
I had elm & Netlify experience, but not elm-pages
or elm-ui
.
- Took ~16 hours to convert the demo app to a the current content.
- Is
elm-pages
a suitable option for personal small projects?-
Yes
-
- Is
elm-pages
a suitable replacement for Jekyll? - Cloudinary for hosting static images
elm-ui
was a great experienceStaticData
was also great (load API data on deploy vs. live)
npm start
==elm-pages develop
npm run build
==elm-pages-beta
# AKA prod artifact, this is the new partnpm run serve
- host static files from βοΈ without watch
Development Example for others trying out `elm-pages`
I cloned DKs repo and checked out his Template Modules branch
Started a new page test.md
and followed the compiler
- frontmatter error on
published: "2020-12-30"
needed quotes around date - author needed, add
-
Problem with the value at json.author: "Aaron Votre"
-
- author image doesn't exist
-
, avatar = Pages.images.author.aaron (does not have aaron field)
- Slightly harder to find because that file is generated from the
image/X
directory
-
- built, but my page stinks
- Wondering how to add custom things inline
- example - inject a bit of elm defined UI into my markdown
- discovered in
MarkdownRenderer.elm
you can add custom tags and then it basically gets built like react with uppercase tags <BOX>
example and this article on the elm markdown rendered
- β Browser title (1hr, several revisions)
- β Remove extra blog posts (tiny)
- β Create landing page (med)
- β Update header links (small)
- β Code syntax highlighting (3hr, include elm lib for it, tried embedded JSβ¦failed)
- β Missing monokai styling in deployed version
- β Favicon (2hr, cloudinary + understanding beta build)
- β
Spotify Page
- β Load Data (~3hr)
- β
Style Data (2hr, learned
elm-ui
) - β
Write content (big)
- β First Draft
- β 2nd Version
- β Get Feedback
- β Final Edit
- β release on github