You are viewing the source of felocity.com. This serves as a portfolio of sorts, as all the code is out in the open to see (except for config files). Browse around, feel free to ask questions. If you see something horrible, glaring, or otherwise a major security problem, please don't hesitate to contact me.
Pages/Code (xml)
<chip:include file="Pages/Macros/Global"/>
<chip:include file="Pages/Widgets/Github"/>
<tal:block tal:define="enable_primary 1; enable_secondary 1; enable_tertiary 1"/>
<html metal:use-macro="html">
<head>
<title metal:fill-slot="title">Felocity.com</title>
<tal:block metal:fill-slot="scripts"></tal:block>
<tal:block metal:fill-slot="css"></tal:block>
</head>
<!-- Primary Content -->
<tal:block metal:fill-slot="primary content">
<h1>Open Source</h1>
<div class="projects">
<div class="project">
<h2>SnapTest</h2>
<p>
Designed with the goal of lowering the barrier to entry for testing, SnapTest
is designed to minimize the amount of code you write before you start writing
your tests. In order to be easy to pick up, the code has to feel like xUnit,
but with an interface that takes advantage of the syntax PHP provides.
</p>
<!-- GitHub -->
<tal:block tal:define="local username string: jakobo; local project string: snaptest; local size 3; local snip 100">
<tal:block metal:use-macro="github widget">
<tal:block metal:fill-slot="project title"><h3>Latest Project Updates</h3></tal:block>
</tal:block>
</tal:block>
</div>
<div class="project">
<h2>Chippino MVC</h2>
<p>
Chippino is a play off of the popular seafood dish "Ciopinno", a soup that is
characterized by the catch of the day. The theory behind Chippino is that its
simple modularity allows it to be extended in such a way that you can write code
quickly, but not be constrained to a lot of the structure and rigor a framework
gives you. This is, of course, without its own drawbacks. It's minimalist feature
set gives URL routing and construction, a TAL based template language, and a
full separation of the business logic tier from the presentation layer.
</p>
<!-- GitHub -->
<tal:block tal:define="local username string: jakobo; local project string: chippino; local size 3; local snip 100">
<tal:block metal:use-macro="github widget">
<tal:block metal:fill-slot="project title"><h3>Latest Project Updates</h3></tal:block>
</tal:block>
</tal:block>
</div>
<div class="project">
<h2>SCAR</h2>
<p>
This is a re-implementation of the Active Record pattern. However, unlike many other
systems, this one intentionally steps around the concept of table joins. This makes
it easier to shard your databases while still maintaining the clean interface that
the AR pattern provides. Additionally, the repository and write through cache
modules are easily swappable, allowing you to quickly implement row-wise caching.
</p>
<!-- GitHub -->
<tal:block tal:define="local username string: jakobo; local project string: scar; local size 3; local snip 100">
<tal:block metal:use-macro="github widget">
<tal:block metal:fill-slot="project title"><h3>Latest Project Updates</h3></tal:block>
</tal:block>
</tal:block>
</div>
</div>
</tal:block>
<!-- Secondary Content -->
<tal:block metal:fill-slot="secondary content">
<h1>This</h1>
<p>
On some level, felocity.com serves as a portfolio piece all its own. You can browse most of
the site's source code and see how everything is constructed. You could start with
<a tal:attributes="href url:source path=Pages/Code">this page</a>, or simply click the "view
source" link in the footer on any page on the site. Here's a few additional interesting pages
to get started with:
</p>
<ul>
<li><a tal:attributes="href url:source path=Pages/FrontPage">Home Page</a></li>
<li><a tal:attributes="href url:source path=Pages/SourceBrowser">View Source</a></li>
<li><a tal:attributes="href url:source path=Pages/JS">JavaScript Files</a></li>
<li><a tal:attributes="href url:source path=Pages/Widgets/Flickr">Flickr Widget</a></li>
</ul>
</tal:block>
<!-- Tertiary Content -->
<tal:block metal:fill-slot="tertiary content">
<h1>Work</h1>
<h2>LinkedIn</h2>
<p>
I'm currently working at LinkedIn as a Senior Web Developer. My work there consists of
building things using rich front-end technologies, specifically around the addition
of JavaScript to the site and striving to keep us true to the ideas of progressive
enhancement and beautiful markup.
(<a href="http://www.linkedin.com">linkedin.com</a>)
</p>
<h2>And?</h2>
<p>
The best place to get my whole work history is at my
<a href="http://www.linkedin.com/in/jakobheuser" rel="me">LinkedIn Profile</a>.
</p>
</tal:block>
</html>