Skip to main
start from cms.data anchor override from layouts end from cms.data.

Client-friendly. Developer-focused. Agents love it.

About

Backstory

Introduction

Hello world. It is I, that’s is Simchock, Mark F Simchock. I am the conductor leading the Hugo Agent Zero orchestra.

I’m also the Chief Executive Alchemist at Alchemy United. Soon I’ll be relaunching AlchemyUnited.com, using HAZ, of course. But until then, here’s where you can find me on LinkedIn: https://www.linkedin.com/in/mfsimchock/

I’ve been working on internet-focused projects for approximately 30 years. The last 15+ years have primarily revolved around WordPress / WooCommerce. I’ve also worked with Shopify, Webflow, Squarespace, and other similar platforms. Technical skills pay my bills, tho I have plenty of experience with marketing, SEO, writing content, design, UI, UX, AI, etc.

If I’m not learning something new, or trying something new… I’m not breathing.

The Pain

Over time, I got tired of the friction from seeing a relatively simple website needing a stack of plugins, numerous dev tools, a temperamental build chain, hosting invoices that occasionally someone forgets to pay, and a CMS dashboard nobody on the client side wanted to learn properly.

More and more, feature bloat became a bug, not a feature.

Can you dig it?

The breaking point came with the WordPress drama over the last couple of years. I’m not anti-WordPress per se, but I finally admitted that I needed a safe, sane and dependable alternative, at least for some projects (including my own).

The Solution

The goal was simple: Mobile-first, content-centric, a back-to-basics mindset, and yet forward-thinking.

After poking around and reviewing different options, I found Hugo [1]. While I liked many of the off-the-shelf Hugo themes, I couldn’t find one that I loved.

I created HAZ because I wanted lighter and easier, yet still robust, flexible and with growth potential. I wanted something AI-first, not to be trendy or as a crutch, but as a useful partner.

I wanted a tool I could depend on (read: no egos, no drama), that reflected the depth and breadth of my experience in web design, user experience, performance optimization, SEO, web development, and most importantly meeting clients’ business needs.

In late 2025, HAZ was born.

[1] Shout out to Micro.blog. Full disclosure: AFAIK, HAZ is not compatible with Micro.blog.

Identity Statements

Mission Statement

To craft a human-friendly but forward-thinking Hugo theme-work for developers, agencies, and projects that want to leverage AI and deliver consistent results, without conceding full control to agents.

Purpose Statement

To champion a static-site publishing tool that brings joy to clients, developers, and agents. A tool that is an alternative to the feature-bloat and “tech for tech’s sake” obsession of too many similar solutions.

Vision Statement

When a project’s needs are within HAZ’s sweet spot, HAZ wants to be considered a viable, lighter-weight and lower-cost alternative to WordPress, Webflow, Wix, Squarespace, Framer, and the like. HAZ simply wants to be in the conversation when it’s possibly the right tool for the need.

Guiding Light

The Client Test guides product decisions. When in doubt ask, “Is this as client-friendly as possible?” While we want the technology to let developers and agencies feel as little restriction as possible, we also understand it’s the clients who decide the value of the solution.

Values Statement

  1. Mobile-first — The small screen experience comes first, as does a dedication to page speed and other such metrics.

  2. KISS (Keep It Stupid Simple) — From zero required dev tooling to leaning on established standards (e.g., Simple.css, Font Awesome free version), HAZ intentionally chooses proven experiences and productivity over the latest shiny new objects.

  3. DRY (Don’t Repeat Yourself) — Emphasize reusable components and configuration over new construction. When a project spawns new components, those can be folded back into the core product’s library, and will then be available to all other projects using HAZ core.

  4. Accessibility — Make it part of the process. Always try to be mindful of the full range of needs of the wide spectrum of users on the internet.

  5. Accept appropriate compromises instead of chasing the gods of optimization, only to get a slightly rounder wheel.

  6. Robust features, calm defaults — Offer a robust range of features and settings but mitigate decision making with defaults that cover the most typical use cases. Allow defaults to be easily overridden.

  7. Let Hugo be Hugo when Hugo needs to be Hugo. HAZ is a mind-expanding supplement.

Mantra

Better to do a great job for the few than a merely good job for the many.