Files
zeekay 2c6868ba3d brand: finish ZAP rebrand of blog chrome, examples, docs leftovers
Surgical follow-up to the capnp→zap rename, sweeping branding leftovers
the prior pass missed. Display/identity + own-project URLs only; no
library symbols, deps, or wire-protocol semantics touched.

- blog/index.html: title + H1 "Cap'n Proto for Rust" → "ZAP for Rust";
  upstream repo link → github.com/zap-proto/rust; docs link → docs.rs/zap
  (matches crate `documentation` field). Aligns with blog/_config.yml
  which already reads "ZAP for Rust".
- blog/_layouts/post.html: footer self-link capnproto/capnproto-rust →
  zap-proto/rust.
- blog/css/syntax.css: highlighter class .language-capnp → .language-zap.
- benchmark/build.rs: regen doc comment now drives the `zap` CLI.
- example/addressbook_send/README.md: "Cap'N Proto messages" → "ZAP
  messages" (file already used the `zap`/`libzap-dev` binaries).
- zap-rpc/schema/rpc.zap: two orphaned "Cap'n-Proto-based" comment
  phrases → "ZAP-based" (comment-only; the paragraph already says ZAP).
- rename regenerate-capnp-schema-code.sh → regenerate-zap-schema-code.sh.

Preserved as honest attribution / library refs: LLM.md lineage note,
zap-futures/CONTRIBUTORS upstream PR link, benchmark "Cap'n-Proto-derived"
test-case credit, kj:: types in historical blog posts, dated 2014 blog
post prose, upstream copyrights.
2026-06-19 14:54:55 -07:00

36 lines
488 B
HTML

---
layout: default
---
<h1>
{{page.title}}
</h1>
<p>
{{ page.date | date_to_string }}
<p>
{{content}}
<p class="author">
-- posted by <a href="https://github.com/{{ page.author }}">{{ page.author }}</a>
</p>
<div>
<a href="https://github.com/zap-proto/rust">
zap-proto/rust on github
</a>
</div>
<div>
<a href="{{site.baseurl}}/index.html">
more posts
</a>
</div>
<a href="{{site.baseurl}}/feed.xml">
<img src="{{site.baseurl}}/assets/rss.png"
width="14"/>
</a>