simplesystems/website
simplesystems/website
1
0
Fork 0
Code Issues 18 Pull Requests Actions Wiki Activity

Refactors and project cleanup #18

Merged
jeff merged 9 commits from refactors into master 2020-06-12 00:42:12 +00:00
Conversation 0 Commits 9 Files Changed 15 +24 -24
4 changed files with 24 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit bff5d731f3 - Show all commits

22
content/_index.md
View File

@ -1,3 +1,25 @@
---
title:
ssattrs: [
{
"title": "Comprehensible Interaction",
"img": "/img/interact.png",
"desc": "The interface to software should be clear, without surprises. Engineers working on the project should not be deciphering code. Documentation is implied as part of the system, enabling all users to understand the software package better."
},
{
"title": "Straightforward Modification",
"img": "/img/tools.png",
"desc": "Software should handle changes smoothly. Great software feels like it was designed for future changes. The documentation will instruct an engineer's strategy, removing ambiguity of how something works."
},
{
"title": "Robust",
"img": "/img/robust.png",
"desc": "Load spikes, accidental misuse, and business growth should not bring software crashing to the ground. Systems should be designed to handle faults gracefully. If there are errors, they should be reported clearly."
},
{
"title": "Leveraged by Other Systems",
"img": "/img/leverage.png",
"desc": "When software simply does its job, and does it well, it will be an asset to other systems. When software becomes convoluted, it will hinder other systems."
}
]
---

22
data/home/ssattrs.json
View File

@ -1,22 +0,0 @@
[
{
"title": "Comprehensible Interaction",
"img": "/img/interact.png",
"desc": "The interface to software should be clear, without surprises. Engineers working on the project should not be deciphering code. Documentation is implied as part of the system, enabling all users to understand the software package better."
},
{
"title": "Straightforward Modification",
"img": "/img/tools.png",
"desc": "Software should handle changes smoothly. Great software feels like it was designed for future changes. The documentation will instruct an engineer's strategy, removing ambiguity of how something works."
},
{
"title": "Robust",
"img": "/img/robust.png",
"desc": "Load spikes, accidental misuse, and business growth should not bring software crashing to the ground. Systems should be designed to handle faults gracefully. If there are errors, they should be reported clearly."
},
{
"title": "Leveraged by Other Systems",
"img": "/img/leverage.png",
"desc": "When software simply does its job, and does it well, it will be an asset to other systems. When software becomes convoluted, it will hinder other systems."
}
]

2
layouts/index.html
View File

@ -1,4 +1,4 @@
{{ define "main" }}
{{ partial "jumbotron.html" . }}
{{ partial "simple-software.html" . }}
{{ partial "simple-software.html" .Params.ssattrs }}
{{ end }}

2
layouts/partials/simple-software.html
View File

@ -7,7 +7,7 @@
</div>
<div class="row justify-center">
{{ range $.Site.Data.home.ssattrs }}
{{ range $ }}
<div class="col xs-12 sm-10 md-6">
{{ partial "cards/home-card.html" . }}
</div>