41–50 of 73 posts
Earlier quoted context omitted.
You check understanding with the low domain-intelligence end of your target audience. That could cause confusion whether someone is the target or not.
Just don't mention that you're choosing them based on their lesser intelligence.
If Bootstrap is taking over the web one project at a time, yours is next. Unless... you take a stand and fight for the right to develop with the freedom not to be forced 75% of the way down the dev path before you've even begun. At the professional web dev level, there's never been a better time to make your own stuff from scratch in HTML and CSS. Working with designers, with UX, with the product team - you can make…
Even if you don't like boostrap, I'd recommend building your own skeleton framework that you can re-purpose without having to spend those first 10-20 hours re-building from scratch every time you start a new project.
Earlier quoted context omitted.
Step 1 - Exclude the .less and .js files that you will not be using. Step 2 - Edit or override the variable.less file. Done
I suspect the answer is read the source, but A) how do I know what bits I will not be using B) how do the JS and LeSS files interact (can I leave out the JS as easily as the less?)
If Bootstrap is taking over the web one project at a time, yours is next. Unless... you take a stand and fight for the right to develop with the freedom not to be forced 75% of the way down the dev path before you've even begun. At the professional web dev level, there's never been a better time to make your own stuff from scratch in HTML and CSS. Working with designers, with UX, with the product team - you can make…
I disagree. Re-scaffolding is a pain in the arse, and if I'm not using something like Bootstrap, I'm using textexpander to re-use snippets, which in effect, is the same thing. Even if you don't like boostrap, I'd recommend building your own skeleton framework that you can re-purpose without having to spend those first 10-20 hours re-building from scratch every time you start a new project.
Bootstrap and others like it just get in the way if you already have something built.
Earlier quoted context omitted.
I suspect the answer is read the source, but A) how do I know what bits I will not be using B) how do the JS and LeSS files interact (can I leave out the JS as easily as the less?)
It's done intelligently, so you don't use tables, then you leave out tables.less. If you don't want tabs, then you leave out tabs.js.
That's really impressive, if accurate. If so many people are using Bootstrap as a default style, it makes me wonder if maybe the default way browser style HTML element shouldn't be closer to what Bootstrap does?
However, of late, I've been doing it this way (rather WIP) -
* Setup a base starting skeleton code (HTML/CSS).
* Include the most important ones such as - normalize, typography and/or a grid.
Start with that and then depending on the size and complexity of the project, add frameworks under "vendor", where bootstrap or foundation or any other framework goes. One thing to be aware is to extract the "configs" and "globals" from the framework you want to use and take it to your "base" starting point.
So,
- BASE (your starting lean code)
- A Vendor framework (Bootstrap, Foundation or just a grid framework like Mueller Grid or just a typography framework like Typeplate)
- Finally, your UI Codes.
Additionally, you an add the following (never goes to production)
- DEBUG Styles
- Shame or design-time-only styles.
This helps in staying lean with your codes to start a project and at the same time, ready to add in the heavy-weights if need be. The remainder is of course the User Interface that you need to design.
Note:
- A CSS pre-processor such as Sass or Less really help in this workflow.
- Following a methodology like BEM[1] or OOCSS[2] can really make life easy.
- The SMACSS[3] Book is a good one to look at.
UPDATE: Here is my current organization (WIP) - https://www.dropbox.com/s/3airw24jdn3snsh/Screen%20Shot%2020...
- It doesn't really fit with my workflow. I find that when I use a framework I end up designing the copy, content, and functionality of my templates to fit within a given confine, which ticks me off. I prefer starting with the content that the page has to display and building the CSS up from there (it helps that I have more front-end experience than the average webdev.)
- I don't like the look of them, for the most part. Yes, you can customize them, but you can still tell who started with a Bootstrap template. No, most customers won't care (or even know what Bootstrap is), but I care, dammit, because I've seen a few dozen too many MVPs that never evolved their design past the "hey, lets change the nav bar to red" stage.
That being said, this is still incredibly inspiring. These frameworks are resulting in more people producing and publishing valuable work, which is awesome. I can't wait to see what the future holds for these projects.
Off topic, I did not know about meanpath and I was looking for a (website) source code search engine for sometime. https://meanpath.com/f/ If they opened all the search results I would surely use this often.
I sometimes use stuff because everyone else is using it. And then I wonder why I did that. I recently removed bootstrap from a website I have that is composed entirely of static HTML documents [1]. It's a teaser / marketing site for my current project. The sample sites looked nice and I figured that since I and CSS are of basically nodding acquaintance -- why not? I discovered that Bootstrap was just too featuresome…
I clearly know why I chose Bootstrap for some of my sites: i) In the past I spent a lot of time with designers and now I can design a site from scratch myself (I am not a web developer). Before bootstrap sites designed by me looked very well on Mosaic :-) ii) If I work with a designer I need to spec a lot of details (bullets, headings, columns, colors) and how the fit together. With bootstrap I know that I can change…
