Skip to content

Instantly share code, notes, and snippets.


Mark Statkus cybercussion

View GitHub Profile
cybercussion / gist:11192402
Last active August 29, 2015 14:00
Prerequisite style imsmanifest.xml
View gist:11192402
<?xml version="1.0" encoding="UTF-8"?>
<manifest xmlns:adlcp="" xmlns:imsss=""
xmlns:adlnav="" xmlns:xsi=""
xmlns:adlseq="" xmlns:lom=""
xsi:schemaLocation=" imscp_v1p1.xsd adlcp_v1p3.xsd adlseq_v1p3.xsd adlnav_v1p3.xsd imsss_v1p0.xsd lom.xsd"
identifier="ims_sequencing_objectives" version="1.0.0" xmlns="">
<schema>ADL SCORM</schema>
<schemaversion>2004 3rd Edition</schemaversion>
View Sample-Directory-Output
"name": "imsmanifest.xml"
"contents": [
"contents": [
"contents": [
cybercussion / config.js
Last active August 29, 2015 14:12
Sample RequireJS setup with some light failover for CSS.
View config.js
/*global requirejs, define, require, CI, $, jQuery */
/*jslint devel: true, browser: true */
* Require Config
* This is all the core scripts needed to be available at runtime.
* Includes CDN and local file fail over.
* Shim will control the availability of dependent libraries/scripts.
* domReady included to insure it all kicks off right.
* @usage <script data-main="js/config" src="js/vendor/requirejs/require.min.js"></script>
cybercussion / index.html
Last active August 21, 2017 21:29
Merge Test #jsbench #jsperf ( #jsbench #jsperf
View index.html
<!DOCTYPE html>
<meta charset="utf-8"/>
<title>Merge Test #jsbench #jsperf</title>
<script src=""></script>
<script src="./suite.js"></script>
<h1>Open the console to view the results</h1>
cybercussion / gist:4675334
Last active August 29, 2017 17:02
This is a more full sample of a SCORM 2004 Learner Attempt with objectives, interactions, comments etc ...
View gist:4675334
"cmi": {
"_version": "1.0",
"comments_from_learner": {
"_children": "comment,location,timestamp",
"_count": "8",
"0": {
"comment": "This is a comment from learner",
"location": "QUnit Test",
"timestamp": "2013-01-28T15:04:39.1-08:00"

General Tips for CloudFront + S3 for Static Sites or going "headless"

This assumes you've setup a AWS Account and logged into the AWS Console. Any one new to AWS there is also a CLI available. AWS will give you a root AccessKey and Token, and from that point forward you can configure users through IAM.

Important things to note since there is a order/method to your setup. Do things out of order and it may require you to Invalidate paths since CloudFront will cache your site in edge locations. You are allowed 2000 path updates until they start charging you. So if you have a ton of files, use that feature sparingly. What gets cached?