Although GitHub is great for discussion, I wanted to make sure that changes to the standard, along with the reasoning and impact, are prominently displayed within the CCSS site. To solve that problem, I have taken the built-in static blogging features of Jekyll and exposed that as a changelog.
I have also gone ahead and created some back-dated content.
Although GitHub is great for discussion, I wanted to make sure that changes to the standard, along with the reasoning and impact, are prominently displayed within the CCSS site. To solve that problem, I have taken the built-in static blogging features of Jekyll and exposed that as a changelog.
I have also gone ahead and created some back-dated content.