Skip to content

Commit da5d81b

Browse files
authored
Merge pull request #385 from simonbaird/more-renaming
Some more changes related to the new name
2 parents 665c155 + a3c2f2b commit da5d81b

10 files changed

+50
-14
lines changed

README.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,18 @@
11

2-
# enterprise-contract.github.io
2+
# conforma.github.io
33

4-
These are the sources for building the https://enterprisecontract.dev website.
4+
These are the sources for building the [conforma.dev][conforma] website.
55
The website uses [Hugo](https://gohugo.io/) and
66
[Antora](https://docs.antora.org/) to build different sections of the website.
77

88
Includes:
9-
* [Website content](./website), built with [Hugo](https://gohugo.io/), published at [enterprisecontract.dev][ec]
10-
* [Documentation](./antora), built with [Antora](https://antora.org/), published
11-
at [enterprisecontract.dev/docs][ec-docs]
129

10+
* [Website content](./website),
11+
built with [Hugo](https://gohugo.io/),
12+
published at [conforma.dev][conforma]
13+
* [Documentation](./antora),
14+
built with [Antora](https://antora.org/),
15+
published at [conforma.dev/docs][conforma-docs]
1316

1417
## Live reload preview
1518

@@ -36,11 +39,10 @@ extensions are [linked](https://docs.npmjs.com/cli/v6/commands/npm-link), so
3639
instead of the versions released to npmjs.com, local versions with any local
3740
changes will be used.
3841

39-
Opening the `enterprise-contract.github.io.code-workspace` workspace file within
42+
Opening the `conforma.github.io.code-workspace` workspace file within
4043
VSCode will load the Node projects of the same extensions and the `Antora Build`
4144
launch configuration in `.vscode/launch.json` allows running the debugger
4245
against those.
4346

44-
45-
[ec]: https://enterprisecontract.dev
46-
[ec-docs]: https://enterprisecontract.dev/docs
47+
[conforma]: https://conforma.dev
48+
[conforma-docs]: https://conforma.dev/docs
File renamed without changes.

package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
{
2-
"name": "@enterprisecontract.dev/website",
2+
"name": "@conforma.dev/website",
33
"version": "0.0.0",
44
"description": "Website for Conforma (formerly Enterprise Contract)",
55
"license": "Apache-2.0",
66
"bugs": {
7-
"url": "https://issues.redhat.com/browse/HACBS"
7+
"url": "https://issues.redhat.com/browse/EC"
88
},
9-
"homepage": "https://enterprisecontract.dev",
9+
"homepage": "https://conforma.dev/",
1010
"engines": {
1111
"node": "20"
1212
},

website/content/posts/a-taste-of-policies.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ policies.
1111

1212
<!--more-->
1313

14+
{{< conforma-name-preamble >}}
15+
1416
Throughtout this post, we will use a container image from one of the author's side projects. This
1517
image was
1618
[built](https://github.com/lcarva/festoji/blob/848edc452ccbc6d42ec56c2807eef2f49e754c5e/.github/workflows/package.yaml)

website/content/posts/evaluating-custom-predicates.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ assert the contents of *any* attestation format, even completely made up ones.
1313

1414
<!--more-->
1515

16+
{{< conforma-name-preamble >}}
17+
1618
Before getting started, let's make sure we have an image that is already signed and has a SLSA
1719
Provenance attestation. We will also need access to the signing key used. The [Hitchhiker’s
1820
Guide](https://enterprisecontract.dev/docs/user-guide/hitchhikers-guide.html) walks through the

website/content/posts/gating-image-promotion-on-gitlab.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ achieve this in a [GitLab] pipeline.
1010

1111
<!--more-->
1212

13+
{{< conforma-name-preamble >}}
14+
1315
> See the [appendix](#appendix) section for the full example.
1416
1517
Consider a simple [.gitlab-ci.yaml] file:

website/content/posts/introducing-action-validate-image.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ processes or any other automated workflow in GitHub.
1111

1212
<!--more-->
1313

14+
{{< conforma-name-preamble >}}
15+
1416
## What is EC Validate Action?
1517

1618
**EC Validate** is a GitHub Action that brings validation capabilities of the Enterprise Contract CLI directly into your GitHub Workflow. Designed to integrate seamlessly into your build pipeline, this action offers both compliance assessments and integrity checks for your container images. It ensures that your images meet both organizational and industry standards before deployment or environment promotion.

website/content/posts/introducing-the-enterprise-contract.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ built on those technologies.
1010

1111
<!--more-->
1212

13+
{{< conforma-name-preamble >}}
14+
1315
## Before starting…
1416

1517
Let’s say you have an image, `quay.io/lucarval/demo:ec`, and you want to verify this image was signed
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
<!--
2+
For better or worse I copied this formatting from Antora.
3+
https://docs.antora.org/antora/latest/asciidoc/admonitions/
4+
5+
Todo maybe: Convert the admonition formatting to a generic reuable
6+
shortcode and use .Inner for the content.
7+
8+
-->
9+
<div class="admonitionblock note">
10+
<table>
11+
<tbody>
12+
<tr>
13+
<td class="icon">
14+
<i class="fa icon-note" title="note"></i>
15+
</td>
16+
<td class="content">
17+
This blog post refers to Conforma by its original name, "Enterprise Contract".
18+
But don't worry! The only thing we've changed is the name. The examples described
19+
here should work exactly the same.
20+
</td>
21+
</tr>
22+
</tbody>
23+
</table>
24+
</div>

0 commit comments

Comments
 (0)