As of now, only Bootswatch themes are optional. Why not making Prettify themes optional too. And not only this, but supporting local/external paths to custom themes. It would make it really simple to customize the output without messing up with the source code. Maybe something like:
{
// hypothetical strapdown setup
bootstrapTheme: "united", // name, path, or empty for default
prettifyTheme: "sunburst" // name, path, or empty for default
}
Prettify themes may be reached from http://strapdownjs.com/ as no other CDN is available (current version works like this anyway)
Users will be able to load other skins like: http://weblees.com/bootstrap-skins/#.UoZzDGSifbw (not all styles are applicable I know, I know! but any output will be better than Bootswatch anyway).
As of now, only Bootswatch themes are optional. Why not making Prettify themes optional too. And not only this, but supporting local/external paths to custom themes. It would make it really simple to customize the output without messing up with the source code. Maybe something like:
The question is: Is that feasible by any means?