Skip to content

Commit d984d48

Browse files
fitzgenfitzgen
committed
Adding skeleton and FAQa
1 parent 08b1b63 commit d984d48

File tree

2 files changed

+113
-34
lines changed

2 files changed

+113
-34
lines changed

‎faq.html

+87
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
<!DOCTYPE html>
2+
<html>
3+
<head>
4+
<meta charset='utf-8'>
5+
<meta http-equiv="X-UA-Compatible" content="chrome=1">
6+
<link href='https://fonts.googleapis.com/css?family=Chivo:900' rel='stylesheet' type='text/css'>
7+
<link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen" />
8+
<link rel="stylesheet" type="text/css" href="stylesheets/pygment_trac.css" media="screen" />
9+
<link rel="stylesheet" type="text/css" href="stylesheets/print.css" media="print" />
10+
<!--[if lt IE 9]>
11+
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
12+
<![endif]-->
13+
<title>Source Maps</title>
14+
</head>
15+
16+
<body>
17+
<div id="container">
18+
<div class="inner">
19+
20+
<header>
21+
<h1>Frequently Asked Questions</h1>
22+
</header>
23+
24+
<hr/>
25+
26+
<section>
27+
<h2>Table of Contents</h2>
28+
<ul>
29+
<li>
30+
<a href="#faq1">How do I combined source maps for concatenated
31+
files?</a>
32+
</li>
33+
<li>
34+
<a href="#faq2">How can I modify the compiled output without
35+
corrupting the source map?</a>
36+
</li>
37+
<li>
38+
<a href="#faq3">Can source maps be completely self contained in
39+
the generated source?</a>
40+
</li>
41+
</ul>
42+
</section>
43+
44+
<hr/>
45+
46+
<section id="main_content">
47+
48+
<h3 id="faq1">How do I combined source maps for concatenated files?</h3>
49+
50+
<p>
51+
Build an index map that refers to the individual pieces. See the
52+
spec for details of a index map.
53+
</p>
54+
55+
<h3 id="faq2">How can I modify the compiled output without corrupting
56+
the source map?</h3>
57+
58+
<p>
59+
For simple modifications such as adding a version or comment, if you
60+
can isolate the change into a line by itself, you can modify that
61+
line without affecting any other line. This is possible because the
62+
source maps are line/column based. This also means that you can
63+
append text to the end of the file without modifying the source map.
64+
</p>
65+
66+
<p>
67+
You can add an entire block of text the the beginning of the file by
68+
creating a simple index map see <a href="#faq1">How do I combined source
69+
maps for concatenated files?</a>
70+
</p>
71+
72+
<h3 id="faq3">Can source maps be completely self contained in the
73+
generated source?</h3>
74+
75+
<p>
76+
Yes. Store the text content of your sources in
77+
the <code>sourcesContent</code> property of your source map, and
78+
then embed your source map into your generated source by using a
79+
<code>data://</code> URI in the <code>//#
80+
sourceMappingURL=...</code> comment pragma.
81+
</p>
82+
83+
</section>
84+
</div>
85+
</div>
86+
</body>
87+
</html>

‎index.html

+26-34
Original file line numberDiff line numberDiff line change
@@ -10,64 +10,56 @@
1010
<!--[if lt IE 9]>
1111
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
1212
<![endif]-->
13-
<title>Source-map.github.io by source-map</title>
13+
<title>Source Maps</title>
1414
</head>
1515

1616
<body>
1717
<div id="container">
1818
<div class="inner">
1919

2020
<header>
21-
<h1>Source-map.github.io</h1>
21+
<h1>Source Maps</h1>
2222
<h2>Source map github pages.</h2>
2323
</header>
2424

25-
<section id="downloads" class="clearfix">
26-
<a href="https://github.com/source-map" id="view-on-github" class="button"><span>View on GitHub</span></a>
27-
</section>
28-
29-
<hr>
30-
3125
<section id="main_content">
32-
<h3>
33-
<a name="welcome-to-github-pages" class="anchor" href="#welcome-to-github-pages"><span class="octicon octicon-link"></span></a>Welcome to GitHub Pages.</h3>
3426

35-
<p>This automatic page generator is the easiest way to create beautiful pages for all of your projects. Author your page content here using GitHub Flavored Markdown, select a template crafted by a designer, and publish. After your page is generated, you can check out the new branch:</p>
27+
<h3>About</h3>
3628

37-
<pre><code>$ cd your_repo_root/repo_name
38-
$ git fetch origin
39-
$ git checkout gh-pages
40-
</code></pre>
29+
<p>
30+
TODO: talk about source maps
31+
</p>
4132

42-
<p>If you're using the GitHub for Mac, simply sync your repository and you'll see the new branch.</p>
33+
<h3>Specification</h3>
4334

44-
<h3>
45-
<a name="designer-templates" class="anchor" href="#designer-templates"><span class="octicon octicon-link"></span></a>Designer Templates</h3>
35+
<p>
36+
The <a href="https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit#">source
37+
map specification</a> is hosted on Google Docs.
38+
</p>
4639

47-
<p>We've crafted some handsome templates for you to use. Go ahead and continue to layouts to browse through them. You can easily go back to edit your page before publishing. After publishing your page, you can revisit the page generator and switch to another theme. Your Page content will be preserved if it remained markdown format.</p>
40+
<h3>Discuss</h3>
4841

49-
<h3>
50-
<a name="rather-drive-stick" class="anchor" href="#rather-drive-stick"><span class="octicon octicon-link"></span></a>Rather Drive Stick?</h3>
42+
<p>
43+
All discussion about the source map specification happens on
44+
the <a href="https://lists.mozilla.org/listinfo/dev-js-sourcemap">source
45+
map mailing list</a>.
46+
</p>
5147

52-
<p>If you prefer to not use the automatic generator, push a branch named <code>gh-pages</code> to your repository to create a page manually. In addition to supporting regular HTML content, GitHub Pages support Jekyll, a simple, blog aware static site generator written by our own Tom Preston-Werner. Jekyll makes it easy to create site-wide headers and footers without having to copy them across every page. It also offers intelligent blog support and other advanced templating features.</p>
48+
<h3>Contribute</h3>
5349

54-
<h3>
55-
<a name="authors-and-contributors" class="anchor" href="#authors-and-contributors"><span class="octicon octicon-link"></span></a>Authors and Contributors</h3>
50+
<p>
51+
To contribute to this
52+
project, <a href="https://github.com/source-map/source-map.github.io">visit
53+
us GitHub</a>.
54+
</p>
5655

57-
<p>You can <a href="https://github.com/blog/821" class="user-mention">@mention</a> a GitHub username to generate a link to their profile. The resulting <code>&lt;a&gt;</code> element will link to the contributor's GitHub Profile. For example: In 2007, Chris Wanstrath (<a href="https://github.com/defunkt" class="user-mention">@defunkt</a>), PJ Hyett (<a href="https://github.com/pjhyett" class="user-mention">@pjhyett</a>), and Tom Preston-Werner (<a href="https://github.com/mojombo" class="user-mention">@mojombo</a>) founded GitHub.</p>
56+
<h3>FAQ</h3>
5857

59-
<h3>
60-
<a name="support-or-contact" class="anchor" href="#support-or-contact"><span class="octicon octicon-link"></span></a>Support or Contact</h3>
58+
<a href="faq.html">Frequently Asked Questions</a>
6159

62-
<p>Having trouble with Pages? Check out the documentation at <a href="http://help.github.com/pages">http://help.github.com/pages</a> or contact <a href="mailto:[email protected]">[email protected]</a> and we’ll help you sort it out.</p>
6360
</section>
6461

65-
<footer>
66-
This page was generated by <a href="http://pages.github.com">GitHub Pages</a>. Tactile theme by <a href="https://twitter.com/jasonlong">Jason Long</a>.
67-
</footer>
68-
69-
7062
</div>
7163
</div>
7264
</body>
73-
</html>
65+
</html>

0 commit comments

Comments
 (0)