-
Notifications
You must be signed in to change notification settings - Fork 31
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
Post Release Update / Future Updates and Improvements #87
Comments
Just my two cents here:
I dont have too much else to add since my frontend knowledge is very lacking but I seriously appreciate the work being put into this. Clean documentation will be massive for Stride to thrive. |
Also to add, I did recently start a tutorial project and recorded the first video a short while ago Ill post in the discord once its properly available. |
@Doprez thank you very much for your feedback 🙂
I believe sharing other options and being transparent will help to spread a word about Stride and/or as you suggested make the right decision to select a right game engine.
You are 100% right here. It is time consuming to bring another location for the discussions. I believe, we should be able to link it with our existing Stride GitHub Discussion otherwise it doesn't make sense for us :)
I found myself in the same situation and I need a better clarity what and how needs to be done when I read something new. GoDot has contributors docs in the main docs. I would just start with a simple page in our Stride website and also in Stride docs, so if happened somebody lands there for the first time, we can provide some intro as a Stride contributor and direct further to relevant docs. I am planning to review/update our contributors docs (https://github.com/stride3d/stride/wiki) and re-structure it so it looks maybe like this https://github.com/VaclavElias/stride-website-next/wiki, eventually maybe moving to Stride Docs if needed. Whatever will be easier to maintain.
Yes, we have a working prototype here https://github.com/VaclavElias/stride-website-next/wiki, I am planning to replicate it to Stride Docs wiki, and Stride wiki 😀
Thank you. As much as I would like to dig in the Stride code base, my strengths are in the web development (not design!) and the Stride website and docs and wikis really need some serious content contributions and updates 🤣 |
I hope it goes well. I would like to do some tutorials in the future as well. Aggror made serious tutorial contributions and they are critical and essential for the new Striders. So any such a content is welcome. I hope he will be able to continue other such tutorials in the future. Not sure how far you want to take it with the tutorials. There could be an option that if you do some series, and you would like it to be an official Stride tutorial series, we could check with the Stride maintainers as the new open collective project and allocate some budget for that https://opencollective.com/stride3d/projects/stride-intermediate-tutorials#category-BUDGET Otherwise, we could promote it in the Stride Blog Post 🙂 |
Aggrors tutorials were a huge help when I started, they were awesome. Im not to sure either I know the current tutorial project is just going to be a basic horror game that will touch on game loop, animation, triggers, AI and navigation. The goal is just to get a base project down for others to see a "complete" game made with Stride that is open source. |
Review, and separate to individual issues:
Web - Split Tags to 2 columns in the /tags pageediton
https://github.com/stride3d/stride-website/blob/staging-next/wiki/Installation.mdThe text was updated successfully, but these errors were encountered: