I think the new compiler is getting close enough that we should set up 2025.roc-lang.org as a clone of the current site, so we can start making breaking changes to the main roc-lang.org (even if it's just changing documentation and tutorials and stuff to "Coming soon!" since we don't have it updated for the new compiler) while still having an easily accessible version of the current site for folks like @Niclas Ahden who have active projects using the Rust-based compiler - thoughts?
I'm happy to start pulling content together and leaving placeholders in places etc.
I'm not sure about the CI and infra though.
We could make 2026.roc-lang.org instead and use that for all the new stuff. I feel like it's much more acceptable for that to look like a work in progress instead of the default site.
I think the site is mainly for newcomers, and for them, it'd be easier if roc-lang.org was for the Zig compiler, even if it's in a rough state. It'd save people cycles by not learning about the Rust compiler, then learning about the Zig compiler and getting a bit confused. The rough state of the site could be viewed as an honest signal of what to expect right now. It'd probably lead to questions which help identify what's most important to work on, while also helping people to try the new Roc (which is good for everyone!)
I strongly agree with Niclas Ahden . It's not like the Rust compiler was super stable. I went down the rabbit hole of playing with the old compiler and ran into Rust panics. I don't regret it in my particular case, because I had been lurking here long enough to know what I was getting into, and even getting 200 lines of Roc written was worthwhile to me.
But I think other newbies would benefit from just looking forward to Zig.
Good points! I would still like to set up http://2026.roc-lang.org/ for a short term, we don't have live previews for pull requests setup (the cloudflare-github integration is very opaque). We at least want to make sure all links work etc. and not just throw something out there in production.
sounds good to me!
@Anton I can start pulling content together for 2026.roc-lang.org -- do you have a preference for where I push that? I assume it would be somewhere in https://github.com/roc-lang/www.roc-lang.org?
I have it almost done at https://github.com/roc-lang/www.roc-lang.org/pull/54, I'm just finishing up some improvements to the docs generation.
Oh cool :smiley:
Just wanted to say a huge thank you to @Anton , @Luke Boswell , @Richard Feldman!!! I've been following ROC weekly for over a year now waiting for the Zig compiler, and incredibly excited for 0.1.0 release with the updated website. The design aspects around static dispatch and full type inference are revolutionary and make it feel like a scripting language with all the type safety and runtime optimization automatically included. I think ROC will get extremely large adoption for production products once the runtime crashes, debug support, and LSP support are ironed out. Looking forward to all the cool things built using ROC in the future!!
Instead of naming it http://2025.roc-lang.org/, would http://alpha4.roc-lang.org/ be a better name?
Yes, or perhaps legacy to avoid confusion for new people who don’t know that alpha-4 is the old compiler? Either is fine to me, just spitballing
I currently set it to https://alpha4.roc-lang.org it's easy to change if we want to.
No desire from my side. Thanks for setting it up! :)
The updated website preview is up at https://new-compiler-website-2026-roc.cc02oj5kr.workers.dev
Let me know if you see any issues.
Note that the goal of the update was just to use the new Roc (zig compiler) everywhere and remove/update outdated information.
Last updated: May 01 2026 at 12:45 UTC