'Wasp 1.0 is coming' blog post - #4767
Conversation
| @@ -0,0 +1,119 @@ | |||
| --- | |||
| title: "After 5 years in Beta, Wasp 1.0 is coming" | |||
There was a problem hiding this comment.
This title, or do we do just "Wasp 1.0 is coming"?
Just "Wasp 1.0 is coming" is more powerful / elegant, and makes more sense on our blog, while "After 5 years in Beta, Wasp 1.0 is coming" is more attractive but reads a bit like written on somebodies else page and is less elegant.
There was a problem hiding this comment.
Of the two options I'd go with just "Wasp 1.0 is coming". Another option could be "Time to get excited for Wasp 1.0" or, simply "Get excited for Wasp 1.0"
Martinsos
changed the title
Deploying wasp-docs-on-main with
|
| Latest commit: |
ceab9a4
|
| Status: | 🚫 Build failed. |
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
There was a problem hiding this comment.
ℹ️ Three publication rough edges are called out inline.
Reviewed changes in the initial ceab9a4 draft, including the article's render contract, frontmatter, internal links, cited public roadmap, and banner asset.
- Wasp 1.0 announcement — Adds the rationale, roadmap categories, feature plans, and release approach for the move out of beta.
- Roadmap references — Links the announcement to the public Wasp roadmap, supporting epics, and earlier TypeScript Spec and Full Stack Modules posts.
- Publication asset — Adds the WebP banner used by both the article body and social metadata.
GPT Sol ｜ 𝕏
| tags: [wasp, update] | ||
| keywords: ["wasp 1.0", "wasp roadmap", "full-stack framework", "full stack modules", "react node prisma framework"] |
There was a problem hiding this comment.
The blog frontmatter contract requires 3–6 tags and at least 10 keywords, but this draft has two and five. Please expand both lists before publication so this announcement meets the repository's SEO/GEO requirements.
|
|
||
| import { ImgWithCaption } from './components/ImgWithCaption'; | ||
|
|
||
| <ImgWithCaption |
There was a problem hiding this comment.
This new file currently fails npm exec -- prettier --check blog/2026-08-26-wasp-1-0.mdx. Please run Prettier on it before merging.
|
|
||
| ETA: ~6 months (warning: this is developers estimating, which means we added buffer, doubled and tripled everything, and will still likely miss it). | ||
|
|
||
| Even though still young in framework-years, Wasp has been around for some time now (>5y), with [over 100 releases](https://github.com/wasp-lang/wasp/releases), [user stories](/#showcases) ranging from startups to Fortune 500 companies, $5M raised so far in investments, and a growing team of currently 8 people behind it plus all the awesome people from our community ([waspeteers](/#waspeteers)). |
There was a problem hiding this comment.
The current landing page does not register a waspeteers anchor, so this link cannot navigate readers to the community section. Please use the existing /#testimonials anchor or link directly to Discord.
There was a problem hiding this comment.
Its about to be merged so I was forwad looking, it's ok we will leave it.
GitHub Actions
Inactive
@wasp.sh/spec
@wasp.sh/wasp-cli
@wasp.sh/wasp-cli-darwin-arm64-unknown
@wasp.sh/wasp-cli-darwin-x64-unknown
@wasp.sh/wasp-cli-linux-arm64-glibc
@wasp.sh/wasp-cli-linux-x64-glibc
@wasp.sh/wasp-cli-linux-x64-musl
commit: |
Tobbe
left a comment
Tobbe
left a comment
There was a problem hiding this comment.
Great post! Very exciting 😄
Just commented on a few tiny details I stumbled upon while reading through the text. Feel free to totally ignore them all!
| @@ -0,0 +1,119 @@ | |||
| --- | |||
| title: "After 5 years in Beta, Wasp 1.0 is coming" | |||
There was a problem hiding this comment.
Of the two options I'd go with just "Wasp 1.0 is coming". Another option could be "Time to get excited for Wasp 1.0" or, simply "Get excited for Wasp 1.0"
| - We found the right shape for [the "Spec"](/blog/2026/06/15/wasp-typescript-spec) without giving up on our vision (this was a big one!). | ||
| - We developed a good intuition for how to balance managed experience with flexibility. | ||
| - We collected a lot of feedback on all the major features of Wasp (Auth, RPC, Jobs, Routing, API, Entities, Deployment, etc.) and know what people care about and need, and how to get there. | ||
| - We got seriously into developing the long-awaited (by us) [Full Stack Modules](/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module), the crown of the "fullstackiest" experience we are aiming for, and are confident we can deliver it. |
There was a problem hiding this comment.
| - We got seriously into developing the long-awaited (by us) [Full Stack Modules](/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module), the crown of the "fullstackiest" experience we are aiming for, and are confident we can deliver it. | |
| - We got seriously into developing the long-awaited (by us) [Full Stack Modules](/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module), the crown of the "fullstackiest" experience we are aiming for, and we are confident we can deliver it. |
It works without that extra "we", but I feel like it reads a little easier with it there
|
|
||
| FSMs might not sound like a 1.0 thing off the bat, but we see them becoming so integral and transformative to how Wasp apps will be built that we want to have it, and its effects on Wasp's API, in before 1.0. | ||
|
|
||
| By the way, we are open to ideas for a better name since LLMs keep thinking we are talking about Finite State Machines. |
2 participants
No description provided.