Bootstrap 4 Cheat Sheet - An interactive Bootstrap 4 cheat sheet

Thanks for your feedback @marek. Placing the snippets and samples on the right side would also cover part of the cheat sheet I think. I decided to put it on the bottom because this way all links are reachable through scrolling at all times. May I ask what screen resolution you're viewing this with?

Thanks for your feedback @joshuapinter. I've considered integrating CodePen links for quickly playing around with the samples, but for now I'd like to keep it simple and avoid overloading it with features. As I've said in the comment above, it's rather meant as a quick lookup table for people working with Bootstrap on a regular basis. The assumption is that when you're using this cheat sheet, you would probably already have a dev environment running where you can fiddle with the component you're using.

@joshuapinter I don't think that's the point of it. I don't know any cheat sheets that let you edit code, nor would I need them. This tool makes it super easy to see all the available components that Bootstrap has to offer without having to trawl through the documentation, and copy the code for your production environment. I can see myself using this on a daily basis (at least until I can memorize all the Emmet shortcuts in Sublime Text).

@parasight Fair enough. I personally prefer to scroll through a section of the official docs and see what might work best for a particular task - they've done such a great job with them. But each to their own. I still think fiddling with it in real-time would be a nice feature, though.

@peedutuisk Except it's not, is it? Plus, you miss out on all the footnotes in the official docs.

@joshuapinter Yea I'm not sure I understand the hype on this one to be honest… Guess I'm just not the target market.

@peedutuisk @joshuapinter I never meant for it to replace the official Bootstrap docs to be honest. The goal was to provide a reminder for people who know Bootstrap already and need to lookup class names quickly - providing a code sample and preview if needed. Ideally it would cover most cases and when it does not, people can drill down into the official documentation for more detailed info.

@arechsteiner That makes sense, thanks.