The Overview page now shows an alphabetized list of all content, with tabs to filter for the type of content that you want (e.g., classes, data types, enums).
We’ve also updated the look and feel of individual Engine API Reference docs (example), including a consolidated summary table at the top, better formatting for deprecated items, and improved spacing and readability.
Notice how there’s just a box, and the type is defined below for essentially no reason when that could be communicated through the icon instead. The padding is also a bit too much
This is great! But it’d be awesome if you addressed the community on the very real possibility that AI verifciation will make it “easier” for predators to “navigate and scan” for children on your platform.
This team who made the docs update unfortunately has little control over that. Although we could bring the conversation back to the original announcements and maybe if we reply enough times they will listen.
Our goal as a community is to get the most recent post to 4k replies, and if they don’t respond when we get to 4k replies then the community will officially declare chaos.
Well the company seems to already be ok with making the platform’s safety even worse, so we should just declare it now. They haven’t shown that they’re willing to address the bigged red flag of this update that jeoprodizes it’s entire point.
If developers truly care about keeping the platform alive then the message should be spread everywhere. All this update does in terms of preventing predators is giving countries more reasons to ban the platform.
Are there any plans to improving searching next? It’s incredibly absurd that you have to know exactly the name of the page you want to go to and not make any typos in order for it to actually show in results, a singular letter difference should not result in completely irrelevant results being shown.
Yes because the people working on the documentation site have a lot of control over the safety issues.
Go send your feedback on the threads that are actually on the topic and stop replying with this to unrelated posts. (this is to everyone who’s doing this)
This rework is amazing, while the send feedback button is a welcome change, why was the API Reference made read only on the GitHub repo?
hi, i think the layout is cool, but the body paragraphs are harder to read than the old documentation. i think the blue words from the old API documentation was so much more suitable for readers than the underlined words of the current one.
