Repository navigation
Expand file tree
/
Copy pathprojects.html
More file actions
73 lines (67 loc) · 2.67 KB
/
Copy pathprojects.html
File metadata and controls
73 lines (67 loc) · 2.67 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
---
title: Projects
description: "Selected projects by conaman across game-engine-adjacent tooling, utilities, and workflow automation."
nav_key: projects
permalink: /projects/
---
<section class="page-hero">
<p class="section-eyebrow">Projects</p>
<h1>Selected projects.</h1>
<p class="page-intro">Each project here was chosen because it represents a real technical problem worth explaining: engine and system constraints, awkward platform behavior, or workflows that benefit from clearer tooling.</p>
<div class="cta-row">
<a class="button button-primary" href="https://github.com/conaman">GitHub profile</a>
<a class="button button-secondary" href="{{ '/writing/' | relative_url }}">Related articles</a>
</div>
</section>
<section class="section">
<div class="project-grid">
{% for project in site.data.projects %}
<article class="project-card">
<div class="project-card__top">
<div>
<p class="card-eyebrow">{{ project.kind }}</p>
<h2>{{ project.title }}</h2>
</div>
<span class="status-badge">{{ project.status }}</span>
</div>
<p>{{ project.headline }}</p>
<p>{{ project.summary }}</p>
<ul class="info-list">
<li>
<strong>Problem</strong>
{{ project.challenge }}
</li>
<li>
<strong>Why it matters</strong>
{{ project.impact }}
</li>
</ul>
<ul class="tag-list">
{% for item in project.stack %}
<li>{{ item }}</li>
{% endfor %}
</ul>
<div class="card-links">
{% if project.detail_url %}
<a class="button button-primary" href="{{ project.detail_url | relative_url }}">Open case study</a>
{% endif %}
<a class="button button-secondary" href="{{ project.repository }}">View repository</a>
</div>
</article>
{% endfor %}
</div>
</section>
<section class="section">
<div class="panel-grid">
<article class="panel">
<p class="section-eyebrow">What gets featured</p>
<h2>Projects that expose decision-making</h2>
<p>I like projects that show their constraints clearly: why the approach was chosen, what environment it targets, and which compromises were worth making to keep the result useful.</p>
</article>
<article class="panel">
<p class="section-eyebrow">Next layer</p>
<h2>Repositories plus context</h2>
<p>The repository alone is rarely the whole story. When a project is interesting enough, I pair it with articles or a dedicated page so the architecture and trade-offs remain legible later.</p>
</article>
</div>
</section>