Hi Babylon team,
I know you guys have redone the site a few times (based on what I’ve seen in the YouTube videos), but it’s still not easy to use. And I really do appreciate all the hardwork that you guys are putting into Babylon, but I need to be critical for a moment.
If the Babylon team hadn’t rewrote the code with Typescript, then I probably would not have taken a closer look. And it’s definitely the website. I will often visit websites, and if they don’t sell me in the first 30 seconds then I leave the site. It’s not on purpose, it’s just how my brain is wired. I probably visited the Babylon site 15 times before I actually even got interested enough to dig deeper.
These things actually drove me away…
The dark blue, orange, and gray color scheme is not attractive. The dark blue really bothers me. The header should be a lighter orange, or white, or black. And the grays need to be different too. Might seem silly, but color schemes really play a factor in me wanting to use software.
I can’t return to the main page (https://www.babylonjs.com) from the docs (https://doc.babylonjs.com) or the forum (https://forum.babylonjs.com). It drives me nuts, because it’s naturally how people navigate back to the main page. Even if they are under different sub-domains, the expectation for the user is to go back to the main page when they click on the Babylon.js logo.
The docs (https://doc.babylonjs.com) are not well organized. When a developer visits the documentation page they want to see the API. Three.js organizes this much better (three.js docs). This is how I would structure the documentation page:
- Getting started: simple instructions on how to npm install, and import the package. No full blown tutorial, because the user isn’t ready for that adventure yet.
- Animations (topic)
- Audio (topic)
- Behaviors (topic)
- Basically the topics under “Diving Deeper” are the reason I’m even visiting the documentation. The link that says “API” is nice too, but I need the API grouped into topics like “Diving Deeper” does, so I can learn why the API methods exist in the first place.
- The current “Getting Started”, “Guided Learning” sections, and “Playground search”, are all nice - but I’m not ready to begin building an entire world when I don’t even understand the basics. These are good references for when I need examples when I get stuck. But I don’t really spend my time on tutorials, because it’s often not something that I want to build.
- The “Getting Started”, “Guided Learning”, “Playground Search”, “Tools and Resources” should all be under a section called tutorials (or playground).
- The “Utility Functions” under “Tools and Resources” should be grouped with the topics to which they relate (animations, audio, meshes, etc).
- The “What’s New” section is a bug change list. That does not need to be in documentation, and can instead live on the GitHub page.
- Most the “Extensions” should be apart of “Getting Started” (not the tutorial version, but the one I’m recommending), importers and exporters are basic needs during the bootstrapping of the system.
- Sections under “Extensions” like… “Tree Generators”, “Mesh Writer”, “Dynamic Terrains” should actually be grouped with the “Diving Deeper” topics.
- The hamburger menu on the main page, doesn’t even open when I click on it half the time (might be because I use Safari, but that shouldn’t matter - should be basic HTML). Not sure why the most important links are collapsed in the first place.
Likewise the topics on this menu are also oddly arranged. “Tools”, “Get”, “Release Notes”, “Learn” all provide redundant links to the docs. And then there are multiple links to what is clearly marketing material “Ecommerce”, “Games”, etc. which could all be grouped together under a marketing section.
Anyway, don’t mean to be critical. But thought the feedback might help.