-
Notifications
You must be signed in to change notification settings - Fork 8
Add a 2025 vision post #343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This tries to tie together the product that we've been building, and explains it to the community. I'm not 100% sure this is the best format for this, but I think it's important that we have this written down somewhere, and tried to do a reasonable good first version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good marketing post 💯
In my opinion, it does a better job as a "2024 recap" than as "2025 vision", since it explains in deep what we've done in 2024 but doesn't go too much in deep on what's coming on on 2025 and how we are going to reach those goals.
The only thing that's briefly mentioned for 2025 is the "Command Pallete". We could also mention the "File Tree Diff" feature somehow. We are also working on "Editable Versions" as another big feature.
On the other hand, I feel that in the whole post it says that everything is expandable and/or customizable (e.g. build process, addons, etc) and that's not 100% true. In particular for addons. I think that 2025 will be the year where addons customization will be possible, and that's probably something to highlight as a goal instead of as something currently possible.
Well, the goal is to share the vision, which requires explaining what we've done, and then the product vision going forward. The recap is the "what we've done" part, and the customization is the "going forward" part. The goal is to share the high-level goals and vision for the product, which I think requires both. I didn't want to dive into specific features we're planning to work on in 2025 necessarily, but just share the "we now support all tools" vision, and the goal of good defaults with customization. |
Planning to merge this tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, just some minor notes
Co-authored-by: Anthony <[email protected]>
This tries to tie together the product that we've been building,
and explains it to the community.
I'm not 100% sure this is the best format for this,
but I think it's important that we have this written down somewhere,
and tried to do a reasonable good first version.
Things I wished we had in this post:
build.jobs.build
support, which I know isn't fully done📚 Documentation preview 📚: https://readthedocs-about--343.org.readthedocs.build/