Problem
Growth often adds navigation before it adds clarity. New pages, packages, and experiments accumulate until the public interface begins to describe internal history instead of useful choices.
Summary
Keep the public interface small by grouping work around the question a visitor has. Projects are things to use. Engineering is how decisions were made. Open source is what can be inspected. Labs are what is still being tested.
Implementation
Every new section needs an explicit contract: who it is for, what it contains, and what it must never contain. That contract is more useful than a long navigation list.
Conclusion
A small interface is not less ambitious. It is easier to learn, easier to maintain, and more honest about where work is ready to be used.