This is the first post on this blog. It is a bit of an experiment, as I am using several new (and new-to-me) techniques for creating and publishing this content
This is the first post on this blog. It is a bit of an experiment, as I am using several new (and new-to-me) techniques for creating and publishing this content. All of the tools are based on standards (formal and de facto) and are freely available.
The Markdown files are then ran through a custom tool that I created. The tool scans a directory for Markdown files (.md extension) and then converts the text to HTML (using the Markdown Sharp library). The resulting HTML is then injected into an HTML template to create the final page. You can see the raw Markdown source used to generate any page by replacing the .html extension with .md (Example: first-post.md).
As of this writing (2012.03.19), the template itself is using the html5boilerplate library, with a side helping of Twitter Bootstrap thrown in for the UI elements, all generated automatically by Initializr.
Anyway, it sounds like a lot of moving parts, but it really makes things quite easy. Just open up a text editor and write the text without worrying about the HTML formatting too much, then click a button and everything is transformed into standards-compliant HTML magically. A simple push to Github and the pages are all updated with full backups, etc.
Let's see how it goes.
How to work around an ARM template limitation when using a Key Vault certificate in a Web App
Quick updates on some Roku libraries that I recently released
How to ensure your CORS headers are properly returned with HTTP error responses on ASP.NET Core
Azure Functions Proxies are awesome - here are just a few ways to leverage them
Although AWS Lambdas are the default, it is dead simple to use Azure Functions for your Alexa skill as well