Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions data/home.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ why_score:
sections:
- from:
title: Cognitive load
text: Developers are forced to become experts in a variety of tech and tools, just do deploy a simple change to their apps.
text: Developers are forced to become experts in a variety of tech and tools, just to deploy a simple change to their apps.
icon: svg/icon-cognitive.svg
to:
title: Features over Ops
Expand All @@ -22,7 +22,7 @@ why_score:
icon: svg/icon-config-drift.svg
to:
title: Local to prod
text: With Score you can easily transition from local to to remote environments. Configs stay consistent, everywhere you deploy.
text: With Score you can easily transition from local to remote environments. Configs stay consistent, everywhere you deploy.
icon: svg/icon-multiple_stop.svg
- from:
title: YAML bloat
Expand All @@ -36,7 +36,7 @@ easily_integrates:
title: Easily integrates in your existing workflows
sections:
- title: Extendable and customizable
text: The <span class="highlight-code">score.yaml</span> file can be extended and customised according to your needs. The score spec leaves room for environment specific overrides as well as platform specific extensions that allow to list additional properties or requirements.
text: The <span class="highlight-code">score.yaml</span> file can be extended and customised according to your needs. The score spec leaves room for environment specific overrides as well as platform specific extensions that allow you to list additional properties or requirements.
image: images/home/6374bfdcaeb3b3355842b6bc_score-overrides-16nov22-p-500.png
- title: Declarative by nature
text: Score lets developers define the resources required by their workloads in a declarative way. You declare once that your workload needs to listen on a port to receive requests - and don’t not need to worry where and how the exact port is defined in e.g. a remote Kubernetes environment. By declaring what the workload needs to run, the “how” becomes an environment specific implementation detail that is taken care of by Score.
Expand Down