COPE with WordPress
summary
Claims a workable COPE pipeline that turns Gutenberg post HTML into a single-source JSON feed and exposes it via API endpoints. It parses editor output with WordPress’s parse_blocks, flattens nested/reusable blocks, strips nonsemantic HTML, extracts missing fields with regex, and maps per-block metadata into a block metadata endpoint (REST, GraphQL as JSON string, and PoP). Proof-of-concept code lives on GitHub and demonstrates filtered queries (e.g., “only images” or “only videos”); limitations include HTML-heavy captions, some block types unsuitable, and GraphQL type proliferation.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:56What is COPE
- 1:37How does it work
- 2:29How to do it
- 3:54Why WordPress
- 5:13Blob vs Blow
- 5:53What is Blow
- 7:31How Gutenberg stores the information
- 16:25GitHub repo
- 16:41Data transformation
- 17:39Other blog types
- 19:28API
- 22:22GraphQL
- 23:13Popup Library
- 23:37Block Metadata
related talks
21mAPI-first Development with Headless WordPress
48mLightning talks from Josh Pollock, Andrew Kaiser, Cole Turner and Jason Clark
24mProgressive Content Management Systems
29mAngular & WordPress: Practical guide to headless CMS
42mHeadless CMS
31mUsing WordPress for an editorial team
07mBy the Power of Headless!
56mUsing WordPress as a Modern Web Dev