Two lists that did not exist, and a way to ask them a question. The documentation is the whole studio explained department by department, for the people directing rather than the people building it — and the ? in every corner now answers out of it. The services page names every screen that sits beside the reels — the benchmarks board, the usage and cost reports, the prompt and dictionary editors, the desks behind the feedback portal — none of which were linked from anywhere.
NewStudioDocumentation: the whole studio is written down at /docs — sixteen chapters covering every department, window and control, in the language of the studio rather than of the code. The front page asks what you need to know, and under it asks which job you are here to do: seven roles, each opening the same book in the order that job needs it, with the screens in pictures and the controls marked on them.
NewStudioAsk a question: the ? in the corner of every screen now answers. Ask it the way you would ask a colleague — the answer is read out of the documentation and nothing else, and arrives with the pages it came from, which open beside your work rather than instead of it. When the book does not cover something it says so, rather than inventing an answer.
NewStudioServices: one page at /services lists every screen beside the main flow — what each one is for, who may open it, and how much the studio has actually used it in the last month. Studio staff only.