Roku must have never heard the phrase "Too many cooks spoil the soup/broth!"
They don't understand the damage they are doing to their brand. They are hurting themselves by damaging their developers relations. They need to put their best foot forward and instead they always place their foot awkwardly and stumble around clumsily. It makes developers weary when the docs we rely on are played with in this manner. Roku are you drunk? A little hair of the dog?
It is like Roku is saying "YEP WE HATE DEVELOPERS F U ALL!" .. Is that what this is Roku? Do you hate us? Can you stop being so penny smart and pound foolish? Can you undo what has been done? It is really annoying when companies mistake horrible things as better. Is this the future? Is Roku even listening? Do they even care? Will they even respond? Do they have souls?Once this transition is complete, we will announce the migration to the new site more broadly through our standard communication channels and promptly give the community a big middle finger. Features — Includes high-level platform feature overviews, bridging the gap between business and technical documentation. If traditional SDK documentation answers the “how,” the documentation in the Features section will answer the “what and why.”
Who asked for the "What and Why" to be put with the "How"? Why was this done. Was it to make it harder to read how to develop because now it is mixed with irrelevant babbling too? This is distracting when trying to code having to read around clutter. Rethink this decision.Developer
— Longtime Roku developers can think of this as synonymous with our old “SDK Docs.” This section includes getting started materials, technical implementation guides, troubleshooting tutorials, etc.
Yeah you might be wishing you had done less as your Longtime Roku developers will see this change as detrimental just as I have. You basically slap them in the face and tell them to like it or lump it. Thanks.
Whoever at Roku thought it would be smart to mess with things should've taken greater care. At the moment it is clumsy, awkward, and harder to navigate for developers than before. Way to go Roku. Slowing down developers and making them hate working with you helps your bottom line.
Side Note: Love the tiny font used on the side bar. Love the fact the font used is also thin. This makes it hard to read on the white background the page uses. Overall a nice suprise to see you can barely make anything out on that sidebar. The minimal use of Roku purple is also nice. Now it is hard to tell is this even a Roku website anymore? Notice on these forums the use of the purple banner with Roku proudly displayed at the top. Now contrast that with these new developer/document pages. Why it is white background with purple text on the header? Why isn't this a purple background with white text, like literally, seen everywhere else? The lack of purple clearly contrasts against Anthony Wood's (Roku CEO) philosophy as he proudly wears the colors. This page and its poor use of that color. Way to go. It now is harder to read, requires squinting and concentration to focus, and overall makes what was once an easy task several shades harder. A win/lose for all. Overall it is one step foward and five steps back.
Take cues from this: http://devtools.web.roku.com
That page is beautiful. Has the same goofy "WRONG" top bar. But that sidebar.. The sidebar. It follows the philosophy of being purple. It has a purple sidebar. Now why can't the header have that purple background too? Also make the fonts larger if possible. Make them larger so people don't need to increase the font size on their browser for your website. Make less work people need to do to use your resources. Please consider what has been mentioned in this post and let in sink in. Thanks.