Elbutschitos HTML Publisher

Elbutschitos HTML Publisher generates a fully static HTML export of your WordPress posts and pages, using WordPress purely as a headless content source, and pushes the result to a deployment target of your choice: Netlify or any standard SFTP host.

Full tutorial: htmlpublisher.ub-internetberatung.de — step-by-step setup, template markers, navigation, forms, URL rewriting, HTML cleanup rules, and troubleshooting.

Core features

• Template-driven generation – use your own HTML template with simple ###placeholder### markers (title, content, date, author, and any custom field via a flexible field-mapping syntax). Assign a different template per post or page when needed.
• Two deployment targets – upload over SFTP (password or private key authentication) to any web host, or deploy straight to Netlify via its API. Batch transfer with progress feedback, or push a single page at a time from the post editor.
• Automatic URL rewriting – internal links and media URLs are automatically rewritten to root-relative paths, with additional custom find-and-replace rules available for anything else (old domains, CDN paths, and so on).
• Working contact forms on a static site – forms keep working after export. On Netlify, forms are automatically wired up for Netlify Forms. On SFTP targets, a small bundled PHP handler emails submissions, with spam-honeypot protection and lightweight client-side validation (required fields, email format) that needs no configuration for accessibility-friendly form markup.
• Navigation from a WordPress menu – keep your designer’s existing, fully styled navigation markup and let the plugin fill it with the real menu structure from a WordPress menu (multi-level menus supported), instead of maintaining two separate navigations by hand.
• Markdown export – export all content as plain .md files with YAML front matter, optionally bundling and localizing referenced images, for use with static-site generators such as Hugo, Jekyll, or Eleventy, or for archiving in a note-taking tool.
• HTML cleanup rules – remove WordPress-only CSS classes, or rename specific layout-relevant ones to your own class names via the class mapping tool so you can restyle them yourself; strip or change arbitrary attributes via simple selector-based rules, and inject custom per-post data into the template.