Commit d7696683 authored by Mark Lodato's avatar Mark Lodato
Browse files

Clean up after PR #121.



Bugfixes:

- Fix the "SLSA" link in the upper left corner, which was broken.
- Add blank lines around `span` tags to fix Markdown syntax. (This isn't
  valid HTML, but I'll address that in another PR.)

Cleanups:

- Remove .DS_Store.
- Make links relative so that they work on GitHub.
- Re-indent to minimize differences from upstream theme (minima).

Signed-off-by: default avatarMark Lodato <lodato@google.com>
parent eb3be024
......@@ -32,4 +32,3 @@ plugins:
- jekyll-readme-index
- jekyll-titles-from-headings
- jekyll-relative-links
<footer class="site-footer">
<data class="u-url"
href="{{ "
/"
|
relative_url
}}"></data>
<div class="wrapper">
<div>
<p>SLSA (pronounced "<a href="https://www.google.com/search?q=how+to+pronounce+salsa">salsa</a>") is <strong>Supply-chain Levels
for Software Artifacts</strong>.</p>
</div>
<div>
{{- site.copyright_html -}}
</div>
<div>
{%- include social.html -%}
</div>
<div>
<a href="{{ site.github.repository_url }}">View SLSA on GitHub </a>
</div>
<footer class="site-footer h-card">
<data class="u-url" href="{{ "/" | relative_url }}"></data>
<div class="wrapper">
<div>
<p>SLSA (pronounced "<a href="https://www.google.com/search?q=how+to+pronounce+salsa">salsa</a>") is <strong>Supply-chain Levels
for Software Artifacts</strong>.</p>
</div>
</footer>
\ No newline at end of file
<div>
{{- site.copyright_html -}}
</div>
<div>
{%- include social.html -%}
</div>
<div>
<a href="{{ site.github.repository_url }}">View SLSA on GitHub </a>
</div>
</div>
</footer>
<header class="site-header wrapper"
role="banner">
<header class="site-header wrapper" role="banner">
<div>
{%- assign default_paths = site.pages | map: "path" -%}
{%- assign page_paths = site.header_pages | default: default_paths -%}
<a class="site-title"
rel="author"
href="{{ "
/"
|
relative_url
}}">{{ site.title | escape }}</a>
<div>
{%- assign default_paths = site.pages | map: "path" -%}
{%- assign page_paths = site.header_pages | default: default_paths -%}
<a class="site-title" rel="author" href="{{ "/" | relative_url }}">{{ site.title | escape }}</a>
{%- if page_paths -%}
<nav class="site-nav">
<input type="checkbox"
id="nav-trigger"
class="nav-trigger" />
<label for="nav-trigger">
<span class="menu-icon">
<svg viewBox="0 0 18 15"
width="18px"
height="15px">
<path
d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.032C17.335,0,18,0.665,18,1.484L18,1.484z M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.032C17.335,6.031,18,6.696,18,7.516L18,7.516z M18,13.516C18,14.335,17.335,15,16.516,15H1.484 C0.665,15,0,14.335,0,13.516l0,0c0-0.82,0.665-1.483,1.484-1.483h15.032C17.335,12.031,18,12.695,18,13.516L18,13.516z" />
</svg>
</span>
</label>
{%- if page_paths -%}
<nav class="site-nav">
<input type="checkbox" id="nav-trigger" class="nav-trigger" />
<label for="nav-trigger">
<span class="menu-icon">
<svg viewBox="0 0 18 15" width="18px" height="15px">
<path d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.032C17.335,0,18,0.665,18,1.484L18,1.484z M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.032C17.335,6.031,18,6.696,18,7.516L18,7.516z M18,13.516C18,14.335,17.335,15,16.516,15H1.484 C0.665,15,0,14.335,0,13.516l0,0c0-0.82,0.665-1.483,1.484-1.483h15.032C17.335,12.031,18,12.695,18,13.516L18,13.516z"/>
</svg>
</span>
</label>
<div class="trigger">
<a class="page-link"
href="{{ "
/"
|
index
}}">Overview</a>
{%- for path in page_paths -%}
{%- assign my_page = site.pages | where: "path", path | first -%}
{%- if my_page.title -%}
<a class="page-link"
href="{{ my_page.url | relative_url }}">{{ my_page.title | escape }}</a>
{%- endif -%}
{%- endfor -%}
</div>
</nav>
{%- endif -%}
</div>
</header>
\ No newline at end of file
<div class="trigger">
<a class="page-link" href="{{ "/" | index }}">Overview</a>
{%- for path in page_paths -%}
{%- assign my_page = site.pages | where: "path", path | first -%}
{%- if my_page.title -%}
<a class="page-link" href="{{ my_page.url | relative_url }}">{{ my_page.title | escape }}</a>
{%- endif -%}
{%- endfor -%}
</div>
</nav>
{%- endif -%}
</div>
</header>
......@@ -4,14 +4,14 @@
{%- include head.html -%}
<body>
<div class="max-width">
{%- include header.html -%}
<main aria-label="Content">
<div class="wrapper">
{{ content }}
</div>
</main>
</div>
<div class="max-width">
{%- include header.html -%}
<main aria-label="Content">
<div class="wrapper">
{{ content }}
</div>
</main>
</div>
{%- include footer.html -%}
......
# Get involved
<span class="subtitle">
We rely on feedback from other organisations to evolve SLSA and be more useful to more people. We’d love to hear your experiences using it!
</span>
## Feedback
......
......@@ -17,13 +17,13 @@ A security framework from source to service, giving anyone working with software
<section class="buttons-horizontal">
<div class="pseudo-button">
[SLSA levels](/levels.md)
[SLSA levels](levels.md)
</div>
<div class="pseudo-button">
[Requirements](/requirements.md)
[Requirements](requirements.md)
</div>
......@@ -46,10 +46,10 @@ That’s where SLSA can help, building intermediary levels to assess where softw
| Level | Description |
| :---- | :-------------------------------------------- |
| **1** | Documentation of the build process |
| **2** | Tamper resistance of the build service |
| **3** | Prevents extra resistance to specific threats |
| **4** | Highest levels of confidence and trust |
| **1** | Documentation of the build process |
| **2** | Tamper resistance of the build service |
| **3** | Prevents extra resistance to specific threats |
| **4** | Highest levels of confidence and trust |
</div>
</section>
......@@ -62,7 +62,7 @@ We’re developing SLSA collectively to tackle common threats across the supply
<div class="pseudo-button m-t-l">
[Get involved](/getinvolved.md)
[Get involved](getinvolved.md)
</div>
......
# Security levels
<span class="subtitle">
Each level provides an increasing degree of confidence, a way to say that software hasn’t been tampered with and can be securely traced back to its source.
</span>
| Level | Description | Example |
......
# Requirements
<span class="subtitle">
This document covers all of the detailed requirements for an artifact to meet SLSA. For a broader overview, including basic terminology and threat model, see [overview](index.md).
</span>
_Reminder: SLSA is in [alpha](roadmap.md). The definitions below are not yet finalized and subject to change, particularly SLSA 3-4._
......
......@@ -3,7 +3,9 @@
## SLSA is currently in alpha
<span class="subtitle">
Google has been using an internal version of SLSA since 2013 and requires it for all of Google's production workloads.
</span>
We encourage the community to try adopting SLSA levels incrementally and to share your experiences back to us. We rely on feedback from other organisations to evolve SLSA and be more useful to more people. [Please get involved!](getinvolved.md)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment