Guide v0: persona-routed iptf-map projection by Meyanis95 · Pull Request #31 · ethsystems/web

Meyanis95 · 2026-05-08T18:45:19Z

Summary

Adds Guide v0 in guide/ — an Astro static site that projects iptf-map content into use-case, pattern, vendor, domain, jurisdiction, FAQ, and glossary views.
Purely additive: doesn't touch the Jekyll site at the repo root, so merging doesn't change what's live at iptf.ethereum.org today.
Draft for team review against Guide v0: ship persona-routed web product on iptf.ethereum.org #29 — opens the discussion on what we want from v0 and how to flip the deploy.

What's here

Static site at guide/ (Astro 5 + React islands)

Routes: /, /approaches, /patterns, /vendors, /domains, /jurisdictions, /faq, /glossary, /explore/{galaxy,tree,browse}, /about, /blog.
Build pipeline (guide/scripts/build-graph.mjs) reads the content/ submodule pinned at iptf-map and generates graph.json + glossary.json at build time. No hand-editing.
Source-of-truth rule encoded: anything from iptf-map renders verbatim (marked with SOURCE: at every render site). UI chrome is the Guide's own.
v2 schema integration — patterns expose structured crops_profile, crops_context, post_quantum, context_differentiation. Approach pages render persona perspectives, sub-approach cards, comparison tables, and the recommendation block.

Live preview: https://iptf-web.vercel.app/ (Meyanis95/iptf-web fork, deploys from this branch).

v0 scope (proposed rescope vs #29 — see comment thread)

Entry point: approaches surfaced as case studies. Persona perspectives stay where they are today (rendered as tabs inside each approach page), no persona frontmatter or persona filtering.

Still open for v0:

Homepage surfaces approaches as the primary entry point (today the index links to all sections equally).
Populate FAQ.md in iptf-map with real content so /faq stops rendering placeholders. Single-source, no per-pattern link-up.
Validation with ≥3 target-persona readers.

Dropped from #29 after discussion (see comment):

~~Persona tags in frontmatter~~ — most patterns are relevant to all personas; filtering would discard information. Persona perspectives in body are sufficient.
~~Per-pattern faq: field~~ — central FAQ.md is enough.

Transition plan (out of scope for this PR — open for discussion)

This branch lands the Guide alongside the existing Jekyll site without changing the live deploy. The deploy switch is a separate decision:

Deploy target: GitHub Pages (Astro static export) vs Vercel. The CNAME currently points iptf.ethereum.org at GitHub Pages (Jekyll).
Jekyll site: keep /blog on Jekyll and let Astro own everything else, or migrate posts into Astro and retire Jekyll entirely.
Blog posts: 6 posts in _posts/ — plan is to keep them as-is (Astro can read the same Markdown).
Submodule on deploy: how to fetch content/ reliably during the GH Action / Vercel build.

Would appreciate team input on (1) and (2) before sequencing the cutover.

Test plan

cd guide && npm install && npm run dev boots locally at http://localhost:4321
Browse the routes above on the Vercel preview and spot-check rendering against iptf-map content
Verify narrow-viewport behaviour (≤720px, ≤1024px)
cd guide && npm test — content pipeline and graph-layout tests pass
Confirm no changes to the Jekyll site → iptf.ethereum.org continues to render today's content after merge

Closes #29 once the deploy-switch follow-ups land.

🤖 Generated with Claude Code

…, relocate explorer Parser update — switches `build-graph.mjs` to `js-yaml` and reads the new pattern + approach templates: nested `crops_profile`/`crops_context`, `post_quantum`, typed `related_patterns`, `open_source_implementations`, `iptf_pocs`, `primary_patterns`/`supporting_patterns`, `use_case`, and the meta-pattern `type` (renamed to `kind` to avoid colliding with our node-type discriminator). Edges are now generated from structured frontmatter first, with body-link extraction as a fallback. Source-of-truth — `extractSummary` returns the full first paragraph verbatim (no 200-char truncation). Pattern + approach index cards no longer fall back to truncated text. Detail and index renderers carry `SOURCE: iptf-map field — do not alter` comments at every map-content site. UI chrome (FAQ, testimonials, landing copy, vendor disclaimer) is the Guide's own and stays curated. Approach detail (`approaches/[slug].astro`) — full rewrite against the v2 schema. Renders Problem framing, sub-approach blocks (with embedded YAML metadata, labelled bodies, benchmarks), Comparison table, persona perspective tabs, Recommendation, Open questions, and optional Example scenario. Sidebar surfaces primary/supporting patterns, IPTF PoCs, open-source implementations, vendors, and related use cases. Pattern detail (`patterns/[slug].astro`) — picks up new fields: `crops_context` narrative table, `post_quantum` block, typed `related_patterns` groups (requires/composes_with/alternative_to/ see_also), open-source implementations, sub-pattern list for meta patterns, context_differentiation callouts. Explorer relocation — `pages/tree.astro` and `pages/browse.astro` moved into `pages/explore/`, with a new `explore/galaxy.astro` to recover the old Galaxy index. Linked unobtrusively from the Guide footer; not part of primary nav. React + D3 deps stay since `/explore/*` uses them. Tests under `guide/tests/` predate this rewrite and target the old parser shape. They need to be rewritten to match v2; deferred to follow-up per plan.

…ive domain counts Wire `src/styles/global.css` into Guide.astro — was never imported, so all `.prose` rules were dead and rendered markdown fell back to browser defaults (16px disc bullets, no padding). Bullets now render as the prototype's custom dot style (`list-style: none` + `::before` dot at 0.55em); body text and tables pick up the prototype font sizing. Approach detail rewrite: persona tabs at top with single indigo color, compact 2-col card grid for architectural options, recommendation as highlighted box, per-architecture detail in collapsibles, comparison + benchmarks render through proper :global(.prose table) styling. Landing: - Drop "Humanitarian Orgs" from the cycling word list - About link points to new /about route, Blog link to existing Jekyll blog at iptf.ethereum.org/blog/ - New "Latest posts" section reads recent posts from the Jekyll _posts/ directory at build time (via import.meta.glob) and surfaces 3 cards with hero images linking to the live blog New /about page: short team description + initiatives (Privacy Map, PoCs, Coordination) + contact cards (email + institution/vendor forms), matching the previous Jekyll landing in the Guide UI. Nav: remove Jurisdictions from primary nav (still reachable via direct URL); explorer/about/blog/contact in the footer. Domain case-study counts are now transitive: domain → use-case ← approach via the `addresses` edge, so /domains/* shows real counts (e.g. Funds & Assets → 7) instead of 0 from the missing direct edge. Cross-cut domains (Custody, Identity & Compliance, Post-Quantum Threats) correctly stay at 0 because their markdown lists no use-cases.

Pin was at 4e72090 (pre-v2). The v2 migration moved approaches to a structured schema (Problem framing / Approaches / Comparison / Persona perspectives / Recommendation / Open questions) which the new guide parser expects. Vercel build was rendering empty approach pages because the submodule still served the old format. Bumps content/ to c8addba (v0.3.0-13-gc8addba) on iptf-map main.

- Drop CROPS row from approach comparison tables (already rendered as pills on the architecture cards above). - Neutralize CROPS-context label colors on patterns; stack rows on narrow viewports. - Remove the "{level} risk" badge from the post-quantum block and switch to neutral coloring; vector + mitigation still document the threat and path forward. - Parse `[role]` prefix from protocol steps and render it as a small badge in a fixed column so step text aligns across rows. - Collapse the pattern page grid to a single column below 1024px. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rymnc · 2026-05-08T18:56:17Z

@copilot can you audit the dependencies please

Agent-Logs-Url: https://github.com/ethereum/iptf-web/sessions/80852098-5eb0-49cb-be42-0065694e6081 Co-authored-by: rymnc <43716372+rymnc@users.noreply.github.com>

Copilot · 2026-05-08T18:59:18Z

@copilot can you audit the dependencies please

Dependency audit complete. Updated astro to 6.3.1 and @astrojs/react to 5.0.4; npm audit now reports 0 vulnerabilities. Commit: 1bc46e5.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

telemetry.astro.build
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/iptf-web/iptf-web/guide/node_modules/.bin/astro build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

rymnc · 2026-05-08T19:01:31Z

@Meyanis95, seems like copilot just pushed a commit, feel free to overwrite it if you would like

Meyanis95 · 2026-05-08T19:02:47Z

I mean, you invoked it, not sure to understand what you're doing here.
Feel free to rollback.

oskarth

Review notes from local verification. I ran npm ci, npm run build, npm test, and npx tsc --noEmit against origin/test_guide.

oskarth · 2026-05-09T14:00:33Z

+    // Apply colors
+    nodeSel.selectAll('circle, rect, polygon')
+      .attr('fill', (_, i, nodes) => {
+        const d = d3.select(nodes[i].parentNode as Element).datum() as SimNode;


Medium: strict TypeScript does not pass here. npx tsc --noEmit reports that nodes[i].parentNode may be null and that the D3 callback node can be EnterElement, which does not expose parentNode. The same issue repeats on lines 190 and 195.

Going to do these in a small follow-up. Page works at runtime; just hygiene.

oskarth · 2026-05-09T15:25:54Z

I think the commit pushed was just general best practice (Astro dep push), and A is saying can either keep it or over-write it depending on preference.

rymnc

can we also add a github action that runs nightly, fetches latest commit from iptf-map, and regenerates the graph and deploys? will cut down maintenance overhead

rymnc

also, lets merge the writeups into this, there is no reason we need to have a different site for writeups and this landing page

oskarth · 2026-05-11T12:14:41Z

Writeups should keep same url as before

- Drop the `truncates long summaries` test. `extractSummary` does not implement truncation and shouldn't (verbatim-render rule). - Update the `fileToSlug` and integration-test fixtures from `pattern-zk-shielded-balances` (removed in the v2 schema bump) to `pattern-zk-proof-systems`. Addresses oskarth review on PR #31. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

- Drop the silent CONTENT_SUBMODULE fallback in candidate resolution. If no candidate has a `patterns/` directory, throw with a clear message pointing at `git submodule update --init --recursive`. - Add a 0-node guard in the CLI main block after buildGraph(). The guard lives in the CLI, not inside buildGraph(), so the test suite can still call buildGraph(repoRoot) directly without tripping it. Previously a fresh checkout with an uninitialized submodule produced "Graph built: 0 nodes, 0 edges" and deployed empty index pages. Addresses oskarth review on PR #31. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

iptf-map authors write portable Markdown for GitHub readers (`../patterns/pattern-foo.md`). When the Guide rendered those bodies through `marked()` directly, 186 raw `.md` hrefs leaked into `dist/` as broken links. - Add `guide/src/lib/render.ts` exporting `renderMarkdown` and `renderMarkdownInline`. Registers a marked link renderer that rewrites relative `.md` hrefs to Guide routes (e.g. `../patterns/pattern-foo.md` → `/patterns/foo`). Leaves absolute URLs, `#anchor` and `mailto:` links untouched. - Validate resolved routes against the current graph node set; `console.warn` once per unresolved href so data drift in iptf-map becomes visible at build time without failing the build. - Replace every `marked(...)` / `marked.parse(...)` / `marked.parseInline(...)` call across approach, pattern, domain, vendor, jurisdiction pages and the DetailPanel React island with the shared helpers. `grep -rohE 'href="[^"]*\.md[^"]*"' dist/` drops from 186 to ~12, all of which are either intentional absolute GitHub source-file URLs or upstream typos (`pattern-dvp-erc7573.md.md`) surfaced by the warnings. Addresses oskarth review on PR #31. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Approach detail pages render a "Use case: ..." chip that links to `/use-cases/<slug>`, and approach sidebars list related use-cases the same way. No `/use-cases` routes existed, so every one of those links 404'd on the staging build. - Add `guide/src/pages/use-cases/index.astro` — card-grid index sorted alphabetically, modeled on `approaches/index.astro`. Reserves an image slot for the follow-up hero-thumbnail work so layout doesn't need restructuring later. - Add `guide/src/pages/use-cases/[slug].astro` — detail page following the simplest existing template (`jurisdictions/[slug].astro`). Renders body via the shared renderer so internal map links resolve. Surfaces related case studies, building-block patterns, and regulating jurisdictions. - Add "Use Cases" to the top nav in `Guide.astro` alongside Case Studies / Patterns / Vendors / Domains, and add `'use-cases'` to the `activeSection` union. 20 new use-case pages emitted; the broken approach chips now resolve. Addresses oskarth review on PR #31. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…uide

netlify · 2026-05-11T16:52:57Z

✅ Deploy Preview for iptf-stagging ready!

Name	Link
🔨 Latest commit	`1ef48e2`
🔍 Latest deploy log	https://app.netlify.com/projects/iptf-stagging/deploys/6a1ef69b351b3f0007b1240c
😎 Deploy Preview	https://deploy-preview-31--iptf-stagging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Meyanis95 · 2026-05-11T17:04:37Z

Addressed critical issues from @oskarth.
Stagging deployment now available at: https://iptf-stagging.netlify.app/
Will follow up with consolidation of Astro over Jekyll, and write-up merge.

Replaces the Jekyll + legacy map/ + guide/ tri-stack with a single Astro app served from the repo root. Closes the staging-to-production transition on PR #31. Promotes guide/ to root: moves astro.config.mjs, tsconfig.json, package.json, src/, scripts/, tests/, and .claude/launch.json out of the subfolder. Adds vitest.config.ts to scope test discovery and updates the integration test's content/ path from `../../content` to `../content`. Migrates blog writeups: _posts/*.md -> src/posts/*.md. Adds the following Astro routes/layouts: - src/pages/[slug].astro post detail at root - src/pages/blog/index.astro archive at /blog/ - src/layouts/Post.astro post layout + JSON-LD BlogPosting - src/pages/feed.xml.js RSS via @astrojs/rss - @astrojs/sitemap registration /sitemap.xml at build time URLs are preserved: posts keep their `/<slug>/` paths via a Jekyll-compatible slugify of the frontmatter title. External inbound links don't break. Open Graph + Twitter meta added centrally in Guide.astro so every page emits og:title, og:description, og:image, og:type, og:url, plus the twitter:* equivalents and a canonical link. Static assets relocated to public/: assets/, CNAME, robots.txt, tee-protocol-page.html. Same URLs. Deletes the Jekyll surface (_config.yml, Gemfile, _layouts/, _includes/, _drafts/, _posts/, index.md, blog.html, serve.sh) and the legacy map/ Astro app (duplicated by src/pages/explore/). Rewrites .github/workflows/deploy.yml to build the Astro app from the repo root (no Ruby step, no map/ build, no merge). Rewrites root README.md and CLAUDE.md to describe the new layout. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

The CONTENT_SUBMODULE path was `__dirname/../../content` which worked when scripts/ lived at guide/scripts/. After the cutover, that resolved one level above the repo (/opt/build/content on Netlify), tripping the fail-fast guard introduced for empty submodules. Drops one `..` so it resolves to repo-root/content. Also drops the stale `__dirname/../../../iptf-map` and `$HOME/IPTF/iptf-map` candidates: the git submodule covers the canonical case, and IPTF_MAP_PATH still works as an explicit override for unusual local layouts. File also reformatted to project style. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rymnc · 2026-05-12T17:01:41Z

@Meyanis95 https://iptf-stagging.netlify.app/resilient-plural-identity/

the images which don't have backgrounds are not visible because the site is dark mode by default, how do you propose we fix this? I see two options -

1/ invert the colors on the images and update them
2/ some astro configuration to add a white background to the images?

I would suggest the former

Three rendering issues surfaced after the cutover landed: - `/blog` and `/use-cases` headers were unstyled because the `.idx-page` / `.idx-header` / `.idx-label` / `.idx-title` / `.idx-desc` rules only lived inside `approaches/index.astro`'s scoped `<style is:global>` block. Astro's `is:global` only loads styles when the defining page is rendered, so sibling index pages didn't pick them up. Moved the shared rules to `src/styles/global.css` and dropped the duplicates from approaches/index.astro. - Post body diagrams (transparent PNGs against a light page, e.g. the Traditional System diagram on `/resilient-plural-identity/`) rendered black-on-black on the site's dark theme. Added a warm off-white background to `.post-body img` so dark strokes show through transparent areas; opaque images cover the background, so it's a no-op for them. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…e line Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Meyanis95 · 2026-05-12T20:20:36Z

@rymnc @oskarth @mojalil
I pushed a bunch of fixes, all from the latest convo, and also wiped out the previous Jekyll setup, making it easier to read/review.
Ready for review.

rymnc · 2026-05-13T08:38:22Z

nice haha

rymnc · 2026-05-13T08:38:33Z

@Meyanis95 can we add a favicon please

rymnc · 2026-05-13T08:41:26Z

markdown formatting leaking into descriptions

https://iptf-stagging.netlify.app/vendors/

rymnc · 2026-05-13T08:43:00Z

on the landing page, this is the navbar:

if i click about / blog, this is the navbar:

intentional?

if so, please try to make the alignment of "About | Blog" the same position in both views for cohesiveness

oskarth · 2026-05-13T09:23:40Z

Copy paste from chat:

https://iptf-stagging.netlify.app/

One thing re IA: I feel like it downplays writeups, which is one of the key artifacts

Is it possible for us to bring this up on same level as case studies? In terms of quality, we spend a lot more effort on writeups vs say, private money market file "case study"

---

Another thing I was thinking about is the use of "case study", to me this implies actually going through a case study with a specific institution

Right now the map use case/approaches we have feels a bit different?

This might be a bit confusing to people IMO

I do think we should have proper case studies, but not sure if what we currently have qualifies as it?

---

https://iptf-stagging.netlify.app/domains/ Re domains this also seems to be quite FI heavy, I feel like we might want to make this a bit more inclusive of eg survive track + mandate/crops stuff?

---

https://iptf-stagging.netlify.app/faq/ I like the FAQ; I can see this being useful to a lot of ppl

---

> What institutions tell us

I'd suggest we hide this until we have this social proof, maybe can capture in "enhancement" GH issue

---

> evaluation framework

CROPS and I2I I2U acronyms should probably be explained somewhere

rymnc · 2026-05-13T10:18:06Z

do we need this page?

https://iptf-stagging.netlify.app/about/

oskarth · 2026-05-13T10:40:02Z

About page always nice to have IMO

rymnc · 2026-05-13T10:59:05Z

About page always nice to have IMO

yes but it looks like the one from the old site, perhaps just needs a design refresh

Meyanis95 · 2026-05-13T15:39:39Z

Is it possible for us to bring this up on same level as case studies?

Agree we can put more emphasis on writeups. That said, I see these as two different funnels: writeups travel through social media and privacy team channels, while the landing is meant for curious people coming in after a workshop or conference talk. Both should be well-served but they might not need to live at the same level as they don't really serve the same purpose. Open to small tweaks to bump writeup presentation quality on the landing though, anything specific you had in mind? (upper positioning, change the grid, ...)

Right now the map use case/approaches we have feels a bit different?

Fair point, that it doesn't fully qualify as case study. The rationale here is to try to meet readers where they are, and re-use verbatims. Other terms that you see often on institutional resources are: insights, survey, case study, our solutions. "approaches" doesn't really show up in their vocabulary. Any preference between those, or another term you've seen land well with this audience?

I feel like we might want to make this a bit more inclusive of eg survive track + mandate/crops stuff?

100%
This one is really a map-level scoping question (the web just renders what's there), so I'll open a follow-up issue in iptf-map to broaden coverage toward survive track + mandate/CROPS material rather than fix it in this PR.

do we need this page?

~~yes, helpful to have it as an anchor for contacts and small team context. Agree on the design, but it shouldn't be a priority for now.~~

All the other comments have been added to the to-do, and fixes will be pushed.
EDIT: fixes pushed in 29161c6
EDIT 2:

writeups are now on visible at the same level of approaches
case studies renamed approaches
modified domains to include survive track work

- add favicon (indigo brand mark) wired into both layouts - strip inline markdown from extracted summaries so vendor descriptions render as plain text - migrate landing to Guide layout so the top nav matches sub-pages - hide "What institutions tell us" testimonials section pending real social proof - spell out CROPS / I2I / I2U inline on the eval section Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Reworked guide site: information architecture, design system, and scoped Astro components. Domain listing is data-driven from the content collection with a build-time validation guard (includes Civic Coordination & Governance). Domain descriptions render as section primers. Adds team and workshop photos. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

feat: Website UI/UX rework

…_guide # Conflicts: # src/posts/2026-05-14-resilient-disbursement-rails.md # src/posts/2026-05-28-resilient-civic-participation.md

…o test_guide

rymnc

adding QA:

1/

too much gap on https://iptf-stagging.netlify.app/use-cases/private-procurement/ assuming all use-cases have this issue

2/

data and oracles misaligned

3/

too much gap between the header and use cases in https://iptf-stagging.netlify.app/use-cases/

4/

table not aligned on https://iptf-stagging.netlify.app/approaches/approach-dvp-atomic-settlement/

assuming all approaches have the same issue

5/

too much whitespace between writeups and header

https://iptf-stagging.netlify.app/blog/

6/

artifacts look elongated here, out of aspect ratio: https://iptf-stagging.netlify.app/

oskarth

Better to merge and work iteratively! LGTM

oskarth · 2026-06-01T11:22:53Z

Agree with @rymnc comments

Also noticed we removed contact us, was this deliberate? any reason we cant have three buttons

Meyanis95 · 2026-06-01T16:16:57Z

Resolved all the above comments from @rymnc

Also noticed we removed contact us, was this deliberate?

Yes, Jakub (UX) didn't recommend having 3 buttons here. It's something we can iterate on depending on what we want to prioritize.

…uild check - astro.config.mjs: site was still iptf.netlify.app — canonical/OG URLs now point to iptf.ethereum.org - Add permanent redirects for all 13 legacy Jekyll post URLs (/:title/ from filename) to their new title-derived /blog/<slug>/ routes - Add @astrojs/sitemap (replaces jekyll-sitemap) and point robots.txt at sitemap-index.xml - deploy.yml: run the build job on pull_request (validate without deploying) so deploy breakage is caught before merge Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Meyanis95 and others added 4 commits May 7, 2026 16:17

Meyanis95 mentioned this pull request May 8, 2026

Guide v0: ship persona-routed web product on iptf.ethereum.org #29

Closed

9 tasks

Copilot started work on behalf of rymnc May 8, 2026 18:56 View session

chore: update astro dependencies

1bc46e5

Agent-Logs-Url: https://github.com/ethereum/iptf-web/sessions/80852098-5eb0-49cb-be42-0065694e6081 Co-authored-by: rymnc <43716372+rymnc@users.noreply.github.com>

Copilot finished work on behalf of rymnc May 8, 2026 19:00

Copilot AI requested a review from rymnc May 8, 2026 19:00

oskarth reviewed May 9, 2026

View reviewed changes

rymnc reviewed May 11, 2026

View reviewed changes

Meyanis95 and others added 5 commits May 11, 2026 12:47

Merge branch 'test_guide' of github.com:ethereum/iptf-web into test_g…

511f05c

…uide

Meyanis95 and others added 3 commits May 12, 2026 10:26

Merge remote-tracking branch 'origin/main' into test_guide

42a0c47

Meyanis95 and others added 3 commits May 12, 2026 15:43

feat(ui): approach card thumbnails, domain TLDR bullets, drop use-cas…

a4a968a

…e line Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

feat(og): per-approach OG/Twitter image on detail pages

5cff2c4

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

feat(posts): syntax-highlight code blocks via shiki

fcdc5ee

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Meyanis95 marked this pull request as ready for review May 12, 2026 20:19

Meyanis95 requested review from mojalil, oskarth and rymnc May 12, 2026 20:20

Meyanis95 and others added 6 commits May 13, 2026 12:07

Homepage: swap hero "Contact us" for "See writeups" → blog

c17fb12

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

feat: Website UI/UX rework

9ba5f5a

feat: Website UI/UX rework

Merge branch 'main' of https://github.com/ethereum/iptf-web into test…

e3665cb

…_guide # Conflicts: # src/posts/2026-05-14-resilient-disbursement-rails.md # src/posts/2026-05-28-resilient-civic-participation.md

Merge branch 'test_guide' of https://github.com/ethereum/iptf-web int…

2fb32ad

…o test_guide

rymnc reviewed May 30, 2026

View reviewed changes

oskarth approved these changes Jun 1, 2026

View reviewed changes

fix(UI): resolve rymnc comments

0d26e4f

Meyanis95 merged commit 113d3cd into main Jun 2, 2026
7 checks passed

Uh oh!

Conversation

Meyanis95 commented May 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What's here

v0 scope (proposed rescope vs #29 — see comment thread)

Transition plan (out of scope for this PR — open for discussion)

Test plan

Uh oh!

rymnc commented May 8, 2026

Uh oh!

Copilot AI commented May 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

rymnc commented May 8, 2026

Uh oh!

Meyanis95 commented May 8, 2026

Uh oh!

oskarth left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

oskarth May 9, 2026

Choose a reason for hiding this comment

Uh oh!

Meyanis95 May 11, 2026

Choose a reason for hiding this comment

Uh oh!

oskarth commented May 9, 2026

Uh oh!

rymnc left a comment

Choose a reason for hiding this comment

Uh oh!

rymnc left a comment

Choose a reason for hiding this comment

Uh oh!

oskarth commented May 11, 2026

Uh oh!

netlify Bot commented May 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for iptf-stagging ready!

Uh oh!

Meyanis95 commented May 11, 2026

Uh oh!

rymnc commented May 12, 2026

Uh oh!

Meyanis95 commented May 12, 2026

Uh oh!

rymnc commented May 13, 2026

Uh oh!

rymnc commented May 13, 2026

Uh oh!

rymnc commented May 13, 2026

Uh oh!

rymnc commented May 13, 2026

Uh oh!

oskarth commented May 13, 2026

Uh oh!

rymnc commented May 13, 2026

Uh oh!

oskarth commented May 13, 2026

Uh oh!

rymnc commented May 13, 2026

Uh oh!

Meyanis95 commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rymnc left a comment

Choose a reason for hiding this comment

Uh oh!

oskarth left a comment

Choose a reason for hiding this comment

Uh oh!

oskarth commented Jun 1, 2026

Uh oh!

Meyanis95 commented May 8, 2026 •

edited

Loading

Copilot AI commented May 8, 2026 •

edited

Loading

netlify Bot commented May 11, 2026 •

edited

Loading

Meyanis95 commented May 13, 2026 •

edited

Loading