HotDocs: Static export

Create a static build with Parklife :

1. bundle add --group development parklife
2. bundle exec parklife init --rails
3. Update Parklife
4. Update bin/static-build
5. bin/static-build

You can test the static export with:

ruby -r webrick -e 'WEBrick::HTTPServer.new(Port: 8000, DocumentRoot: "build").start'

Refer to the Parklife docs for details on how to tweak the configuration.

Fetch fresh content

There are situations where a static build is limiting. For example, you may have a page that loads some data from the database:

Registered users: #{User.registered.count}

If you exported that page from a development environment, the count would be wrong. And, even if you managed to export it from the production database, the count would be outdated.

You can work around this issue by using the fetcher helper:

After setting fetcher_host in hotdocs_helper.rb, wrap content in a fetcher block to fetch dynamic content from the backend.

For example, given the following is statically exported:

<div id="someid" data-controller="fetcher" data-fetcher-host-value="http://127.0.0.1:3000" data-fetcher-path-value="/my/path" data-fetcher-fallback-value="Registered users: Loading..." style="visibility: hidden;">
  Registered users: #{User.registered.count}
</div>

1. On the first load, the fallback is rendered:

Registered users: Loading...

2. the fetcher gets fetcher_host + path, which is expected to contain either:

<div id="someid" data-controller="fetcher" data-fetcher-host-value="http://127.0.0.1:3000" data-fetcher-path-value="/my/path" data-fetcher-fallback-value="Registered users: Loading..." style="visibility: hidden;">
  Registered users: #{User.registered.count}
</div>

or an element with the correct id:

<div id="someid">
  Registered users: #{User.registered.count}
</div>

3. the content is swapped:

- Registered users: Loading...
+ Registered users: #{User.registered.count}