Skip to content

docs: clarify CC0 license for website content - #35

Merged
oskarth merged 1 commit into
mainfrom
docs/clarify-cc0-license
Jun 16, 2026
Merged

oskarth merged 1 commit into
mainfrom
docs/clarify-cc0-license

Conversation

@oskarth

@oskarth oskarth commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Adds top-level CC0 license.
  • Clarifies that site content, posts, pages, RFPs, writeups, and docs are CC0 unless otherwise stated.
  • Leaves third-party dependency licenses unchanged.

Verification

  • rg -n "CC0|License|Copyright" README.md LICENSE content/README.md content/LICENSE
  • cmp -s content/LICENSE LICENSE

@oskarth
oskarth merged commit 2ac4beb into main Jun 16, 2026
3 checks passed
rymnc pushed a commit that referenced this pull request Sep 25, 2026
Moves the "Building blocks: chainfold" writeup from 24 to 25 September
2026.

## Changes

- Renamed `src/posts/2026-09-24-building-blocks-chainfold.md` →
`2026-09-25-building-blocks-chainfold.md`
- Renamed `src/assets/posts/2026-09-24-building-blocks-chainfold/` →
`2026-09-25-building-blocks-chainfold/` (hero.png, architecture.svg,
recovery.svg, two-views.svg, composition.svg)
- Frontmatter `date: 2026-09-24 14:00:00 +0200` → `2026-09-25 14:00:00
+0200`
- Updated the five in-post asset paths (frontmatter `image:` + four
figure references)

Time of day is unchanged at 14:00 +0200. `rg` found no other reference
to the old date or slug in the repo.

## Public URL is unchanged

`src/pages/writeups/[slug].astro` derives the slug from
`jekyllSlugify(post.data.title)`, not the filename, so the post stays at
`/writeups/building-blocks-chainfold/`. The filename date is convention
only.

## Verified

`npm run build` and `npm test` (55 tests) pass. Building with the date
temporarily backdated renders `/writeups/building-blocks-chainfold/`
with all four SVGs resolving through Astro's asset pipeline
(`/_astro/architecture.*.svg`, `recovery`, `two-views`, `composition`)
and the hero through the `image()` schema helper.

## Publishing window — no regression, but note the gate

`src/lib/posts.ts` `isPublished()` compares the full timestamp, not the
calendar day. The post was **not yet live** at the old date either:
`2026-09-24 14:00:00 +0200` is 12:00 UTC today, and it is currently
~04:45 UTC. So this PR moves the first publish from 12:00 UTC on 24 Sep
to 12:00 UTC on 25 Sep rather than pulling a live post down.

Practical consequence: any build that runs before 12:00 UTC on 25
September drops the post from the site (216 pages instead of 218 — I
reproduced both counts). The site needs a rebuild at or after that time
for the post to appear.

Prompted by: ac

Co-authored-by: ethsystems-bot <321619048+ethsystems-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants