Moved to https://github.com/metaflop/metaflop-www/wiki/Contribute-a-MF-to-Metaflop
This is a rough draft, work in progress
The structure is planned to change, but for now this is how a metaflop font should look like to be compatible with metaflop.
- Create the required files structure, have a look at e.g. https://github.com/metaflop/metaflop-font-bespoke and https://github.com/metaflop/metaflop-font-fetamont.
- Create a file font.mf in the top level directory. This is the starting point which will be invoked.
- Map all the variables that should be exposed in the UI as slider or a dropdown. See https://github.com/metaflop/metaflop-www/blob/master/app/lib/font_parameters.rb#L47-L79 for reference which variable names you can use.
- The variables that should not the visible as adjustable parameters in the UI need to be postfixed with @hidden (https://github.com/metaflop/metaflop-font-fetamont/blob/master/font.mf#L14)
- Define the adjustable range of the parameter as $ <lower_bound> / <upper_bound>, e.g. $ 3 / 6 (https://github.com/metaflop/metaflop-font-fetamont/blob/master/font.mf#L16)
- Optional: Put all your glyph files in a sub directory "glyphs". You can there further create sub directories as you like.
- Optional: Create a top level glyphs.mf that references all the other glyph files. This way you only need to include the glyphs.mf in your font.mf.
- Create a github repository, which we then can fork and include. This is optional, but is the easiest way.
- Tell us about it (e.g. in a tweet, through a github issue)