Astrum - A lightweight pattern library for any web project

@pwheslop Hey, I'll answer on Dan's behalf. So I guess you could think of it like the front-end equivalent of branding guidelines. So as front-end dev's we'd break down a design into reusable chunks of markup/code e.g. different button styles, different navigation styles etc etc. Those all then go into the pattern library (Astrum) for reference by other developers, the designers to ensure consistence and it also acts as documentation for the project. It's particularly beneficial when multiple developers are working on a project and/or when a project is going to be passed around to other teams. In the long term it can reduce future development time because you can review and use your reusable components, documented in the pattern library, rather than dissecting existing templates or worse reinventing the wheel and build the same thing again from scratch.

@pwheslop Ryan answered this much better than I could ;) But thanks for the kind words and following along for the ride :)

@ambrium You're welcome. :-)

@pebutler3 Awesome! Let us know how you get on. :-)

@saenzramiro Thanks Ramiro 🤓

@famouslabs It would depend on your workflow and how you want to approach including a pattern library. Do you use anything currently? Internally, at No Divide, we found we start building reusable code in Astrum prior to building up final templates which becomes a far more quicker process because the reusable code is already in place and tested in isolation. We also find that it helps our designer ensure that his designs remain consistent. Interested to hear where you think the slow downs would be though?

@4ndeh Thanks Andy!