kivikakk

• Any allowed id and name attributes have "user-content-" prefixed to their value.
• A maximum of 2 nested sub or sup tags are allowed.
• A maximum of 10 nested ul or ol tags are allowed.

Allowed Element	Allowed Attributes
All allowed elements	abbr, accept, accept-charset, accesskey, action, align, alt, axis, border, cellpadding, cellspacing, char, charoff, charset, checked, clear, color, cols, colspan, compact, coords, datetime, dir, disabled, enctype, for, frame, headers, height, hreflang, hspace, id, ismap, itemprop, label, lang, maxlength, media, method, multiple, name, nohref, noshade, nowrap, open, prompt, readonly, rev, rows, rowspan, rules, scope, selected, shape, size, span, start, summary, tabindex, title, type, usemap, valign, value, vspace, width
a	As above plus href (must be github-mac, github-windows, http,

nvivo

public static class BundleCollectionExtensions
{
    public static void AddMultipleDirectories<T>(this BundleCollection bundles, string appRelativePath, params string[] directories)
    where T : Bundle
    {
        var list = new List<string>();

        foreach (var dir in directories)
        {
            bundles.Add<T>(dir);

domenic

Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.

Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.

Paths and URLs

On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation