Hi Serverless team,
Your current contribution page invites guest contributors to email, open an issue, or submit a pull request. The published contributor email returned an address-not-found response, so I’m using the issue route to confirm editorial fit before preparing a complete PR.
Proposed original article
Your deploy button is an external API: testing monorepo contracts from the outside
The article would use a reproducible failure from the open-source elm.chat project: its production deployment worked, but a new user following the public Deploy to Cloudflare button reached No Wrangler configuration detected because the deploy contract was hidden inside a workspace.
The article would focus on reusable serverless engineering lessons:
- why maintainer-successful deployments can conceal a broken public setup path;
- how to expose a minimal build/deploy contract at a monorepo’s target root;
- when a public template should intentionally omit production-only bindings;
- how to test root/workspace parity in CI; and
- an outside-in checklist for testing one-click deployment as a stranger.
The implementation and repair are public in elm.chat PR #89. A shorter field note already exists at elm.chat; the proposed Serverless article would be an original expansion written for this audience, not a duplicate submission.
Author and disclosure
I’m Shawn Bure, an AI professional and technologist with decades of operating and software experience. I lead Workrr AI and Workrr One, and I created elm.chat.
AI tools substantially assisted the project implementation and preliminary drafting under my direction. I review the code, tests, sources, and claims and remain responsible for the work. elm.chat is early-stage, has not had an independent security audit, and has unfinished message-authentication and replay-protection work. The proposed article would stay narrowly focused on the verified deployment failure and repair, without presenting the project as an audited security product.
If this angle fits the current editorial calendar, I’ll prepare the complete article, author JSON, and required 1200 × 600 header image in a draft PR following the repository’s writer guide. Is the guest-contribution workflow still active, and would this topic be useful to your readers?
Hi Serverless team,
Your current contribution page invites guest contributors to email, open an issue, or submit a pull request. The published contributor email returned an address-not-found response, so I’m using the issue route to confirm editorial fit before preparing a complete PR.
Proposed original article
Your deploy button is an external API: testing monorepo contracts from the outside
The article would use a reproducible failure from the open-source elm.chat project: its production deployment worked, but a new user following the public Deploy to Cloudflare button reached No Wrangler configuration detected because the deploy contract was hidden inside a workspace.
The article would focus on reusable serverless engineering lessons:
The implementation and repair are public in elm.chat PR #89. A shorter field note already exists at elm.chat; the proposed Serverless article would be an original expansion written for this audience, not a duplicate submission.
Author and disclosure
I’m Shawn Bure, an AI professional and technologist with decades of operating and software experience. I lead Workrr AI and Workrr One, and I created elm.chat.
AI tools substantially assisted the project implementation and preliminary drafting under my direction. I review the code, tests, sources, and claims and remain responsible for the work. elm.chat is early-stage, has not had an independent security audit, and has unfinished message-authentication and replay-protection work. The proposed article would stay narrowly focused on the verified deployment failure and repair, without presenting the project as an audited security product.
If this angle fits the current editorial calendar, I’ll prepare the complete article, author JSON, and required 1200 × 600 header image in a draft PR following the repository’s writer guide. Is the guest-contribution workflow still active, and would this topic be useful to your readers?