Typeplate StarterKit organisation and use case

[mistergraphx]

Hi,

Since last months, i've played around, tested and used TypePlate StarterKit on different projects. So i just post this issue as a reflexion and user experience return ;-)

To use TypePlate as a starter or base usable in completely different projects, i've tried multiple way and solutions. Finally the more flexible way i've found is to separate in multiple files the Typeplate core, as it is in Compass for example:

|-> Typeplate.scss
|-> _variables.scss
|-> _core.scss (mixins, placeholders, functions : re usable in projects)
|-> _styles.scss (for those who want a starting point and override in their own styles)

In this way, a user which want to quickly start, can import the whole Typeplate Kit, and others can import the core component and use placeholder, mixins in their sass projects without taking care or overriding TypePlate Styles (importing styles or rules they 'll never use). Yes, its just some kb but optimisation is this sort of fight ;).

Just my opinion ...and how i use TypePlate
Best regards and thanks for your work.

[grayghostvisuals]

Thanks for your suggestions. I would encourage you to take a look at the namespacing branch currently that has some of these suggestions already awaiting to be released :)

[mistergraphx]

Whoooo ;-) in the future i'll look and use the dev branch before posting an issue, i promise ^^
Thx