not really known
Go to file
2019-10-19 10:02:35 -07:00
.idea Update idea workspace. 2019-10-19 10:02:35 -07:00
elm-package/src/Pages Add starting point for function to extract StaticRequests for each page. 2019-10-19 10:02:28 -07:00
examples/docs Add starting point for function to extract StaticRequests for each page. 2019-10-19 10:02:28 -07:00
generator Add starting point for function to extract StaticRequests for each page. 2019-10-19 10:02:28 -07:00
src Initial prototype to fetch static data. 2019-10-15 22:16:49 -07:00
tests Move modules over in preparation for elm package publish. 2019-09-15 16:05:40 -07:00
.gitignore Run webpack server for elm-pages build. 2019-08-14 09:57:04 -07:00
.travis.yml Change node version for travis script to see if it fixes build error. 2019-10-07 08:37:05 -07:00
CHANGELOG-NPM.md Add onUrlChange to Pages.application (fixes #4). 2019-10-08 20:36:54 -07:00
CONTRIBUTING.md Add contributing guide. 2019-10-08 19:59:08 -07:00
elm.json Move modules over in preparation for elm package publish. 2019-09-15 16:05:40 -07:00
index.js Initial prototype to fetch static data. 2019-10-15 22:16:49 -07:00
jsconfig.json Setup jsconfig.json to check TypeScript against js files. 2019-09-16 15:22:05 -07:00
LICENSE Add LICENSE file. 2019-09-20 13:58:20 -07:00
netlify.toml Update netlify config to run build script for generated elm file. 2019-09-15 21:53:32 -07:00
package-lock.json Bump npm package to 1.0.37. 2019-09-28 11:00:19 -07:00
package.json Bump npm package to 1.0.37. 2019-09-28 11:00:19 -07:00
README.md Add NPM and Elm package badges to README. 2019-10-08 19:50:40 -07:00

elm-pages Netlify Status npm Elm package

Deploy to Netlify

A statically typed site generator, written with pure Elm.

Getting Started Resources

Key features

SEO made easy

With elm-pages, SEO is as easy as calling a type-safe, high-level Elm API and passing in data from your content's metadata.

The metadata is just Elm data that you define however you want, using a Json Decoder to grab data out of your markdown frontmatter.

import MyMetadata exposing (MyMetadata)

head : BlogMetadata -> List (Head.Tag Pages.PathKey)
head meta =
  Seo.summaryLarge
    { canonicalUrlOverride = Nothing
    , siteName = "elm-pages"
    , image =
      { url = PagesNew.images.icon
      , alt = meta.description
      , dimensions = Nothing
      , mimeType = Nothing
      }
    , description = meta.description
    , locale = Nothing
    , title = meta.title
    }
    |> Seo.article
      { tags = []
      , section = Nothing
      , publishedTime = Just (Date.toIsoString meta.published)
      , modifiedTime = Nothing
      , expirationTime = Nothing
      }

Optimized for performance

elm-pages has a set of features built-in to make sure your page is blazing fast on any device.

  • Automatic page pre-rendering
  • Page content is split up per-page so page content downloads and parses just-in-time
  • Page pre-fetching on link hover

Try out elm-pages, open up Lighthouse, and see for yourself! Or check out https://elm-pages.com (find the source code in the examples/docs/ folder).

Built-in type-safety

elm-pages generates static Elm data for you to make sure you don't have any broken links or images. The SEO API even uses it to make sure you are only pointing to valid images and pages so you have valid metadata!

For example, if you have a content folder like this:

- content
  - blog
    - index.md
    - hello-world.md
    - second-post.md

Then you will be able to access those pages in a type-safe way like this from Elm:

-- this is a generated module
-- it is re-run whenever your `content` folder changes
-- just run `elm-pages develop` to start the watcher
import Pages exposing (pages)
import Pages.PagePath as PagePath exposing (PagePath)


indexPage : PagePath Pages.PathKey
indexPage =
  pages.blog.index


helloPostPage : PagePath Pages.PathKey
helloPostPage =
  pages.blog.helloWorld


secondPost : PagePath Pages.PathKey
secondPost =
  pages.blog.secondPost

Offline Support

elm-pages uses pure elm configuration to setup your progressive web app settings. This includes a "source icon" which is used to generate your favicons and icons for the images following best practices for a progressive web app. The image is even a type-safe ImagePath that guarantees you are using an available image!

manifest : Manifest.Config Pages.PathKey
manifest =
    { backgroundColor = Just Color.white
    , categories = [ Pages.Manifest.Category.education ]
    , displayMode = Manifest.Standalone
    , orientation = Manifest.Portrait
    , description = "elm-pages - A statically typed site generator."
    , iarcRatingId = Nothing
    , name = "elm-pages docs"
    , themeColor = Just Color.white
    , startUrl = pages.index
    , shortName = Just "elm-pages"
    , sourceIcon = images.icon
    }

It will also take care of setting up a service worker which will automatically cache the basic shell for your application's compiled Elm code and HTML container. The page content is currently cached as it is loaded, but in the future there will be an API to choose some pages to "warm up" in the cache.