Hacker News new | past | comments | ask | show | jobs | submit login

I am really not trying to stir a pot here. I am truly looking to learn. But the whole idea of bootstrap seems to go against other stuff I used to read about how to use css. I understood that your markup should be semantic and detached from you layout and style as much as possible. But when you use the bootstrap grid to arrange your page, you are absolutely mixing content and layout.

For me, I always thought actually fully separating markup and layout/styling was a pipe dream, and unless you're going to absolutely fill your page with id's and classes (a la zen garden) and spend enormous time tweaking things, then a major overhaul will require changing markup anyway, so why bother? But that seemed to fly in the face of advice I was reading. But using a grid seems to fly in the face of that old advice too. So what's the deal? Do people no longer think markup and styling/layout should be separated? Or was I just misinterpreting what I read in the past?




It's still a good idea to separate markup and styling. In the interest of getting things that look decent out the door quickly it's often necessary to postpone ideological purity.

If your idea proves successful then over time you will need to evolve away from bootstrap anyway, and you can get cleaner markup and style along the way.

If your idea proves unsuccessful, good thing you didn't waste too much time on a pure semantic markup.


Right - grids are basically table-based layout with credibility.

Still, the clue is in the name. "Bootstrap" your app, then faff it into pure web standards over time, should the app prove popular.

Less time wasted on an app you don't know will fly.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: