We identified distinct kinds of users: Learners who are finding the specification to the first time, Observers of the specification who are watching proposal improvement, and Reference Users who desire a central place where all the substantial documents can be found. The website was designed around these users. So as to not overwhelm people with information, the MVP is especially focused on the information, namely suggestions of our process. Links are contextualized in order to help people understand what documents they’re currently looking at.
We are looking forward to your comments and comments. This endeavor was community-driven– thank you to everyone who made it possible!
Included in the survey, emails gathered so as to get in contact later, as we were uncertain how many responses we’d get. The goal was to better understand specific concerns. But , we had an overwhelming amount of feedback that pointed us in the direction we had to go. After reviewing this, we decided against keeping to ask feedback publicly and this information. Thank you to everybody who participated.
The site is quite easy, but gives us a beginning point from which to move forward. We’re continuing to work on documenting our procedure. We expect to make more of these documents available and to integrate them.
Screenshot of this TC39 website
The site comes as a part of work that began last year to comprehend the way the community accessed information . We did a run of in-person interviews to better understand what people fought. Among the biggest requests was that we publish and maintain a website that helps people find the information that they are looking for.
Aggregated tags in response to this query”Is there something we can do better, or that you find especially frustrating at this time?”
We’ve got plans to enlarge it while the website is straightforward and now an MVP. These programs include a set of documentation. As the need arises, We’ll experiment with different features.
The two most items with respect to resources were a Website along with Learning Resources. These two are connected, but need different kinds of work. Since this highlighted the need we began work on this right away.
Aggregated tags in response to the question”What do you want to view as a resource for the language specification process?”