Add support for building on production.

[izaakschroeder]

Since middleman is actually retarded, we hijack manipulate_resource_list to do the actual font compilation; every SASS file needs to have all its dependants generated by the time this step passes, so this is the only viable entry point. Since the font depends on a directory of files, and not any individual file, we must also monkey patch .template? and .binary? since they only work on regular (non-directory) files. Finally we output the generated fonts as resources in order to keep the Sitemap system happy. no_hash is enabled permanently since it is now the job of :asset_hash.

[izaakschroeder]

This needs cleanup to work with other types of outputs.

[izaakschroeder]

/ping @uetchy this is ready now and actually works.

[uetchy]

Thanks 😃
It looks good but actually doesn't works well on my environment.
I wonder at these changes put css_dir and fonts_dir into "build" dir.
Why "build"?

[izaakschroeder]

Since they are generated files, build seems like the place to put them. That way they are, by default, out of the grasps of version control (like git) and they get picked up by the :asset_hash plugin.

Setup middleman:

sprockets.append_path File.join root, "build", "stylesheets"
sprockets.append_path File.join root, "build", "fonts"

activate :fontcustom do |fc|
  fc.font_name = 'icons'
  fc.source_dir = 'source/icons'
  fc.fonts_dir = 'fonts'
  fc.css_dir = 'stylesheets/components'
  fc.templates = 'scss'
  fc.font_design_size = 62 # picas not pixels
  fc.font_ascent = 850
  fc.font_descent = 150
end

Import icons:

@import "components/icons"

[uetchy]

This looks like more rational way.
But I'm concerned about they might be forcing users to use a bit tricky way like append_path
In addition, these changes put litter of 'scss' and 'svg' on build dir.
What do you think about this?