etkm-webpage-build

Generate self-contained ETKM HTML pages with inline CSS for WordPress Raw HTML blocks.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-webpage-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: etkm-webpage-build
Source: https://github.com/easttxkravmaga/Claude/tree/main/archive/user/etkm-webpage-build
Command: npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-webpage-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The locked production standard for building ETKM HTML pages ensures consistency, quality, and reliable deployment across multiple domains via WordPress Raw HTML blocks. It covers hero specs, image treatment, section patterns, font loading, responsive breakpoints, and editorial deployment rules, derived from the March 2026 site rebuild (19 pages) and referenced by etkm-event-page, etkm-pdf-pipeline, and etkm-webform-build.

Core Features & Use Cases

  • Self-contained HTML with inline CSS and no external stylesheets or JS, designed for WordPress Raw HTML blocks.
  • Standardized hero, typography, color palette, and responsive patterns to ensure brand-consistent pages across etxkravmaga.com, fightbacketx.com, and etkmstudent.com.
  • Modular section patterns (Hero, Split Content, Card Grid, Testimonial, CTA Banner, Stats) with clear deployment rules and accessibility considerations.

Quick Start

Apply this standard before starting any page HTML work.

Frequently Asked Questions about etkm-webpage-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build self-contained HTML for WordPress Raw HTML blocks?

To build self-contained HTML for WordPress Raw HTML blocks, you create production-grade pages with inline CSS and no external stylesheets or JS, ensuring reliable rendering across multiple domains without relying on external theme assets.

Why does my WordPress page layout break at 768px and how do I enforce a strict breakpoint?

To enforce a strict 768px responsive breakpoint, apply standardized responsive patterns that adjust hero specs, typography, and modular sections specifically for tablet and mobile viewports within your self-contained HTML structure.

What's the best way to standardize brand consistency across multiple WordPress domains?

The best way to standardize brand consistency across multiple WordPress domains is to apply a strict color palette, grayscale hero imagery, and standardized Google Font loading directly within self-contained HTML page templates.

How do I use inline CSS to ensure reliable rendering for WordPress landing pages?

You use inline CSS to ensure reliable rendering for WordPress landing pages by embedding all styling rules directly in the HTML document, eliminating external stylesheet dependencies that often break inside Raw HTML blocks.

What modular section patterns do I need for production-grade HTML pages?

For production-grade HTML pages, you need modular section patterns including Hero, Split Content, Card Grid, Testimonial, CTA Banner, and Stats, which feature clear deployment rules and accessibility considerations for structured page assembly.

Why does grayscale hero imagery matter for WordPress site rebuilds?

Grayscale hero imagery matters for WordPress site rebuilds because it enforces strict brand consistency and visual standardization across multiple domains, ensuring a uniform aesthetic within your self-contained HTML templates.