nialbima
commented
6 years ago Some stuff to consider:
- how do we easily/quickly set up a co-branded site?
- how fast is it to build a standard component? (i.e. if we need a form, how much custom css should we do? how do we do "basically none"?)
- how hard is it to debug/track down a display issue?
- how do we avoid file-count bloat? (as in, if we have a separate CSS file for each new component that draws from a base set of classes, that could quickly snowball into hundreds of files + classes)
- what kind of naming conventions do we want to use? (i've been dash-casing the JS filename and using that, but if we're use the three-ducks pattern that won't quite match up).
- can we improve render/build speed if we do this intelligently? (probably!)
On Fri, Dec 8, 2017 at 1:59 PM, jaredmurphy notifications@github.com wrote:
How can we make our css more
1.
reusable and/or extensible 2.
maintainable 3.
faster 4.
pretty
Discuss patterns & implementation
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/airtailor/react-express-fe/issues/28, or mute the thread https://github.com/notifications/unsubscribe-auth/AFdIlTt9EbOIPHgGRfNmKeM_HfZoJP_xks5s-YcSgaJpZM4Q7gcw .
How can we make our css more
reusable and/or extensible
maintainable
faster
pretty
Discuss patterns & implementation