over the past few months, @tyleretters, @tehn, and @eigen have completely re-designed norns.community to address what we’ve learned from the life of the first version – most importantly, the friction involved in authors having to manually re-pack materials for the maiden project manager, GitHub repositories, lines threads, and norns.community entries. we also found that the platform we’d selected for the first version had too many moving parts to be fun, in practice. so, from February 3rd onward, we began dissecting what mechanisms were necessary to keep the usefulness of the resource while cutting the cruft of the behind-the-scenes processes. we took inspiration from permacomputing for the new site’s architecture and technology, with a necessary eye toward web accessibility practices.
through many incredibly thoughtful pre-release iterations, and a fantastic round of author feedback, we’re incredibly stoked to share that @tyleretters has put the finishing touches on version 2 of norns.community !!
script authors: thank you all for your generous + continued contributions to this community – we hope that you’ve found as much energy and warmth throughout your engagement with this project as the mountains of folks who make your scripts part of their music-making rituals 
still-highly-relevant thoughts from @tehn’s v1 top-post:
over the last three years norns has grown beyond our earliest imaginings: all sorts of new functionality, expanded documentation, group tutorials and classes, weekly hangouts, and perhaps most notably a huge explosion of community-contributed scripts. script-making is also art-making, and the inspiring level of sharing has itself built a community.
last year we created the Library category here on lines to collect and discuss new projects: updates, documentation, exchanges between artist and author, artifacts created with the script— these all combine to create interwoven streams of text.
as the collection grew it became clear that a forum is not a perfect platform for cataloging and discovery. earlier on we began listing a handful of contributed scripts within the monome documentation as celebrated examples, but increasingly we’d like to emphasize that virtually all of these scripts are the work of the community itself.
so we (@dan_derks and i) decided to create a centralized place for community projects, and brought on some talent to help shape the vision. @tyleretters (who initiated the norns study group) added sharp visual styling and data design. @eigen (who launched the
awesome-monome-nornsrepository) created a dynamic discovery mechanism with tagging and gallery images. and importantly, over the last month we’ve been working with a crowd of script authors to populate the collection, gather insight, and make adjustments.with deep gratitude for your continuing generosity, we present to you: norns.community
immediate contributions are encouraged. please let us know here if you need any assistance getting started, and we welcome your feedback.
the Library category on lines will absolutely continue to serve as the best place to announce and discuss projects. but the new community site will be an excellent place to host script documentation and a dedicated platform to explore the growing collection. as always, the monome docs will be where all of the tutorials, reference, and learning materials live.
together we will continue to evolve ++
