One thing rhat would be really useful would be a search for the documentation. I've resorted to grepping the documentation in source. Google searches typically end up on an old page.
G From: Alex Heneveld <[email protected]> To: [email protected] Date: 04/13/2017 10:26 AM Subject: Brooklyn website Hi folks- I've been hearing two categories of feedback from people who've spent time on our website: "I don't get it" and "Sounds complicated". I think the time is right for us to fix this. We can give a clear, gentle experience, and we can tone down the academic ideas in favour of real examples, which thanks to recent improvements are pretty simple. I'm thinking of a few changes: * Expand and ground the landing page (currently it's all academic theory words words words) -- I attach a mock-up of how this could look in the attached (based on other sites) * Rework the Getting Started example to be something using bash, rather than a magic java entity * Instead of YAML/Java blueprints, call it "Basic Blueprints" "Advanced Blueprinting", make the "Basic Blueprints" section nice simpler reference pages, with much of the content moved into advanced (where the Java items might get buried further) What do other people think? Should we have a chat? Say next Fri 4pm UK ? Best Alex
