These are required by web browsers.

meta(charset="UTF-8")
meta(name="viewport", content="width=device-width, initial-scale=1.0")

We should separate snippet.pug (just the snippet code) from the page it's rendered on. This will give us more flexibility when embedding the snippet directly on someone else's page.

Snippets should only show the primary slice's file and range in the collapsed state.

• Update API to use file:startLine:endLine slice syntax
• Parse and verify slices in the new format
• Parse and verify multiple slices

This needs to end up in our Pug template file, but you can prototype it using our demo-page.html. We need to convert the right-side button to link to GitHub.

We'll copy GitHub's behavior of returning a script that adds a bunch of elements to the user's DOM, including a link to our stylesheet

snippet {
    /* shared style */
}

snippet--dark {
    /* dark style */
}

snippet--light {
    /* light style */
}

I'm marking this as a bug because our current approach of two stylesheets is error-prone.

This a stretch goal. It would minimize our JavaScript payload to the client and it feels like the right thing to do.

This bug makes it really annoying to write to the DOM. Our code will be wrapped in document.write('...'), so any single quote characters will break the system. This makes me feel like we are overlooking a step, but in the Spirit of the Hackathon I say we choose the quick fix.

Consider using an external library like highlight.js

Blocked by #25

• Tab switching
• Expand/collapse

Right now we are fetching the page where the icon lives, not the actual file. We need to use https://raw.githubusercontent.com/jesseweed/seti-ui/master/icons/{language}.svg

public/snippet-script.js and public/snippet-style should be updated on Azure storage whenever they are modified.

Here's an example:

Render a snippet

https://digist.azurewebsites.net/gist/{gist_id}?file={file}&slice={slice}&theme={theme}

Originally posted by @jungaretti in #63 (comment)

Azure App Service deployment is broken up after each commit until I toggle the plan from free to paid to free, so README.md should probably include directions for running Digist locally

• Dummy content to get started with Pug 😀
• Static, unstyled content
• Static content
• Final result

https://nodejs.org/es/docs/guides/anatomy-of-an-http-transaction/

We need to provide:

• File names.
• File contents.
• Gist URL.

I tried to show my friend our beautiful project this evening, but Azure App Service is not cooperating. I think something is either wrong with Azure or wrong with the resource. I'll try to deploy again tomorrow.

Icons are here: https://github.com/jesseweed/seti-ui

I think we could do something like <img src="https://raw.githubusercontent.com/jesseweed/seti-ui/master/icons/{extension}.svg" alt="{language}">

These files will be available on Azure soon...

We'll deploy our service using Azure App Service.

Repro Steps

• Visit https://gist.github.com/jwparsons/b8bcfe1023296fabe6eb66dbfbaa684e
• Notice that test.cpp has 34 lines
• Visit https://digist.azurewebsites.net/gist/b8bcfe1023296fabe6eb66dbfbaa684e?file=test.cpp&slice=14:34
• Notice that an invalid range error appears
• Visit https://digist.azurewebsites.net/gist/b8bcfe1023296fabe6eb66dbfbaa684e?file=test.cpp&slice=14:33
• Notice that the request returns successfully

I'd expect https://digist.azurewebsites.net/gist/b8bcfe1023296fabe6eb66dbfbaa684e?file=test.cpp&slice=14:34 to be a valid request since test.cpp has 34 lines.

https://css-tricks.com/bem-101/