Factor reusable components into material-foundation/milemarker

[appsforartists]

From #3, here's one potential plan:

• Move the repo to material-foundation. Call it milemarker.
• Remove the configuration assumptions in the material-foundation repo. Provide a clear place to fill things out.
• Fork the material-foundation repo to material-motion. Call it material-motion-milemarker.
• Make a local modification to our fork with the configuration.
• Deploy the code to gh-pages.

This gives a healthy balance of configuration, minimal overhead, and the ability for others to hack on the project as well.

[jverkoey]

I think that milemarker could also infer the org/username by looking at the published url. This would mean you simply fork the repo and it'll immediately start serving the correct information for your org.

[appsforartists]

That'd be cool.

Would you leave the {js,objc,swift,android} parser/tabs in the main repo (and let people fork if they have different conventions)? Anything else in here that's Motion-specific?