- Ready-made CSS stylesheets for Markdown, just copy the assets folder you want
- Bundled with
generate-md
, a small tool that converts a folder of Markdown documents into a output folder of HTML documents, preserving the directory structure - Use your own custom markup and CSS via
--layout
. - Support for relative paths to the assets folder via
{{assetsRelative}}
and document table of content generation via{{toc}}
. - Support for generic metadata via a meta.json file
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<meta name="viewport" content="width=device-width, initial-scale=1"> | |
<meta name="description" content="Bootstrap: Android select menu fix"> | |
<link href="http://maxcdn.bootstrapcdn.com/bootstrap/latest/css/bootstrap.css" rel="stylesheet" type="text/css"> | |
<title>JS Bin</title> | |
<style id="jsbin-css"> | |
body { |
layout | title |
---|---|
post |
Example content |
Jekyll is, at its core, a text transformation engine. The concept behind the system is this: you give it text written in your favorite markup language, be that Markdown, Textile, or just plain HTML, and it churns that through a layout or series of layout files. Throughout that process you can tweak how you want the site URLs to look, what data gets displayed in the layout, and more. This is all done through editing text files, and the static web site is the final product.
A basic Jekyll site usually looks something like this:
.
├── _config.yml
This project aim is to provide general solarized light and dark colorschemes for HTML documents.
Basically I wanted [solarized][1] colorschemes for [org-mode][2] HTML exports. It is supposed to be used as a single stylesheet for HTML documents that uses regular HTML elements.
Repository: [http://github.com/thomasf/solarized-css][3]
Is your family stuck in a rut? Are you bored? Do you find yourself wondering how you got so far off track?
All families go through times like these occasionally. I know I would love to be able to push a pause button and just sit, regroup and get back on track.
While that's not literally an option, life doesn't come with a pause button, there are ways we can get back in touch with our families. With a bit of effort it is possible to get in sync, connect and move forward in a deliberate and meaningful way as a team.
Bootstrap (currently v3.3.1) has a few easy ways to quickly get started, each one appealing to a different skill level and use case. Read through to see what suits your particular needs.
![][1]
In the world of text editors, there's a plethora of options out there. If you've ever Googled "how to edit HTML sites" or some such, you know what we mean. Allow us, then, to introduce you to VIM, a free website editor that offers many of the same features as Adobe Dreamweaver, and runs on just about every desktop platform. Specifically, it comes by default on the vast majority of Linux distributions, OS X and commercial Unix systems. (It's available to install on Windows, too.) And did we mention it's free? That command line UI isn't necessarily self-explanatory, though, so join us after the break for a quick crash course to help you get started.
If you're running OS X or Linux, start out by opening a terminal. Now type "vim" et voilà: you're using VIM and you didn't even install it. Using Windows? Head over [here][2] and grab the binaries for Windows. Double-click the installer and you'll have VIM on Windows in no time.
So, what is GitHub Flow?
- Anything in the master branch is deployable
- To work on something new, create a descriptively named branch off of master (ie: new-oauth2-scopes)
- Commit to that branch locally and regularly push your work to the same named branch on the server
- When you need feedback or help, or you think the branch is ready for merging, open a pull request
- After someone else has reviewed and signed off on the feature, you can merge it into master
- Once it is merged and pushed to ‘master’, you can and should deploy immediately