docs: fix styling and content
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
- Black background instead of blue - Remove 'dev' from build commands - Shorter problem descriptions - Fix missing infrastructure description (DBs, APIs, K8s)
This commit is contained in:
buenosairesam
@@ -9,7 +9,9 @@
|
||||
<body>
|
||||
<header>
|
||||
<h1>Soleprint</h1>
|
||||
<p class="subtitle">Cada paso deja huella / Each step leaves a mark</p>
|
||||
<p class="subtitle">
|
||||
Cada paso deja huella / Each step leaves a mark
|
||||
</p>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
@@ -19,15 +21,25 @@
|
||||
<div class="findings-grid">
|
||||
<article class="finding-card">
|
||||
<h3>Freelance Work Standardization</h3>
|
||||
<p>Generalizing and homogenizing freelance work across projects. Instead of setting up different environments, testing approaches, and connector patterns for each client, Soleprint provides a consistent framework. Build once, reuse everywhere.</p>
|
||||
<p>
|
||||
Consistent framework across projects. Build once,
|
||||
reuse everywhere.
|
||||
</p>
|
||||
</article>
|
||||
<article class="finding-card">
|
||||
<h3>Missing Infrastructure Replication</h3>
|
||||
<p>When working with large corps where you can't access their Jira, Slack, payment systems, or internal APIs directly - Soleprint's shunts let you mock those systems locally. Test against fake MercadoPago, fake Jira tickets, fake webhooks without needing real credentials.</p>
|
||||
<h3>Missing Infrastructure</h3>
|
||||
<p>
|
||||
Mock systems you can't access yet - DB designs in
|
||||
progress, Kubernetes not ready, APIs being built.
|
||||
Test locally with shunts.
|
||||
</p>
|
||||
</article>
|
||||
<article class="finding-card">
|
||||
<h3>Reliable Testing Environment</h3>
|
||||
<p>Figure out what tests to write by actually running flows in a controlled environment. BDD -> Gherkin -> Tests workflow. Instead of guessing what to test, you explore the actual behavior first, document it, then generate tests from that documentation.</p>
|
||||
<h3>Reliable Testing</h3>
|
||||
<p>
|
||||
BDD -> Gherkin -> Tests. Explore behavior first,
|
||||
then generate tests.
|
||||
</p>
|
||||
</article>
|
||||
</div>
|
||||
</section>
|
||||
@@ -36,7 +48,9 @@
|
||||
<section class="graph-section" id="overview">
|
||||
<div class="graph-header-row">
|
||||
<h2>System Overview</h2>
|
||||
<a href="graph.html?g=01-system-overview" class="view-btn">View Full</a>
|
||||
<a href="graph.html?g=01-system-overview" class="view-btn"
|
||||
>View Full</a
|
||||
>
|
||||
</div>
|
||||
<a href="graph.html?g=01-system-overview" class="graph-preview">
|
||||
<img src="01-system-overview.svg" alt="System Overview" />
|
||||
@@ -45,10 +59,22 @@
|
||||
<p>The four systems that make up Soleprint.</p>
|
||||
<h4>Systems</h4>
|
||||
<ul>
|
||||
<li><strong>Soleprint</strong>: Core coordinator hub (port 12000)</li>
|
||||
<li><strong>Artery</strong>: Connectors to external services - "Todo lo vital"</li>
|
||||
<li><strong>Atlas</strong>: Actionable documentation - "Documentacion accionable"</li>
|
||||
<li><strong>Station</strong>: Tools and monitors - "Centro de control"</li>
|
||||
<li>
|
||||
<strong>Soleprint</strong>: Core coordinator hub
|
||||
(port 12000)
|
||||
</li>
|
||||
<li>
|
||||
<strong>Artery</strong>: Connectors to external
|
||||
services - "Todo lo vital"
|
||||
</li>
|
||||
<li>
|
||||
<strong>Atlas</strong>: Actionable documentation -
|
||||
"Documentacion accionable"
|
||||
</li>
|
||||
<li>
|
||||
<strong>Station</strong>: Tools and monitors -
|
||||
"Centro de control"
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</section>
|
||||
@@ -57,9 +83,14 @@
|
||||
<section class="graph-section" id="artery">
|
||||
<div class="graph-header-row">
|
||||
<h2>Artery Hierarchy</h2>
|
||||
<a href="graph.html?g=02-artery-hierarchy" class="view-btn">View Full</a>
|
||||
<a href="graph.html?g=02-artery-hierarchy" class="view-btn"
|
||||
>View Full</a
|
||||
>
|
||||
</div>
|
||||
<a href="graph.html?g=02-artery-hierarchy" class="graph-preview">
|
||||
<a
|
||||
href="graph.html?g=02-artery-hierarchy"
|
||||
class="graph-preview"
|
||||
>
|
||||
<img src="02-artery-hierarchy.svg" alt="Artery Hierarchy" />
|
||||
</a>
|
||||
<div class="graph-details">
|
||||
@@ -103,7 +134,9 @@
|
||||
<section class="graph-section" id="build">
|
||||
<div class="graph-header-row">
|
||||
<h2>Build Flow</h2>
|
||||
<a href="graph.html?g=03-build-flow" class="view-btn">View Full</a>
|
||||
<a href="graph.html?g=03-build-flow" class="view-btn"
|
||||
>View Full</a
|
||||
>
|
||||
</div>
|
||||
<a href="graph.html?g=03-build-flow" class="graph-preview">
|
||||
<img src="03-build-flow.svg" alt="Build Flow" />
|
||||
@@ -120,15 +153,17 @@
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>python build.py dev</code></td>
|
||||
<td><code>python build.py</code></td>
|
||||
<td>gen/standalone/</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>python build.py dev --cfg amar</code></td>
|
||||
<td>
|
||||
<code>python build.py --cfg amar</code>
|
||||
</td>
|
||||
<td>gen/amar/</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>python build.py dev --all</code></td>
|
||||
<td><code>python build.py --all</code></td>
|
||||
<td>both</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@@ -140,7 +175,9 @@
|
||||
<section class="graph-section" id="room">
|
||||
<div class="graph-header-row">
|
||||
<h2>Room Configuration</h2>
|
||||
<a href="graph.html?g=04-room-config" class="view-btn">View Full</a>
|
||||
<a href="graph.html?g=04-room-config" class="view-btn"
|
||||
>View Full</a
|
||||
>
|
||||
</div>
|
||||
<a href="graph.html?g=04-room-config" class="graph-preview">
|
||||
<img src="04-room-config.svg" alt="Room Configuration" />
|
||||
@@ -149,10 +186,24 @@
|
||||
<p>How rooms are configured in cfg/.</p>
|
||||
<h4>Room Structure</h4>
|
||||
<ul>
|
||||
<li><strong>config.json</strong>: Framework branding, terminology</li>
|
||||
<li><strong>data/</strong>: veins.json, shunts.json, depots.json</li>
|
||||
<li><strong>soleprint/</strong>: Docker config for this room</li>
|
||||
<li><strong>databrowse/, tester/, monitors/, models/</strong>: Room-specific extensions</li>
|
||||
<li>
|
||||
<strong>config.json</strong>: Framework branding,
|
||||
terminology
|
||||
</li>
|
||||
<li>
|
||||
<strong>data/</strong>: veins.json, shunts.json,
|
||||
depots.json
|
||||
</li>
|
||||
<li>
|
||||
<strong>soleprint/</strong>: Docker config for this
|
||||
room
|
||||
</li>
|
||||
<li>
|
||||
<strong
|
||||
>databrowse/, tester/, monitors/,
|
||||
models/</strong
|
||||
>: Room-specific extensions
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</section>
|
||||
@@ -200,7 +251,9 @@
|
||||
|
||||
<footer>
|
||||
<p>Soleprint - Development Workflow Platform</p>
|
||||
<p class="date">Generated: <time datetime="2025-01">January 2025</time></p>
|
||||
<p class="date">
|
||||
Generated: <time datetime="2025-01">January 2025</time>
|
||||
</p>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
Reference in New Issue
Block a user