archive/theorangeone.net-legacy
Archived
1
Fork 0
Code Releases Packages Activity

add links to about page

Browse source
This commit is contained in:
Jake Howard 2016-08-07 22:21:08 +01:00
parent 85bc1ccf67
commit 0f5d377102
Signed by: jake
GPG key ID: 57AFB45680EDD477
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
content/pages/about.html
View file

@ -37,10 +37,10 @@
My website is the culmination of all my knowledge, compiled into 1 place. It not only contains all my projects, but it in itself is a project. Making sure this website works properly is a tall order, especially considering it's self hosted. My website is the culmination of all my knowledge, compiled into 1 place. It not only contains all my projects, but it in itself is a project. Making sure this website works properly is a tall order, especially considering it's self hosted.
</p> </p>
<p> <p>
The site is primarily powered by <a href="">Pelican</a>, a static site generator. This converts markdown and HTML templates into static HTML files. The templates are generated using <a href="">Jinja2</a>, a templating language similar to <a href="">Django</a>'s. This allows me to write nice clean, <i>DRY</i> content, and have it come out as clean HTML. The site is primarily powered by <a href="http://getpelican.com">Pelican</a>, a static site generator. This converts markdown and HTML templates into static HTML files. The templates are generated using <a href="http://jinja.pocoo.org/">Jinja2</a>, a templating language similar to <a href="https://www.djangoproject.com/">Django</a>'s. This allows me to write nice clean, <i>DRY</i> content, and have it come out as clean HTML.
</p> </p>
<p> <p>
The static content (JS, CSS etc) is built using a custom build pipeline. The Javascript is built and compiled using <a href="">Babel</a> and <a href="">Browserify</a>, and the CSS is written using <a href="">node-SCSS</a> as a pre-processor. The static content (JS, CSS etc) is built using a custom build pipeline. The Javascript is built and compiled using <a href="https://babeljs.io/">Babel</a> and <a href="http://browserify.org/">Browserify</a>, and the CSS is written using <a href="https://github.com/sass/node-sass">node-SCSS</a> as a pre-processor.
</p> </p>
</div> </div>
</section> </section>
@ -48,10 +48,10 @@
<div class="container"> <div class="container">
<h2>The Server</h2> <h2>The Server</h2>
<p> <p>
The website is hosted on my <a href="">UK VPS</a>. Previous versions have been hosted on <a href="">1&amp;1</a> and <a href="">MyWindowsHosting</a>. The website is hosted on my <a href="">UK VPS</a>. Previous versions have been hosted on <a href="https://www.1and1.com/">1&amp;1</a> and <a href="http://www.myWindowsHosting.com/index?r=100196823">MyWindowsHosting</a>.
</p> </p>
<p> <p>
The static files are served using a <a href="">custom Express server</a>, which allows me to auto-deploy the site from my <a href="">CI</a>. This is then served using a custom, closed-source reverse proxy, which makes local development and domain switching much easier. This is pointed to by <a href="">NGINX</a>, which actually serves port 80. The static files are served using a <a href="https://github.com/RealOrangeOne/host-container">custom Express server</a>, which allows me to auto-deploy the site from my <a href="https://circleci.com/">CI</a>. This is then served using a custom, closed-source reverse proxy, which makes local development and domain switching much easier. This is pointed to by <a href="https://www.nginx.com/">NGINX</a>, which actually serves port 80.
</p> </p>
</div> </div>
</section> </section>