hangarplatform.dev · Review · Site feedback

What two reviews said about this site, and what I did about it

The day the site went live I asked Grok and ChatGPT what they thought of it. Both were kind, and both made the same three criticisms: it's dense, it's written for peers more than for hiring managers, and it tells more than it shows. Claude checked every point against the live site and the repo. Here's what I did with them.

Review September 27, 2026Reviewers Grok and ChatGPT, checked by Claude against the live site and repoScope the website only, not Hangar's architecture
Done · eight changes live by Sep 28, 2026

Show more, explain the jargon, and stay honest about what's built.

I took eight of the eleven suggestions, kept one as optional and declined two. The ones I declined would have made the site weaker for the people it's written for, or less honest.

Eleven suggestions, sorted

Eleven suggestions, sortedTwo AI reviews plus one issue found while checking produced eleven items: four to do first and four next, all live by Sep 28, 2026; one optional; two declined.Two reviews+ one found checkingDo first4 itemsNext4 itemsOptional1 itemDeclined2 itemsLIVE BY SEP 28, 2026Eight shipped in a day.Three I kept to myself.
Figure 1Eleven items, four piles. Everything in Do first and Next shipped the next day.

Do first

1. Take the home-lab cluster names out of the published diagrams

Done

Found while checking
Two Autopilot diagrams and the brand page still named the lab clusters. The fix went into the generators, not the built site, and they now say "dev cluster" and "prod cluster".

2. Add a tech-stack view

Done · /stack/

ChatGPT, Grok
ChatGPT had to list the tools itself and draw its own stack diagram, which told me a page was missing. Three mockups later, it became the stack as decisions: every tool, what I chose it over, and why.

3. Show the running product on the home page

Done · home page

ChatGPT
The Tower walkthrough was hidden behind a card on /tower/. It now plays just under the hero, so "is this real?" gets an answer in ten seconds.

4. Bring the track record onto the home page

Done, in part

ChatGPT, partly agreed
A short strip of facts from the About page went on the home page. I declined the other half, publishing DORA or MTTR numbers from past jobs: I don't have numbers I can share, and estimates would break the honesty the site is built on.

Next

5. Record a "zero to running" walkthrough

Done · /run/

ChatGPT
The most convincing thing I could add. Two services went from nothing to production on camera, one in the terminal and one in Tower, and the run found four real platform bugs. See Zero to running.

6. Write about what the stack costs

Done · essay

ChatGPT, Grok
The sharpest critique in either review, and exactly what the site is for. It became the first Architecture essay, what Hangar costs, and where Crossplane stops.

7. Explain the jargon in plain words

Done · /glossary/

ChatGPT, partly agreed
I didn't simplify the pages, because the depth is the point. Instead there's a glossary and a short explainer on the first mention of each term.

8. Mark Autopilot's maturity on the product cards

Done · badges

ChatGPT, partly agreed
Every product card now carries a status, so Autopilot reads "Early: core built, runtime proposed" instead of looking as finished as Glidepath.

Optional, or declined

9. A 30-second path for first-time visitors

Optional

Grok
"Start here" already did this, just too far down. Fine to move up, not worth a new section.

10. Move more of the deep content onto the site

Declined

Grok
Mostly done already: the docs sync from every repo. ADRs stay linked to GitHub, because the source of truth belongs next to the code.

11. Rewrite the site for executives

Declined

ChatGPT
The site is here to show the work and share opinions, and peers are the people who can judge both. Items 3 and 4 give a hiring manager what they need in ten seconds.

What the reviews got wrong