EN 
DE 
RU 
PT 
JA 
ES 
IT Machine Guarding
SGF Blog Reference Contract Validation
This production article validates that the SGF Blog route now follows the same section-based contract as the accepted machine-guarding reference page, with the theme owning the top title and featured image while the body stays inside sgf-content-container.
What the reference contract requires
The earlier clean sample was structurally valid, but it did not mirror the mature SGF Blog reference page closely enough. This sample uses the reference root, hero section, feature cards, table block, applications section, download section, and bottom CTA.
| Contract area | Required SGF output |
|---|---|
| Reference root | sgf-content-container with section-based SGF Blog body |
| Top shell owner | WordPress title and featured image, not body h1 |
| Body hero | section.hero.sgf-pain-box with h2, summary, figure, CTA |
| Forbidden output | No inline style, no body h1, no old fixed-width table, no unresolved slots |
Three route checks now locked to the reference
01. The body starts from the accepted SGF wrapper
The generated post content begins with sgf-content-container and uses the same hero, specs, features, applications, download, and bottom_cta sections as the supplied reference page.
02. The title and featured image stay in the theme shell
The body does not emit an h1. WordPress owns the page title and featured image above the content, matching the machine-guarding reference page instead of creating a duplicate hero system.
03. The route blocks legacy table flow and inline styling
The final HTML is checked for inline CSS, body h1 tags, unresolved placeholders, and old table-layout strings before the Live URL can be used for manual validation.
Where this Blog contract applies
- Automation cells that need guarded access before commissioning starts
- Packaging or palletizing lines where gate hardware and controls handoff must be agreed early
- Retrofit lines where field drilling and late interlock changes create schedule risk
The layout contract is deliberately about structure, not final sales copy. Product-specific content can change later, but the SGF body skeleton must stay stable.
What to confirm before future SGF Blog publishing
Before publishing a real article, the route must read Theme Lock, Template_Blog.md, and Template_Blog.slot_schema.json first; then it fills JSON slots and renders the fixed template.
Use the reference contract before content generation
This sample is the production proof candidate for SGF Blog after switching to the machine-guarding reference structure.
