Publish the Modelplane v0.2 announcement post#33
Merged
Conversation
Flip the post from draft to published and pin it to the top of the blog. It was merged as a draft so it could be reviewed on preview; this makes it live on the production site. No content changes. Signed-off-by: Bassam Tabbara <bassam@upbound.io>
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
1 participant
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 and why
Publish the Modelplane v0.2 announcement. The post was merged as a draft (hidden on
production) so it could be reviewed on preview. This flips it live:
draft: falseandpinned: true, so it renders on modelplane.ai and pins to the top of/bloglike thelaunch announcement. No content changes.
Checklist
npm run lintnpm run buildlocally.next lintonly offers to create an ESLint config (none exists in the repo yet);npm run buildpasses and now emits/blog/modelplane-v0-2under a production build.npm run validate-posts(changed blog content) — passes.git commit -s.