Skip to content

Commit 3a3349b

Browse files
stedmanstedman
committed
deploy: ec746d0 
1 parent 5b6a0f3 commit 3a3349b

File tree

215 files changed

+528
-26380
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

215 files changed

+528
-26380
lines changed

‎2011-austin-javascript-sxsw-party-poster/index.html‎

Lines changed: 1 addition & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1 @@
1-
{#
2-
This is the closest we can get to 301 redirects in GitHub Pages.
3-
4-
This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds
5-
(change that delay if you wish the page to appear for longer, though if you do, note that the
6-
template is basic and un-styled). The template also sets the canonical link to the
7-
new page location and a link in the body, in case the browser doesn't do meta refresh.
8-
9-
This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/)
10-
from `_data/redirects.json`. Note that there is additional old/new file mapping in
11-
that file that may be removed if it's not needed.
12-
13-
The obvious downside to this approach is that files are created in the root or posts
14-
directory for each of the old permalinks. At worst, this may result in namespace collisions
15-
should a future filename/permalink match one of the redirect permalinks. Otherwise,
16-
this approach merely clutters up the output directory with "old" files.
17-
18-
We may want to sunset this approach as traffic to the old pages drops off to a certain level.
19-
#}
20-
<!DOCTYPE html>
21-
<html lang="en">
22-
<head>
23-
<meta charset="utf-8">
24-
<meta http-equiv="refresh" content="0;url=/posts/2011-austin-javascript-sxsw-party-poster/" />
25-
<link rel="canonical" href="/posts/2011-austin-javascript-sxsw-party-poster/" />
26-
</head>
27-
<body>
28-
<h1>Redirecting</h1>
29-
<p>This page been moved to <a href="/posts/2011-austin-javascript-sxsw-party-poster/">/posts/2011-austin-javascript-sxsw-party-poster/</a>.</p>
30-
</body>
31-
</html>
1+
{# This is the closest we can get to 301 redirects in GitHub Pages. This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds (change that delay if you wish the page to appear for longer, though if you do, note that the template is basic and un-styled). The template also sets the canonical link to the new page location and a link in the body, in case the browser doesn't do meta refresh. This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/) from `_data/redirects.json`. Note that there is additional old/new file mapping in that file that may be removed if it's not needed. The obvious downside to this approach is that files are created in the root or posts directory for each of the old permalinks. At worst, this may result in namespace collisions should a future filename/permalink match one of the redirect permalinks. Otherwise, this approach merely clutters up the output directory with "old" files. We may want to sunset this approach as traffic to the old pages drops off to a certain level. #}<!doctype html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="refresh" content="0;url=/posts/2011-austin-javascript-sxsw-party-poster/"><link rel="canonical" href="/posts/2011-austin-javascript-sxsw-party-poster/"></head><body><h1>Redirecting</h1><p>This page been moved to <a href="/posts/2011-austin-javascript-sxsw-party-poster/">/posts/2011-austin-javascript-sxsw-party-poster/</a>.</p></body></html>

‎2011-austin-javascript-sxsw-party-wrapup/index.html‎

Lines changed: 1 addition & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1 @@
1-
{#
2-
This is the closest we can get to 301 redirects in GitHub Pages.
3-
4-
This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds
5-
(change that delay if you wish the page to appear for longer, though if you do, note that the
6-
template is basic and un-styled). The template also sets the canonical link to the
7-
new page location and a link in the body, in case the browser doesn't do meta refresh.
8-
9-
This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/)
10-
from `_data/redirects.json`. Note that there is additional old/new file mapping in
11-
that file that may be removed if it's not needed.
12-
13-
The obvious downside to this approach is that files are created in the root or posts
14-
directory for each of the old permalinks. At worst, this may result in namespace collisions
15-
should a future filename/permalink match one of the redirect permalinks. Otherwise,
16-
this approach merely clutters up the output directory with "old" files.
17-
18-
We may want to sunset this approach as traffic to the old pages drops off to a certain level.
19-
#}
20-
<!DOCTYPE html>
21-
<html lang="en">
22-
<head>
23-
<meta charset="utf-8">
24-
<meta http-equiv="refresh" content="0;url=/posts/2011-austin-javascript-sxsw-party-wrapup/" />
25-
<link rel="canonical" href="/posts/2011-austin-javascript-sxsw-party-wrapup/" />
26-
</head>
27-
<body>
28-
<h1>Redirecting</h1>
29-
<p>This page been moved to <a href="/posts/2011-austin-javascript-sxsw-party-wrapup/">/posts/2011-austin-javascript-sxsw-party-wrapup/</a>.</p>
30-
</body>
31-
</html>
1+
{# This is the closest we can get to 301 redirects in GitHub Pages. This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds (change that delay if you wish the page to appear for longer, though if you do, note that the template is basic and un-styled). The template also sets the canonical link to the new page location and a link in the body, in case the browser doesn't do meta refresh. This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/) from `_data/redirects.json`. Note that there is additional old/new file mapping in that file that may be removed if it's not needed. The obvious downside to this approach is that files are created in the root or posts directory for each of the old permalinks. At worst, this may result in namespace collisions should a future filename/permalink match one of the redirect permalinks. Otherwise, this approach merely clutters up the output directory with "old" files. We may want to sunset this approach as traffic to the old pages drops off to a certain level. #}<!doctype html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="refresh" content="0;url=/posts/2011-austin-javascript-sxsw-party-wrapup/"><link rel="canonical" href="/posts/2011-austin-javascript-sxsw-party-wrapup/"></head><body><h1>Redirecting</h1><p>This page been moved to <a href="/posts/2011-austin-javascript-sxsw-party-wrapup/">/posts/2011-austin-javascript-sxsw-party-wrapup/</a>.</p></body></html>

‎2012-austinjs-sxsw-3-year-anniversary-party/index.html‎

Lines changed: 1 addition & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1 @@
1-
{#
2-
This is the closest we can get to 301 redirects in GitHub Pages.
3-
4-
This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds
5-
(change that delay if you wish the page to appear for longer, though if you do, note that the
6-
template is basic and un-styled). The template also sets the canonical link to the
7-
new page location and a link in the body, in case the browser doesn't do meta refresh.
8-
9-
This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/)
10-
from `_data/redirects.json`. Note that there is additional old/new file mapping in
11-
that file that may be removed if it's not needed.
12-
13-
The obvious downside to this approach is that files are created in the root or posts
14-
directory for each of the old permalinks. At worst, this may result in namespace collisions
15-
should a future filename/permalink match one of the redirect permalinks. Otherwise,
16-
this approach merely clutters up the output directory with "old" files.
17-
18-
We may want to sunset this approach as traffic to the old pages drops off to a certain level.
19-
#}
20-
<!DOCTYPE html>
21-
<html lang="en">
22-
<head>
23-
<meta charset="utf-8">
24-
<meta http-equiv="refresh" content="0;url=/posts/2012-austinjs-sxsw-3-year-anniversary-party/" />
25-
<link rel="canonical" href="/posts/2012-austinjs-sxsw-3-year-anniversary-party/" />
26-
</head>
27-
<body>
28-
<h1>Redirecting</h1>
29-
<p>This page been moved to <a href="/posts/2012-austinjs-sxsw-3-year-anniversary-party/">/posts/2012-austinjs-sxsw-3-year-anniversary-party/</a>.</p>
30-
</body>
31-
</html>
1+
{# This is the closest we can get to 301 redirects in GitHub Pages. This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds (change that delay if you wish the page to appear for longer, though if you do, note that the template is basic and un-styled). The template also sets the canonical link to the new page location and a link in the body, in case the browser doesn't do meta refresh. This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/) from `_data/redirects.json`. Note that there is additional old/new file mapping in that file that may be removed if it's not needed. The obvious downside to this approach is that files are created in the root or posts directory for each of the old permalinks. At worst, this may result in namespace collisions should a future filename/permalink match one of the redirect permalinks. Otherwise, this approach merely clutters up the output directory with "old" files. We may want to sunset this approach as traffic to the old pages drops off to a certain level. #}<!doctype html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="refresh" content="0;url=/posts/2012-austinjs-sxsw-3-year-anniversary-party/"><link rel="canonical" href="/posts/2012-austinjs-sxsw-3-year-anniversary-party/"></head><body><h1>Redirecting</h1><p>This page been moved to <a href="/posts/2012-austinjs-sxsw-3-year-anniversary-party/">/posts/2012-austinjs-sxsw-3-year-anniversary-party/</a>.</p></body></html>

‎2012-austinjs-sxsw-party-wrapup/index.html‎

Lines changed: 1 addition & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1 @@
1-
{#
2-
This is the closest we can get to 301 redirects in GitHub Pages.
3-
4-
This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds
5-
(change that delay if you wish the page to appear for longer, though if you do, note that the
6-
template is basic and un-styled). The template also sets the canonical link to the
7-
new page location and a link in the body, in case the browser doesn't do meta refresh.
8-
9-
This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/)
10-
from `_data/redirects.json`. Note that there is additional old/new file mapping in
11-
that file that may be removed if it's not needed.
12-
13-
The obvious downside to this approach is that files are created in the root or posts
14-
directory for each of the old permalinks. At worst, this may result in namespace collisions
15-
should a future filename/permalink match one of the redirect permalinks. Otherwise,
16-
this approach merely clutters up the output directory with "old" files.
17-
18-
We may want to sunset this approach as traffic to the old pages drops off to a certain level.
19-
#}
20-
<!DOCTYPE html>
21-
<html lang="en">
22-
<head>
23-
<meta charset="utf-8">
24-
<meta http-equiv="refresh" content="0;url=/posts/2012-austinjs-sxsw-party-wrapup/" />
25-
<link rel="canonical" href="/posts/2012-austinjs-sxsw-party-wrapup/" />
26-
</head>
27-
<body>
28-
<h1>Redirecting</h1>
29-
<p>This page been moved to <a href="/posts/2012-austinjs-sxsw-party-wrapup/">/posts/2012-austinjs-sxsw-party-wrapup/</a>.</p>
30-
</body>
31-
</html>
1+
{# This is the closest we can get to 301 redirects in GitHub Pages. This template uses meta refresh to redirect from the old path to the new permalink in 0 seconds (change that delay if you wish the page to appear for longer, though if you do, note that the template is basic and un-styled). The template also sets the canonical link to the new page location and a link in the body, in case the browser doesn't do meta refresh. This template uses 11ty Pagination to create pages with data (https://www.11ty.dev/docs/pages-from-data/) from `_data/redirects.json`. Note that there is additional old/new file mapping in that file that may be removed if it's not needed. The obvious downside to this approach is that files are created in the root or posts directory for each of the old permalinks. At worst, this may result in namespace collisions should a future filename/permalink match one of the redirect permalinks. Otherwise, this approach merely clutters up the output directory with "old" files. We may want to sunset this approach as traffic to the old pages drops off to a certain level. #}<!doctype html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="refresh" content="0;url=/posts/2012-austinjs-sxsw-party-wrapup/"><link rel="canonical" href="/posts/2012-austinjs-sxsw-party-wrapup/"></head><body><h1>Redirecting</h1><p>This page been moved to <a href="/posts/2012-austinjs-sxsw-party-wrapup/">/posts/2012-austinjs-sxsw-party-wrapup/</a>.</p></body></html>

0 commit comments

Comments
 (0)