Quick note from a single operator. Loved the tool enough to ship an operator-onboarding page for it this morning. Then tried to actually use it for real production work and got held up at the very first step. Sharing the .dgmo source for what I would have built — and asking for a pointer to get past the stuck spot.
If you're Demian, another Diagrammo user, or anyone who knows the click I'm missing — text or DM PJ. I'd love to actually render this and ship the screenshot as the second SideGuy × Diagrammo proof point.
📲 Text PJ · 858-461-8054 DM on LinkedIn →— PJ · SideGuy Solutions · Encinitas · The operator-translation layer for tools like Diagrammo
Don't see what you were looking for?
Text PJ a sentence about what you actually need — I'll build you a free custom shareable on the house. No email, no funnel, no SOW.
📲 Text PJ — free shareable
What happened
This morning I shipped a 30-second operator-onboarding page for Diagrammo as the first move in the SideGuy "smash-back" pattern — when a builder ships something gorgeous, you don't pitch them, you USE it and ship something better than the README on top.
Step two was supposed to be: build my own real production diagram (the SideGuy factory map) IN Diagrammo and ship that as a second proof point. The plan was about 30 seconds of paste-and-render.
I got stuck before the diagram. Couldn't figure out how to make a new file. Probably user error — but it was the kind of friction where 10 minutes pass and you're still on step one. Eventually shifted to the meta-move you're reading: ship the .dgmo source on my domain and ask the builder for a pointer.
Here's the .dgmo I was trying to render
The actual factory map for SideGuy Solutions — capture, generate, publish, distribute, convert, compound — plus the three background cron agents that ship while I sleep. Paste this into a fresh Diagrammo file and the diagram should render in 30 seconds (which is the whole point of diagram-as-code):
Why I'm shipping this as a public page (instead of just DMing)
Two reasons. One: shareables are designed for exactly this — substantive peer-to-peer asks live longer as a permanent URL than as a buried DM. Two: if other operators are hitting the same friction, this page becomes the place they land when they Google it. Compounds for both sides.
Public-by-default is the SideGuy pattern. Private DMs die in inboxes; URLs persist.