steverusso
696731b1b5
Disable taxonomy types. Put the simple software data in the home page content file. Navbar can be cached. Make the CSS assets and bundle the global CSS. Can cache the scripts and the footer. Global CSS and JS partials. These don't make any sense. Fix baseof titling. Move navbar and footer out of directories where they are the only files, update base template. Reviewed-by: jeff <jeff@simplesystems.tech>
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
---
|
|
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."
|
|
}
|
|
]
|
|
---
|