4 ms·

Just out of curiosity, do you write HTML5/CSS inside a text editor with live reload or have you switched to builders like Bootstrap Studio, Webflow, Pingendo et

Just out of curiosity, do you write HTML5/CSS inside a text editor with live reload or have you switched to builders like Bootstrap Studio, Webflow, Pingendo etc.? Asking since I'm converting a design into a template for a Symfony app and when coding with Bootstrap from scratch I'm a bit lost. Even doing basic things like sticky left sidebar and overlapping top navbar (basic admin panel layout) requires lots of StackOverflow digging. Should I give up and just buy templates?

dgb23 6y ago
Sass (scss) & overriding default variables/lists/maps & some custom class/mixin generation (via nested each & includes). I personally like to default to utility classes (builtin + custom) and only build components when they get apparent during development. This is for bespoke designs. YMMV
purerandomness 6y ago
I simply have the documentation open, which is really excellent and doesn't require any other sources. I begin with copying one basic example and building from there. Then I'll tweak the HTML+CSS live in the browser's DevTools until I feel I understand what's happening in the CSS, I switch back to IntelliJ and bake my tweaks into my own custom SCSS extending bootstrap's classes and building on them. Never bought templates as I have the feeling that template authors don't really have the time to really grasp the concepts of bootstrap, nor do they care, and simply tend to pile tons of rules until they have some effect they desire. I felt it's always easier to simply read the docs, and occasionally jump into IRC in ##bootstrap or #css or their Slack when I'm stuck.
williamdclt 6y ago
> inside a text editor with live reload this one > Even doing basic things [...] requires lots of StackOverflow digging It's mostly a matter of getting used to it. If you do it by hand, you tend to better understand the building blocks and it gets easier to compose them into whatever you want. Same as any language or framework, really > Should I give up and just buy templates? Give up, no. Buy templates, why not. They're usually fairly cheap and if it saves you hours of coding, that's fair enough (I'm food with frontend and I buy templates sometimes). But if it's a skill you need, it's probably a better investment to hone it than to work around it
celicaraptor 6y ago
As a novice in front end stuff, i have tried Bootstrap Studio but i found it to complicated to use and have since coded my websites through documentation and examples.Perhaps if i have stuck through the learning curve i would prefer it. Templates can help you a lot but be careful.Extending the template to fit your needs does require work and knowledge
tracker1 6y ago
Today, I'd probably just use parcel and reference bootstrap from source in an index.scss from my index.html file... Not the fasted performance option, but works well enough and quickest getting started option for more modern projects.

dgb23 6y ago

Sass (scss) & overriding default variables/lists/maps & some custom class/mixin generation (via nested each & includes). I personally like to default to utility classes (builtin + custom) and only build components when they get apparent during development. This is for bespoke designs. YMMV

purerandomness 6y ago

I simply have the documentation open, which is really excellent and doesn't require any other sources. I begin with copying one basic example and building from there. Then I'll tweak the HTML+CSS live in the browser's DevTools until I feel I understand what's happening in the CSS, I switch back to IntelliJ and bake my tweaks into my own custom SCSS extending bootstrap's classes and building on them. Never bought templates as I have the feeling that template authors don't really have the time to really grasp the concepts of bootstrap, nor do they care, and simply tend to pile tons of rules until they have some effect they desire. I felt it's always easier to simply read the docs, and occasionally jump into IRC in ##bootstrap or #css or their Slack when I'm stuck.

williamdclt 6y ago

> inside a text editor with live reload this one > Even doing basic things [...] requires lots of StackOverflow digging It's mostly a matter of getting used to it. If you do it by hand, you tend to better understand the building blocks and it gets easier to compose them into whatever you want. Same as any language or framework, really > Should I give up and just buy templates? Give up, no. Buy templates, why not. They're usually fairly cheap and if it saves you hours of coding, that's fair enough (I'm food with frontend and I buy templates sometimes). But if it's a skill you need, it's probably a better investment to hone it than to work around it

celicaraptor 6y ago

As a novice in front end stuff, i have tried Bootstrap Studio but i found it to complicated to use and have since coded my websites through documentation and examples.Perhaps if i have stuck through the learning curve i would prefer it. Templates can help you a lot but be careful.Extending the template to fit your needs does require work and knowledge

tracker1 6y ago

Today, I'd probably just use parcel and reference bootstrap from source in an index.scss from my index.html file... Not the fasted performance option, but works well enough and quickest getting started option for more modern projects.