The deckdown regex parser should be able to break up a document by headers. For example this input html fragment:
<h1>Section</h1>
<p>Section Info</p>
<h2>Section</h2>
<p>Section Info</p>
<h1>Section<h1>
#testing | |
*** | |
Just Testing using Gists for Deckdown |
The deckdown regex parser should be able to break up a document by headers. For example this input html fragment:
<h1>Section</h1>
<p>Section Info</p>
<h2>Section</h2>
<p>Section Info</p>
<h1>Section<h1>
console.log("Masonry getting loade by browser. Angular?"); | |
(function () { | |
'use strict'; | |
angular.module('wu.masonry', []).controller('MasonryCtrl', [ | |
'$scope', | |
'$element', | |
'$timeout', | |
function controller($scope, $element, $timeout) { | |
var bricks = {}; |
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
<plist version="1.0"> | |
<dict> | |
<key>quiz</key> | |
<dict> | |
<key>question</key> | |
<array> | |
<dict> | |
<key>text</key> |
{ | |
questions: [{ | |
text: "What does 'API' stand for?", | |
answer: "API stands for Application Programming Interface." | |
},{ | |
text: "What's so good about pragmatic REST?", | |
answer: "It's focused on the api consumer, so it makes it easier for developers to contribute to your app library!" | |
}] | |
} |
<?xml version="1.0" encoding="UTF-8" ?> | |
<quiz> | |
<question> | |
<text>What does 'API' stand for?</text> | |
<answer>API stands for Application Programming Interface.</answer> | |
</question> | |
<question> | |
<text>What's so good about pragmatic REST?</text> | |
<answer>It's focused on the api consumer, so it makes it easier for developers to contribute to your app library!</answer> | |
</question> |