Update changelog.

CHANGELOG-ELM.md

@@ -9,6 +9,26 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+## [5.0.0] - 2020-03-28
+
+### Changed
+- Use builder pattern to build application. In place of the old `Pages.Platform.application`, you now start building an application config with `Pages.Platform.init`, and complete it with `Pages.Platform.toProgram`. You can chain on some calls to your application builder. This is handy for creating plugins that generate some files and add some head tags using `withGlobalHeadTags`.
+- The `documents` key is now a List of records. The `Pages.Document` module has been removed entirely in place of a simplified API. `elm-markup` files no longer have any special handling
+  and the direct dependency was removed from `elm-pages`. Instead, to use `elm-markup` with `elm-pages`, you now wire it in as you would with a markdown parser or any other document handler.
+- Replaced `generateFiles` field in `Pages.Platform.application` with the `Pages.Platform.withFileGenerator` function.
+- Instead of using the `zwilias/json-decode-exploration` package directly to build up optimizable decoders, you now use the `OptimizedDecoder` API. It provides the same drop-in replacement,
+  with the same underlying package. But it now uses a major optimization where in your production build, it will run a plain `elm/json` decoder 
+  (on the optimized JSON asset that was produced in the build step) to improve performance.
+
+### Added
+- Added `Head.Seo.structuredData`. Check out Google's [structured data gallery](https://developers.google.com/search/docs/guides/search-gallery) to see some examples of what structured
+  data looks like in rich search results that it provides. Right now, the API takes a simple `Json.Encode.Value`. In the `elm-pages` repo, I have an example API that I use, 
+  but it's not public yet because I want to refine the API before releasing it (and it's a large undertaking!). But for now, you can add whatever structured data you need,
+  you'll just have to be careful to build up a valid format according to schema.org.
+- `Pages.Directory.basePath` and `Pages.Directory.basePathToString` helpers.
+- You can now use `StaticHttp` for your generated files! The HTTP data won't show up in your production bundle, it will only be used to produce the files for your production build.
+- Added `Pages.PagePath.toPath`, a small helper to give you the path as a `List String`.
+
 ## [4.0.1] - 2020-03-28
 
 ### Added

CHANGELOG-NPM.md

@@ -9,6 +9,33 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+## [1.4.0] - 2020-05-11
+
+### Added
+- Added hot content reloading to the dev server! That means that you no longer have to restart your dev server if you add/change a StaticHttp request. You don't even
+  have to reload your browser! It will automatically load in the new data, while keeping your application state. Your markdown (or other format) data, and metadata,
+  from the `content` folder will also load for you without having to restart the dev server or refresh your browser! You'll see a loading indicator to show you when
+  the dev server is loading a new change.
+- `elm-pages` now uses an in-memory cache for `StaticHttp` requests. That means that the dev server won't redo requests that were already being performed as you change
+  code with the dev server running.
+  frontmatter in files in the `content/` folder and save with the dev server running.
+- Files are re-generated as you change your Elm code. Just refresh the generated file URL while running your dev server, and you'll always see the latest version! Note:
+  there's still an issue where if you no longer generate a file, you'll need to restart your dev server to get a 404 when hitting that URL.
+
+### Changed
+- Uses Terser instead of GoogleClosureCompiler to minify the JavaScript bundle in production. GoogleClosureCompiler was causing some issues for Windows users when
+  they ran `elm-pages build` because that dependency has known issues on Windows. See [#90](https://github.com/dillonkearns/elm-pages/pull/90). Thank you very much
+  to [Johannes Maas](https://github.com/Y0hy0h) for the PR!
+
+### Fixed
+- Fixed an issue with the dev server not noticing changes to `.emu` files. See [#78](https://github.com/dillonkearns/elm-pages/issues/78). `elm-markup` files, and files with
+  the `.emu` extension, are handled exactly like any other files in the `content/` folder now. This simplifies the API, and the internal logic is simpler and less error-prone.
+- Decode errors now show error messages correctly for `StaticHttp.unoptimizedRequest`s.
+- `elm-pages` will generate the `gen/Pages.elm` module whether or not there are any errors in the build. This was problematic before this fix because you often need
+  the generated file in order to get it compiling in the first place. So it can cause a chicken-and-egg problem.
+- `elm-pages` is now more reslient to errors so you don't have to restart the dev server as often. There is still a known issue where a dev server restart is needed
+  when you have unfinished `---` for your
+
 ## [1.3.0] - 2020-03-28
 
 ### Added