Add blog post: How We Designed Modelplane#31
Merged
bassam merged 1 commit intoJul 15, 2026
Conversation
dennis-upbound
marked this pull request as ready for review
July 14, 2026 22:14
Contributor
|
@dennis-upbound please add a bio and photo, and a cover image for the blog. |
dennis-upbound
force-pushed
the
blog-how-we-designed-modelplane
branch
from
July 15, 2026 14:59
f35121b to
0a6011c
Compare
dennis-upbound
force-pushed
the
blog-how-we-designed-modelplane
branch
from
July 15, 2026 15:02
0a6011c to
9249c8c
Compare
bassam
approved these changes
Jul 15, 2026
The Crossplane blog covers how Modelplane is built; readers still lack a post on why the developer-facing API is shaped the way it is. This adds "Any Engine, Any Topology, Any Infrastructure: How We Designed Modelplane", walking through the two-role API, the decision to abstract around engines rather than over them, and how one shape covers any engine, topology, and infrastructure, with a section on what v0.1's scheduler does and does not yet do. Validated with npm run validate-posts and npm run build (both pass). Signed-off-by: Dennis Ramdass <dennis@upbound.io>
dennis-upbound
force-pushed
the
blog-how-we-designed-modelplane
branch
from
July 15, 2026 16:31
9249c8c to
9a53612
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a blog post: "Any Engine, Any Topology, Any Infrastructure: How We Designed Modelplane."
The Crossplane blog (Building Modelplane) covers how Modelplane is built. This post covers why the developer-facing API is shaped the way it is: the two-role API (platform vs. developer), the decision to abstract around engines rather than over them, and how one shape covers any engine, any topology, and any infrastructure. It closes with what v0.1's scheduler does and does not yet do.
New file:
content/blog/2026-07-14-how-we-designed-modelplane/index.mdxChecks
npm run validate-posts— passes (2 posts, all good)npm run build— passes; generates/blog/how-we-designed-modelplane, the author page, and tag pagesOpen decisions (need a call before merge)
github.com/negz) as a placeholder — he designed the API and wrote the companion Crossplane post. Change the author (or add title/bio/avatar/socials, as the existing post has) before merge.2026-07-14. Adjust to the intended publish date.draft/pinned: currentlydraft: false,pinned: false. Opened as a draft PR so the Vercel preview is reviewable without publishing.https://modelplane.ai. If there's a canonical getting-started URL (e.g.docs.modelplane.ai/getting-started/), swap it in.Notes
ModelDeploymentYAML uses the flatspec.enginesshape that shipped in v0.1. If thespec.template.spec.enginesrestructure lands before this publishes, the two YAML blocks need updating to match.