DEV.to
@workbehindtheluck
Long-form teaching library and searchable proof. Articles are canonical on dev.to; the site's /blog mirrors them via the API. Keep DEV for essays and how-we-built-it posts — not local event logistics.
Download all DEV.to assets (.zip) ↓Handle limit 30 chars · backups: thewbtl · workbehindluck
01 — Set up, in order
- 01Mat's personal DEV.to account (his own name) is the author. Paste the personal bio; website https://workbehindtheluck.com; location Pampanga.
- 02Settings → Organization → Create: name “The Work Behind the Luck”, username workbehindtheluck, logo devto/profile-1000.png, website, summary (≤250), tag line (≤60), proof (≤1,500), brand colour #f2a33c, CTA button + body (all text in Paste these).
- 03Publish the introductory article (Launch page) under the organization: cover devto/article-cover-1000x420.png, tags community · career · ai · webdev, footer image devto/footer-cta-1000x250.png, author bio at the end.
- 04Invite co-authors by username or the org secret code (Settings → Organization). Set DEVTO_USERNAME in Vercel so /blog lists the articles.
02 — Paste these
Profile bio179/200179/200. This is Mat's personal DEV.to profile.
I lead a platform engineering team and interview a lot of engineers. Founder of The Work Behind the Luck: weekly Build Nights in Pampanga + online. I write about finishing things.
Organization summary213/250
A practical community for learning, building, and creating opportunity. Weekly Build Nights in Pampanga + online: one useful lesson, an hour of guided work on your project, demos, and a next step before you leave.
Organization About743 charsAbout 115 words.
The Work Behind the Luck is a practical community for learning, building, and creating opportunity. Build Nights run weekly in Pampanga, with online access; developers, students, career changers, and builders learn one useful skill, work on something real, and leave with a next step. This organization publishes what comes out of the room: lessons from Build Nights, build-in-public updates on the community site (Next.js, Tailwind, Prisma, tRPC), member project writeups, and honest posts about building with AI without handing over your judgment. Expect tradeoffs, iterations, and what went wrong, not hype. People may call the outcome luck. We focus on the work behind it. Reserve a seat at the next Build Night at workbehindtheluck.com.
Brand color7 charsAmber. Enter in the organization settings color field.
#f2a33c
Organization tag line59/60
The work people don't see. The opportunities they later do.
Organization name24/5024/50. Username: workbehindtheluck (17, within 2 to 30).
The Work Behind the Luck
Organization proof (required: your association with the org)380/1500
I'm Mat Mozer, founder of The Work Behind the Luck, a practical community with weekly Build Nights in Pampanga, Philippines, plus online access. I own and operate workbehindtheluck.com (see workbehindtheluck.com/about, which names me as founder) and my DEV.to account email is on that domain. I run the events, write the community's articles, and will be the organization's admin.
Organization CTA button text18/20
Join a Build Night
Organization CTA body (markdown)208/256
Weekly Build Nights in Pampanga + online. One practical lesson, an hour of guided work on your project, a next step before you leave. Beginners welcome. [Reserve a seat](https://workbehindtheluck.com/events).
Canonical URL rule242 chars
DEV.to is the original for the community's articles, so leave canonical_url empty in the front matter. Only set canonical_url (pointing at the workbehindtheluck.com/blog URL) when cross-posting an article that was published on the site first.
03 — Pinned / welcome
Organization page pinned line132 charsUse as the organization's pinned article blurb or the first line of the org profile.
Start with "Why I'm building The Work Behind the Luck", then come to a Build Night. Pampanga + online, weekly. workbehindtheluck.com
04 — Upload these
DEV.to article cover (navy)Download ↓
1000 × 420 · PNGFields: title, kicker, series. DEV shows covers at 1000×420.
DEV.to article cover (paper)Download ↓
1000 × 420 · PNGLight variant for white DEV feeds. Amber-on-light is #b06d10 for contrast.
DEV.to article footer CTADownload ↓
1000 × 250 · PNGDrop at the end of every article: canonical note + Build Night invite.
Screenshot frame (tutorials / DEV.to)Download ↓
1600 × 1000 · PNGNavy frame with window chrome. Drop the real screenshot into the slot; watermark stays bottom-right.
Diagram style — 5-pillar flowDownload ↓
1200 × 675 · PNGReference for diagrams in articles: hairline boxes, amber arrows, Archivo labels. Reuse the look, not the content.05 — Specs & limits
| Item | Size / limit | Notes |
|---|---|---|
| Organization username | 2–30 chars | Shares one namespace with user usernames — claim workbehindtheluck as the org, not as a personal handle (available as of Aug 2026). |
| Organization name / summary / tag line | 50 · 250 · 60 chars | Summary shows under the org name on every post. |
| Organization proof | 1,500 chars | Required on creation: text proving you're associated (e.g. you own the domain). |
| Organization CTA | button 20 · body 256 chars | Optional call-to-action shown on every org post — use it for Build Night. |
| Logo / profile image | square, ≤ 8 MB (upload 1000²) | Rendered small and rounded. Brand colour #f2a33c. |
| Personal bio | 200 chars | Mat's own profile (the author). Location/website 100 chars each. |
| Article cover | 1000 × 420 (100:42) | Dark cover for the article page; the light variant reads better in the white feed list. |
| Title / tags | 128 chars · 4 tags | e.g. community, career, ai, webdev, beginners, productivity. |
| canonical_url | front matter | Leave empty — dev.to is the original for our articles; the site points its copy back here. Set it only when cross-posting something that first appeared on workbehindtheluck.com. |
06 — Post formats that run here