Explore Custom Post Types handling in Blueprint

Open
#32 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php, wordpress
Domain
content

Research direction

The issue names no implementation files, entry points, or tests. Start by clarifying the proposed Blueprint schema for custom post types, including validation and autocomplete expectations, then identify the relevant Blueprint implementation and test locations. Done means an agreed, documented design with a defined scope and acceptance criteria.

Written by the indexing model from the issue text.

Description

enhancement

Whenever I am selling the idea of WordPress to people, I always like to show how easy it is to implement custom functionality for different use cases.
For example:
"I want a website that is a book catalog"

I always send then to online generators for CPTs and Custom Meta.
ACF entire selling point is to provide this glue code.
It would be nice if blueprint offered an opinionated, very lean options to create a website with those features.

TBD more examples once I think about it more :D

Goals

  1. Ability to express any CPT
  2. Autocompletion for devs
  3. Easy for GPT to generate (e.g. Via a simple, validated schema?)
Dominant language
PHP
Stars
61
Forks
21
Avg merge
19h 34m
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/php-toolkit

All issues in WordPress/php-toolkit

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.