Creating a grunt build system for octicons v4.0.0

[jonrohan]

This is a WIP to create a grunt build system for octicons that will out put both font files and svg files.

The tl;dr of what I'm trying to do is:

• SVG icon files will be placed in src/svg
• The developer will run grunt
• All assets are compiled to dist

@aaronshekey @github/css

[aaronshekey]

Yes! This is super awesome and addresses #88 and #87.

[jonrohan]

@aaronshekey I have this working pretty well, but there's some weird hinting going on
need to fine tune it.

Plus here's a few more things I want to address

• Stuff labeled v4 https://github.com/github/octicons/milestones/v4.0.0
• Update site to show svg and font
• A little bit better organization of dist folder with styles and resources properly organized

[aaronshekey]

Yeah, that is rendering strangely. Some of the unicode symbols have changed between this and prior versions, right? That may be an issue, though I can't be sure how everyone's using Octicons. I'm not sure how high of a priority it is though.

[mdo]

I haven't pulled down the code to see the full diff yet, but I'm seeing hella _posts files. How performant is that looking vs something like a data file?

[jonrohan]

but I'm seeing hella _posts files. How performant is that looking vs something like a data file?

I pulled that directly from https://github.com/github/octicons.github.com in the interest of combining all the 3 repos for octicons. I would be into updating it to use a data map though. 👍

[jonrohan]

Some of the unicode symbols have changed between this and prior versions, right? That may be an issue

The beauty of a major update https://github.com/github/octicons#versions we're telling people it's breaking changes. 4.0.0

[aaronshekey]

We're telling people it's breaking changes.

With this build system, any additional symbol will be a breaking change, right?

[mdo]

major update [...] breaking changes

🙌 🙌 🙌

[jonrohan]

With this build system, any additional symbol will be a breaking change, right?

I guess so, but we can create a character code map to keep them similar. https://github.com/sapegin/grunt-webfont#codepoints

[sophshep]

I think this is similar to what Grunticon does, though they don't create a font. (Which is fine for our use internally, imo)

I just got that up and running in a PR on the new help site and so far it is working great.

[aaronshekey]

@sophshep I think we may indeed want to keep the font around for local Keynote presentations and the like. I've added the pre-established codepoints, so we should be covered ✌️

[jonrohan]

I'm going to merge this in, leaving the version at 3.5.0, not publishing anything new to npm. So I can do some testing in the github/github pipeline