Skip to content

Instantly share code, notes, and snippets.

@mikofski

mikofski/blogger_codestyle.html

Last active December 18, 2015 18:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mikofski/5824499 to your computer and use it in GitHub Desktop.
Save mikofski/5824499 to your computer and use it in GitHub Desktop.
Download ZIP
CSS inline and block code classes for blogger
Raw
blogger_codestyle.html
<!-- begin CSS styles -->
<head><style type="text/css">
.block-code{
background-color: pink;
border-style: solid none;
border-color: red white;
font-family: "Courier New", Courier, monospace;
}
.inline-code {
background-color: silver;
font-family: "Courier New", Courier, monospace;
}
</style></head>
<!-- end CSS styles -->
To see the <a href="http://xkcd.com">XKCD</a>
Python comic, type: <span class="inline-code">
import antigravity</span>
<!-- begin code-block -->
<pre class="block-code">
&gt;&gt;&gt; import this
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
</pre>
<!-- end code-block -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment