← all branches

content/auto-draft

needs attentionviewing older commit
8c43554 · fullPR #304reviewed 2026-07-14 01:15 UTC0H · 2M · 1L · 2I
The branch
Purpose
Auto-drafted marketing blog post for the CFE tariff content cluster, targeting the 'tarifa GDMTH' keyword identified in the editorial calendar as priority-2 informational content.
Goal
Publish a factually-grounded, SEO-optimised guide to the GDMTH tariff — covering TOU blocks, demand charges, factor de potencia, and the GDMTH-vs-solar calculus — to drive organic search traffic from energy managers and solar integrators in Mexico.
Sub-goals
  • SG-1: New MDX post apps/web/content/blog/tarifa-gdmth.mdx with full frontmatter, 5-item FAQ, two inline chart components, and source citations.
  • SG-2: calendar.yml status flip idea→review to reflect pipeline state.
The changes (whole branch)
What
Added 166-line MDX blog post (tarifa-gdmth.mdx) covering GDMTH tariff structure, TOU blocks, demand formula, factor de potencia, GDMTH vs GDMTO comparison, and solar implications. Flipped draft:false via a follow-up chore commit to enable preview rendering. Updated calendar.yml status from idea to review.
Why
Part of the autonomous content pipeline (content-pipeline.yml) fulfilling the CFE tariff keyword cluster defined in docs/content-strategy.md. Targets 'tarifa GDMTH' — a priority-2 informational keyword with high intent from GDMTH-tariff customers who are the primary buyers of Batu's CFE bill automation.
Areas
apps/web/content/blog/tarifa-gdmth.mdx+166−0apps/web/content/calendar.yml+1−1
Blast
2 files, +167/−1. Content-only change — no code, no schema, no routes. Blog post auto-included in sitemap when draft:false. No API or platform impact.
hero-visual-todo regulatory-source-needs-human-verify
➖ci· gh pr checks returned 'Resource not accessible by personal access token' — CI status unavailable➖coderabbit· No .coderabbit.yaml in repo

Findings · 5

correctness2

medium

Regulatory restructuring claim needs fact-check (CRE → CNE, 2025)

apps/web/content/blog/tarifa-gdmth.mdx:162

The sources section states 'La CRE fue absorbida por la CNE en la reforma energética de 2025.' This is a specific historical claim that can't be verified from the codebase. The cited acuerdo 'CT/11.SE/8-2025' and its DOF publication should be confirmed against the actual DOF entry before publishing. If the restructuring is partial/in-progress rather than complete, the wording may be inaccurate.

medium

FC=0.57 and demand formula sourced from DOF — verify before publish

apps/web/content/blog/tarifa-gdmth.mdx:99

The demand formula `Demanda calculada = Energía (kWh) ÷ (0.57 × 24 × días)` and the FC=0.57 value are attributed to 'Acuerdo CT/11.SE/8-2025, DOF enero 2026'. This specific acuerdo number is new (post-2024 reform) and should be cross-referenced with the CFE tariff table at app.cfe.mx before merging. If the factor changed in a recent resolution, the formula would be wrong. PR checklist item 'CFE / tariff facts accurate' covers this.

conventions2

info

SEO frontmatter: all fields within spec

apps/web/content/blog/tarifa-gdmth.mdx

metaTitle generates `Tarifa GDMTH de CFE: qué es y cómo funciona | Batu` (52 chars, ≤60 ✓) via page.tsx `${post.metaTitle ?? post.title} | Batu` pattern. description is 153 chars (150–160 ✓). FAQPage JSON-LD is auto-emitted for the 5-item faq block. draft:false set by chore commit. Blog post auto-included in sitemap via getAllPostsMeta() ✓.

info

Internal links and MDX components resolve correctly

apps/web/content/blog/tarifa-gdmth.mdx

Internal link `/blog/como-leer-recibo-cfe` targets existing `como-leer-recibo-cfe.mdx` ✓. `TouBlocksChart` and `DemandVsConsumptionChart` are exported from `apps/web/src/components/blog/charts.tsx` and wired in the MDX component map ✓. GdmthBillCallouts is in a JSX comment only, never instantiated ✓. External links go through the MdxLink wrapper with rel=noopener noreferrer ✓.

improvement1

low

Hero visual is a named TODO — PR checklist item will block merge

apps/web/content/blog/tarifa-gdmth.mdx:20

The post renders a visible `> [Visual pendiente — hero]` callout block in place of `<GdmthBillCallouts />`. The component itself is in a JSX comment (`{/* TODO... */}`) so there's no runtime error, and the placeholder is honest to the reader. However, the PR checklist item 'Required visuals present (replace TODO placeholders)' is explicitly unchecked. This is a content-readiness concern, not a code defect — fine to merge to review branch, but the visual should be produced before final publish.

History · 14 commits

  1. c27ea57needs attentionincremental3H · 5M · 4L2026-08-04 17:46
  2. ff69645needs attentionincremental0H · 6M · 8L2026-07-28 18:21
  3. 0257d74safeincremental0H · 0M · 0L2026-07-20 23:00
  4. 0795a9dsafeincremental0H · 0M · 2L2026-07-20 22:42
  5. 5c57414needs attentionincremental2H · 7M · 10L2026-07-20 22:29
  6. 5a57a8fneeds attentionincremental0H · 5M · 8L2026-07-20 17:14
  7. cc9056eneeds attentionfull1H · 3M · 9L2026-07-20 16:40
  8. 8b79d33needs attentionincremental5H · 7M · 11L2026-07-14 18:10
  9. f0c337cneeds attentionincremental1H · 1M · 5L2026-07-14 17:15
  10. 5c9de97needs attentionincremental0H · 5M · 7L2026-07-14 17:02
  11. 92cce08needs attentionincremental1H · 4M · 3L2026-07-14 02:00
  12. b7dd610needs attentionincremental0H · 6M · 7L2026-07-14 01:43
  13. 8c43554needs attentionfull0H · 2M · 1L2026-07-14 01:15current
  14. 2149391blockedfull8H · 6M · 7L2026-07-10 17:30