Update image, fix image name spelling, fix some formatting

This commit is contained in:
Jack Bond-Preston 2019-02-14 21:26:08 +00:00
parent 2c700d78ed
commit b8d4b14bca
3 changed files with 16 additions and 14 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 56 KiB

BIN
images/potato-library.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

View File

@ -6,14 +6,15 @@
<meta charset="UTF-8"> <meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="css/uikit.min.css" /> <link rel="stylesheet" href="css/uikit.min.css" />
<link rel="icon" type="image/png" href="images/favicon-16x16.png" sizes="16x16"> <link rel="icon" type="image/png" href="images/favicon-16x16.png" sizes="16x16">
<link rel="icon" type="image/png" href="images/favicon-32x32.png" sizes="32x32"> <link rel="icon" type="image/png" href="images/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="images/favicon-96x96.png" sizes="96x96"> <link rel="icon" type="image/png" href="images/favicon-96x96.png" sizes="96x96">
</head> </head>
<body> <body>
<script src="js/uikit.min.js"></script> <script src="js/uikit.min.js"></script>
<script src="js/uikit-icons.min.js"></script> <script src="js/uikit-icons.min.js"></script>
<div style="height: 100%"> <div style="height: 100%">
<div class="uk-section uk-section-secondary"> <div class="uk-section uk-section-secondary">
<div class="uk-container"> <div class="uk-container">
@ -26,7 +27,7 @@
</div> </div>
</div> </div>
</div> </div>
<div class="uk-section uk-section-default"> <div class="uk-section uk-section-default">
<div class="uk-container uk-container-large"> <div class="uk-container uk-container-large">
<div class="uk-grid-match uk-child-width-expand@m" uk-grid> <div class="uk-grid-match uk-child-width-expand@m" uk-grid>
@ -44,9 +45,9 @@
</div> </div>
<div> <div>
<div class="uk-tile uk-tile-muted"> <div class="uk-tile uk-tile-muted">
<p class="uk-h4"> <p class="uk-h4">
<a href="https://www.linkedin.com/in/jack-bond-preston-922706150/">LinkedIn</a> <a href="https://www.linkedin.com/in/jack-bond-preston-922706150/">LinkedIn</a>
</p> </p>
</div> </div>
</div> </div>
</div> </div>
@ -93,7 +94,7 @@
<div> <div>
<div class="uk-inline"> <div class="uk-inline">
<a href="https://gitlab.com/spe-potato/potato-library"> <a href="https://gitlab.com/spe-potato/potato-library">
<img src="images/potato-libary.png" alt="Potato Library Screenshot"> <img src="images/potato-library.png" alt="Potato Library Screenshot">
</a> </a>
<div class="uk-overlay uk-overlay-primary uk-position-bottom"> <div class="uk-overlay uk-overlay-primary uk-position-bottom">
<h3 class="uk-heading"> <h3 class="uk-heading">
@ -102,7 +103,7 @@
</a> </a>
</h3> </h3>
<p> <p>
A bespoke book management system for A bespoke book management system for
<a href="https://p.ota.to/">Potato</a>. <a href="https://p.ota.to/">Potato</a>.
</p> </p>
<p class="uk-visible@m"> <p class="uk-visible@m">
@ -133,10 +134,11 @@
This game of life implementation was written in This game of life implementation was written in
<a href="https://en.wikipedia.org/wiki/XC_(programming_language)">XC</a> <a href="https://en.wikipedia.org/wiki/XC_(programming_language)">XC</a>
and designed to run on the XMOS xCORE-200 eXplorer. The program runs concurrently across tiles, utilising and designed to run on the XMOS xCORE-200 eXplorer. The program runs concurrently across tiles, utilising
channels for cross-thread communication. Hardware memory limitations posed interesting challenges, with solutions channels for cross-thread communication. Hardware memory limitations posed interesting challenges, with
such as packing the individual "cells" into individual bits of 32/16-bit integers to be as memory-efficient as solutions such as packing the individual "cells" into individual bits of 32/16-bit integers to be as
possible. Each turn, the board is split up into rows of these packed cells which are then distributed across memory-efficient as possible. Each turn, the board is split up into rows of these packed cells which are then
workers for processing, then returned to the distributor and consolidated back into a single board each turn. distributed across workers for processing, then returned to the distributor and consolidated back into a single
board each turn.
</p> </p>
</div> </div>
</div> </div>