What are some sane and future-proof models of organizing (web) components (both UI & non-UI) that you use/used successfully? Some links would be greatly appreciated.
Thanks! That's kinda what I need - some hierarchy of a lot of components of various kinds, maybe from a working (preferably big/huge) project with tons of nested pieces. Usually, methodologies like BEM, OOCSS work for a certain direction, but those are more like guidelines, not actual directory/filesystem-wise organization.
3 comments
[ 2.7 ms ] story [ 19.5 ms ] threadBest example of course is ruby on Rails