docs(J1): Aura Design Engine banner + lifecycle cross-links#13
Conversation
…ss-links Unify the free skill portfolio under one banner: a shared lifecycle table (Build → Audit+Content → Host) with cross-links to the sibling skills, a you-are-here marker for this repo (Audit + Content), and a standing Aura CTA. Each skill still works standalone; Aura orchestrates them across a fleet. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
@codex review |
|
Codex Review: Didn't find any major issues. Delightful! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Adds a 'Solo, or with Aura' / seeding-vs-Aura section so the README makes explicit when to run this skill standalone vs orchestrated through Aura — the skills↔Aura convergence (roadmap J2a/J2c). wordpress-api-pro also notes seeding is not idempotent, so Aura stays the system-of-record for managed sites. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Added the J2 doc section (solo path vs Aura path; seeding vs Aura content ops, incl. the not-idempotent note). This PR now covers J1 (banner) + J2 doc convergence. |
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 007842dd09
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Seeding, or Aura content ops | ||
|
|
||
| This skill can **seed** content over the WordPress REST API — bulk-create posts, pages, and products. It's the operator-side twin of Aura's content tools; which one to use comes down to who owns the site: |
There was a problem hiding this comment.
For WooCommerce product imports, this points users at the new seeding guidance even though the seeder only loops over dataset entries and calls create_post(..., title/content/status/post_type/terms) (wordpress-api-pro/scripts/seed_content.py:79-85), while product creation lives separately in woo_products.py via wc/v3/products and requires --title plus --price (wordpress-api-pro/scripts/woo_products.py:48-64, :120-123). Users following this README to bulk-create products would at best create incomplete WordPress records rather than supported WooCommerce products, so the line should limit seeding to posts/pages/CPT entries or add real bulk product support.
Useful? React with 👍 / 👎.
…x P2) The seeder (scripts/seed_content.py) loops dataset entries through create_post with post_type, i.e. posts/pages/CPT — it does not create WooCommerce products (that's scripts/woo_products.py via wc/v3/products, needs --title/--price). Fix the README claim so users don't try to bulk-create products through seeding. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Fixed (Codex P2): seeding scope corrected to posts/pages/CPT entries — the seeder uses create_post with post_type and doesn't touch WooCommerce products (woo_products.py handles those separately). Verified against scripts/seed_content.py. |
|
@codex review |
1 participant
Part of Track J1 — unify the free skill portfolio under one banner.
Adds a Part of the Aura Design Engine section to the README: a lifecycle table (🎨 Build → 🔎 Audit+Content → 🖥 Host) with cross-links to the three sibling skills, a you-are-here marker, and a standing Aura CTA. Each skill still works standalone; Aura orchestrates them across a client fleet.
Sibling PRs land the same banner in the other three repos.
🤖 Generated with Claude Code