superpowers-sage:modeling

Classify WordPress content architecture by applying a decision checklist that evaluates reuse, growth, filters, cardinality, detail pages, and search needs to assign elements to static ACF fields, dynamic CPT collections, global Options Pages, relationship fields, or fixed repeaters.

Model Sage and Bedrock content architecture by evaluating each component element through a structured checklist, then outputting implementation guidance including Poet CPT configuration, ACF field definitions, and query patterns while avoiding direct register_post_type usage.

Use WordPress Options Pages instead of ACF fields when content architecture classification identifies elements as globally shared data that needs centralized editing rather than static component fields or dynamic CPT collections.

Configure Poet CPTs by classifying dynamic content collections during the architecture modeling phase, then outputting Poet CPT configuration names and settings as implementation guidance rather than using direct register_post_type registration.

Yes, the content architecture modeling approach explicitly applies to block and Livewire component planning, helping classify component content elements as static fields, dynamic CPT collections, or global Options Pages before implementation.