@jakobloekke I have a need to create a theme for my company with a "sticky sidebar" layout and the code snippets below the rendered markup. Similar to this (less the mobile phone of course):
http://ionicframework.com/docs/components/#header

Obviously, pulling this off is pretty involved. I have managed to do this, and have it default to the "original" theme (EDIT: made some more changes so it's currently defaulting to sidebar theme, but I can easily change this back to "original" later).

I did have to hack on tdcss.js a bit. So I'm not sure how you feel about it...

I do think this capability would be highly desirable as an option. That said, it would probably be good to someday (when anybody has time for hacking open source 👅) to create a subclass callback hook sort of thing for theming. This would default to "original" and subclassers would be able to override. That said, I simply don't have time to implement such a thing right now as work is an absolute bottleneck at present.

Anyway, for this branch, would you like me to just maintain a forked branch? Would you want to create a sidebar-experiments base branch in your repo and I can submit to that? Or just merge in to develop? Please let me know how you feel about this. Thanks.

Here's the code:
https://github.com/roblevintennis/tdcss.js/compare/jakobloekke:develop...sidebar-theme?expand=1

Also, I didn't get a chance to intialize with the diff:true option so I'm pretty sure the CSS for that wouldn't yet work. If you advise overall, I'll be happy to make changes if I can get enough spare cycles to do so

Underscore character (_) in snippet name causes:

 TypeError: Cannot read property 'trim' of undefined
 at getFragmentScriptHTML

https://dl.dropboxusercontent.com/u/2886688/web/tdcss.js/index.html

Would love to see it though.

When fragment height is specified, the horizontal scroll bar for the code display box disappears out of view

This is currently only applicable to the develop branch

@jakobloekke It's pretty simple to activate the sidebar but no one will likely find without some sort of indication that it's available and how to use. I'd normally put such docs in a README but I notice you keep yours sparse and defer to the web site. Let me know if you'd like some help or if you'd prefer to do it yourself?

As for activation of sidebar, it's as simple as uncommenting following section of demo/index.html:

    <!--  ORIGINAL THEME -->
    <link rel="stylesheet" href="../build/themes/original/tdcss.css" type="text/css" media="screen">
    <script type="text/javascript" src="../build/themes/original/theme.js"></script>

    <!--  SIDEBAR THEME -->
    <!-- <link rel="stylesheet" href="../build/themes/sidebar/tdcss.css" type="text/css" media="screen"> -->
    <!-- <script type="text/javascript" src="../build/themes/sidebar/theme.js"></script> -->

Also, as a second iteration, the whole theming callback arch should probably be explained for potential other theme writers, and I'd be happy to write something there too (and even later add a few more useful hooks that could be optionally "no opt'd", as I only added callback hooks as needed for the sidebar theme). Just let me know how and where you'd prefer that submittion ✌️ 😄

Oh, and of course, you can go ahead and just reassign this back to me if you'd like me to do it and provide above info for me! Thanks @jakobloekke