Can somebody give me a checklist or a link on how to develop a Bootstrap theme? (a portfolio theme will do for the moment)
Good lord, why would you want to piss all over a template with that halfwit bloated nonsense that just results in more work, more code, and little if anything resembling sane and rational development.
I hereby decree that forthwith Bootstrap be defined as the 2 square inch area on deathshadows desk where he slams his head once daily out of entirely justified frustration. Nigel
In a very strict sense no not really. I am more on the advertising marketing end of things these days but I know a huge mess when I see it. In no uncertain terms Bootstrap is a huge pile of shit utilized by the uninitiated and lazy. I should note that when I was learning markup I was taught xhtml 1.0 from a fellow in England. They take accessible code much more seriously over there. It has its benefits. I consider myself extremely lucky I learned stuff correctly out of the gate. It has saved me literally months of time that would have been wasted otherwise. I tend to look at stuff like bootstrap like I do Dreamweaver. It simply teaches people very bad practices and stuffs up the internet with slow loading bloated code. There is absolutely no need to have pages of libraries and crazy markup to make some columns and rounded corners. I had a client howling at me about the benefits of bootstrap last week. Not only was he wrong across the board he was attempting to use margins to shove something into a span above where he actually was. Just further evidence folks don't get it. Less is always more, Nigel
Additionally, way too much use of px for instance, its not even remotely semantic for the most part and frankly pretty damn stringent hence hard to modify. I cant for the life of me figure out why classes are used so heavily for presentational matters. The W3C expressly states to not do this so again you wind up with a range of non semantic code. Here is a pretty simple explanation of some of the glaring stupid here. http://blog.terriblelabs.com/blog/2012/01/04/step-away-from-the-presentational-classes/ I like the quote "Its like wearing a t-shirt that is "red" which just so happens to actually be red" Hope that helps a bit. DS does a much better job of explaining this stuff than I do. Nigel
Ok, your paint is still quite green -- we'll need to clarify a few terms. Wordpress isn't even related to the topic -- it is a PHP and mySQL Content management system... Some people MIGHT call it a PHP framework, though that's more what things like Codeignitor are. In-between the two there's Joomla. They all basically act as glue between data stored in databases and your markup (HTML). You still have to make HTML for them to use/output... none of them help you make that HTML in the first place, they are just a means of delivering it. Blueprint, YUI, Bootstrap are HTML/CSS frameworks, allegedly existing to make development of that HTML and CSS easier. Generally they tend to piss all over the entire reason HTML exists, rely on presentational use of tags and classes, and in fact make more work and more fragile sites no matter what their creators and the halfwit fools who use them claim. It's just somethign else to learn that worse, prevents you from learning to do anything properly. JUST WRITE THE HTML AND CSS, forgetting all that framework crap. The same applies to garbage like LESS, SASS, jQuery and a host of other garbage people sleaze onto websites any old way that serves no legitimate purpose other than pissing away accessibility. The process I advocate for making a website "template" is to start out with your content, or at least a reasonable facsimile of what's going into that template for content text and images. It's the "CONTENT FIRST" approach to design and development and plays to the one holy truth of the Internet. Content is King! -- and because it's King content should dictate markup, that markup and content should then dictate layout, and then you can furhter enhance it with other technologies like JavaScript if so desired. This process of working in steps from content to layoutS (yes, plural) is called progressive enhancement -- and it should be done so you have something else called "Graceful degradation". If you make a page that WORKS and is ACCESSIBLE with plain semantic markup and no styling, then slowly add style, scripting functionality and so forth -- the page will still work and be useful to users should any of those bits and pieces along the way be missing, unavailable, blocked, or just not within the capabilities of the device it's being displayed on or even for the user. From there you use CSS to create your layoutS -- YES, PLURAL. Screen, media queries for different layouts on screen, print if so desired -- and that screen layout should be the following things: semi-fluid: meaning it has a maximum width based on the content so that long lines don't get so long as to be hard to read while being able to adjust narrower to fit different screen sizes making best use of the available space. elastic: any minimum or maximum widths, column widths, and font sizes should be declared in EM's -- allegedly the average width of a capitol M in the current font, though that's horse manure on the implementation. This lets the layout auto-size to the users or operating system default. Large font/120dpi users have been around forever, Win7/later will default on some displays to as much as 144dpi (it's not actual DPI, it's another lie), so your site should auto-adjust so users aren't diving for the zoom -- particularly since in anything other than Opera 12/lower zoom is usually a buggy broken unusable wreck. (more so if you don't have a fluid layout!) Both of the above are why px metric fonts and fixed widths are idiotic half-assed bullshit that no self respecting designer should even be THINKING about using, no matter what the artsy fartsy types and lazy sleazeballs might say. responsive: The new kid, reponsive layout is just the next logical step after the above layout concepts. It means using CSS3 'media queries' to change the layout based on the available width. You can strip off columns, change out presentational images and effects, even split existing columns into more columns at this point so as to best use the available space be it a crappy little 192x240 pixel phone right up to a bleeding edge 4096x2560 display. You will ALWAYS hear the lazy ignorant dipshits arguing against everything I just said -- time and time again idiocy like "everyone has a 1024 or wider display" and "None of my visitors use handhelds"; and they've been proven wrong time and time and time and time again over the past TWO DECADES! This is the Internet, the only thing of which we can be certain is we cannot be certain of just who will visit a website or what they or their device are capable of. Properly written HTML should say what things ARE, NOT what they look like, so as to build a logical document structure with a useful order. This gives you a clean baseline as a lowest common denominator... You use numbered headings (h1..h6) to indicate the start of the site (h1), unique subsections of the page (h2), subsections of those subsections (h3) and so forth. If there's no heading text suitable for a marking the start of subsection, you use a horizontal rule to mark a section divider. You have a short list of choices or bullet points, you use a unordered list if they're in no particular order, ordered list if the order is part of the content... if it's big enough to have headers and it's own subsections, it's not a list item so you don't use a list. IF you have a GRAMMATICAL paragraphs, you put it in a P tag... so on and so forth. This plays to the entire reason HTML exists -- device neutral delivery of content! That's why TBL (Tim Berners Lee) CREATED HTML IN THE FIRST PLACE; to say what things are, or would be in professional writing, then let the device best determine how to show that. At the time he was working at CERN dealing with scientific papers and the like -- and it was a good system. Sure, he had tags like B and I, but that's because professionaly written content makes things bold and italic for a reason -- and that gives them a semantic purpose separate from STRONG and EM, no matter what the people who never grasped semantics or don't know enough about writing claim. We got away from that original intent during the browser wars, when the browser makers of the time (Netscape and Microsoft) went ape shit adding stuff just to satiate the needs of the people who only cared about desktop displays and to hell with anything else. The end result was the train wreck known as HTML 3.2 which anyone with a brain has been fighting since the end of the '90's. That was the intent of HTML 4 and CSS -- to separate the two so you could have your accessible device neutral baseline, while targeting specific devices and capabilites. ... and that's why the STYLE tag shouldn't even exist, and the STYLE attribute has no business being used in all but the RAREST of cases... and it's why the LINK tag has a MEDIA attribute, so you can say for what target device your external CSS is for.... and why MEDIA="ALL" is stupid, and why people who omit the MEDIA attribute entirely don't know enough about building websites to be opening their yaps on the subject! Ok, I'll stop ranting for now, getting late here. Bottom line, what I'm saying is use HTML and CSS to make your HTML and CSS, you don't need any stupid halfwit frameworks like YUI, Blueprint or Bootstrap, or goofy dumbass addons or pre-processors like LESS and SASS to do something so malfing simple; unless of course you never take the time to learn to do it properly in the first place... and to be frank, failing to learn to do it properly in the first place is why there are people ignorant enough to see a point to using all that pointless crap... and why most of the websites people vomit up aren't worth a sheet of bog roll.
Wow... thanks DS The sole purpose of my post was to learn a new trick quickly and make bucks hence Bootstrap... I'll make sure I learn the basics your way... Its good to know I am surrounded by committed people.... Thanks all....
We need way more folks like DS around here. Its what makes this place tick. Also... http://www.techdirt.com/articles/20140107/11263425789/not-cool-mpaa-joins-w3c.shtml Because we need a bunch of douchebags that don't know how browsers and google even works sticking their grubby, extortionist hands into web standards. RIP W3C. Nigel
Hello ! Open this URL getbootstrap.com . And click on the Downlaod Bootstrap bottuon. After download this extract it and then click on Components link. Here are so many Components that you need to apply on your themes. Its very easy to use and save your time...
You know, not to sound like a broken record, but I REALLY wish people would stop recommending that idiotic halfwit bullshit that just makes people dumber by it's very existance.