<feed xmlns='http://www.w3.org/2005/Atom'>
<title>spragg-ssl.co.uk/html/@include.php, branch master</title>
<subtitle>The spragg-ssl.co.uk website</subtitle>
<link rel='alternate' type='text/html' href='https://spragg-ssl.co.uk/projects/cgit.cgi/spragg-ssl.co.uk/'/>
<entry>
<title>Change the "private file" prefix from "@" to "_"</title>
<updated>2018-07-26T14:09:50+00:00</updated>
<author>
<name>Adam Spragg</name>
<email>adam@spra.gg</email>
</author>
<published>2018-07-26T14:09:50+00:00</published>
<link rel='alternate' type='text/html' href='https://spragg-ssl.co.uk/projects/cgit.cgi/spragg-ssl.co.uk/commit/?id=f80f775dfbe12cf6b95bda38b73f5dc37327d7fa'/>
<id>f80f775dfbe12cf6b95bda38b73f5dc37327d7fa</id>
<content type='text'>
It has all the benefits previously mentioned in commit 2f547251, as well
as mirroring the common programming convention of using a "_" prefix to
identify private variables/functions

Hides files beginning with _ from mod_autoindex listings

As well as 404ing on files starting with "_", also 404 on files starting
with ".", as these are also private. Except for /.well-known/, because
that's... well known, and should be public.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It has all the benefits previously mentioned in commit 2f547251, as well
as mirroring the common programming convention of using a "_" prefix to
identify private variables/functions

Hides files beginning with _ from mod_autoindex listings

As well as 404ing on files starting with "_", also 404 on files starting
with ".", as these are also private. Except for /.well-known/, because
that's... well known, and should be public.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add new "amber" stylesheet and make it default</title>
<updated>2018-06-27T15:41:11+00:00</updated>
<author>
<name>Adam Spragg</name>
<email>adam@spra.gg</email>
</author>
<published>2018-06-27T15:41:11+00:00</published>
<link rel='alternate' type='text/html' href='https://spragg-ssl.co.uk/projects/cgit.cgi/spragg-ssl.co.uk/commit/?id=f35b4d49358cb72ad27aeb64ffcc2cdf4cea6d32'/>
<id>f35b4d49358cb72ad27aeb64ffcc2cdf4cea6d32</id>
<content type='text'>
Because apparently green doesn't show up super-bright with traditional
CMYK printing, so my business card with the green-on-black header
wouldn't have looked great - unless I was willing to pay a lot of money
for special printing.

However, apparently yellow does show up well (probably because it's the
Y in CMYK), and because old-old-school CRTs came in amber-on-black as
well as green-on-black, switching to amber-on-black lets me keep the
same kind of aesthetic while being more print-friendly.

Also, it looks less Matrix-y. On the one hand, that's better because it
looks less derivative. On the other, it's worse, because it doesn't grab
you quite as instinctively as it did before.

I've done it with alternate stylesheets though, so you can still pick
the green colorscheme if you want.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Because apparently green doesn't show up super-bright with traditional
CMYK printing, so my business card with the green-on-black header
wouldn't have looked great - unless I was willing to pay a lot of money
for special printing.

However, apparently yellow does show up well (probably because it's the
Y in CMYK), and because old-old-school CRTs came in amber-on-black as
well as green-on-black, switching to amber-on-black lets me keep the
same kind of aesthetic while being more print-friendly.

Also, it looks less Matrix-y. On the one hand, that's better because it
looks less derivative. On the other, it's worse, because it doesn't grab
you quite as instinctively as it did before.

I've done it with alternate stylesheets though, so you can still pick
the green colorscheme if you want.
</pre>
</div>
</content>
</entry>
<entry>
<title>Simplify hiding navigation items slightly</title>
<updated>2018-06-25T14:24:19+00:00</updated>
<author>
<name>Adam Spragg</name>
<email>adam@spra.gg</email>
</author>
<published>2018-06-25T14:24:19+00:00</published>
<link rel='alternate' type='text/html' href='https://spragg-ssl.co.uk/projects/cgit.cgi/spragg-ssl.co.uk/commit/?id=8637cf6add0b5be32dd58992e94d23ff1e80966c'/>
<id>8637cf6add0b5be32dd58992e94d23ff1e80966c</id>
<content type='text'>
The code is now a bit longer, but it's also a bit clearer. The resulting
HTML is also clearer.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The code is now a bit longer, but it's also a bit clearer. The resulting
HTML is also clearer.
</pre>
</div>
</content>
</entry>
<entry>
<title>Output the page head/header/footer with PHP</title>
<updated>2018-06-19T15:35:15+00:00</updated>
<author>
<name>Adam Spragg</name>
<email>adam@spra.gg</email>
</author>
<published>2018-06-19T15:35:15+00:00</published>
<link rel='alternate' type='text/html' href='https://spragg-ssl.co.uk/projects/cgit.cgi/spragg-ssl.co.uk/commit/?id=2f5472519016b3092dea07d6f041b1cb74c3cd13'/>
<id>2f5472519016b3092dea07d6f041b1cb74c3cd13</id>
<content type='text'>
Allows putting all the repeated stuff in one place (DRY!), so that if it
needs changing it only needs to change once.

Start the name of the included file with "@", and disallow the retrieval
of files beginning with "@" (returning 404) so that it can't be
downloaded, because it won't output anything meaningful.

Why "@"? Because it's about the only ASCII punctuation character that
doesn't mean anything special to most shells (bash), or programs, and is
therefore easy to use as a filename on the command line. I almost went
with "+", but it turns out that nvim treats arguments beginning with "+"
as options. So "@" it is.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Allows putting all the repeated stuff in one place (DRY!), so that if it
needs changing it only needs to change once.

Start the name of the included file with "@", and disallow the retrieval
of files beginning with "@" (returning 404) so that it can't be
downloaded, because it won't output anything meaningful.

Why "@"? Because it's about the only ASCII punctuation character that
doesn't mean anything special to most shells (bash), or programs, and is
therefore easy to use as a filename on the command line. I almost went
with "+", but it turns out that nvim treats arguments beginning with "+"
as options. So "@" it is.
</pre>
</div>
</content>
</entry>
</feed>
