-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📣 Contribute to the 2021 Web Almanac #2167
Comments
@rviscomi with the growing interest in ESG (Environmental, Social, and Corporate Governance) do you foresee a time when there may be a chapter on energy consumption features of the web? |
I wonder if localization can also be a topic. I know there's various different work going on in localization and internationalization for languages that are not ltr from logical css to fonts to other stuff. |
We definitely want to try and add WebAssembly data this year. |
@cqueern That's a great idea and a really important topic. What do you think about dedicating a section to that as part of the Page Weight (#2157) chapter, given how it's a function of bytes?
Thanks @SaptakS and @RReverser I've added those chapters to the list! See #2169 and #2168 |
Glad you're excited too! |
The original interest form had a designer role as well. Where does that fit in? |
@rviscomi what about Ajax? As far as I know there's no chapter covering it. Understanding the current state of Ajax use, via various apis, like XMLHttpRequest, fetch or even beacon looks like a good addition to the almanac. |
Thanks for the suggestion @soulcorrosion. I think that would be a good topic to explore in the JavaScript chapter. Would you be interested to join that team as a reviewer? |
Hi there, I would be interested in collaborating with the translations. I could help with either Japanese or Spanish. Where could I get more information about that? |
Would love to have your help @alangdm ! I've just sent you GitHub invites to the project there so you'll be able to edit and be assigned to issues. Japanese is being tracked in #586 and is making great progress by @ksakae1216 . 2019 is completely done, and 2020 is more than half done. Spanish is being tracked in #498 and currently only has one 2020 translation and a handful of 2019, but the ground work is all done so ready to go! There's more info in our Translator's Guide but feel to comment on either of above two issues if you have any questions! |
@tunetheweb Thanks for the invite, I'll check the issues and see what I can help with 👍 |
Really important issue. I've been doing a good bit of research around the environmental impact of data and digital devices, so if there's any way I can help, I'd be happy to. |
Team, @rviscomi suggested we explore what data the HTTP Archive might offer to investigate the carbon impact of websites over on the HTTP Archive forum. Look forward to your thoughts! |
Hi @TrevorFSmith, we had a section for WebXR in the 2019 Media chapter but it never materialized. @Yonet do you remember what the reason was for dropping it? Looking through the queries, I only see one basic query for XR libraries based on script file names. If you feel like there is enough content to research and talk about this year I'd be super excited to see us include a section in the 2021 Media chapter. Let me know what you both think and I can add you to the Media team. |
@rviscomi Based on the stories I've found for each week of the Immersive Web Weekly there was a large uptick in WebXR usage in 2020 that continues today. If nothing else, we can update the query that you linked to include common libraries like react-three-fiber and wonderland. |
@TrevorFSmith sounds good, let's discuss in #2144 |
I'm interested joining as a reviewer of the JavaScript section. ✨ |
Hi @rviscomi, sure, I'll be glad to help. |
I was thinking if we can also have Immersive Web (WebXR) as a chapter too. It would be wonderful to finally have it as a separate chapter |
Hi @HTTPArchive/almanac-contributors, it's that special time of year again when we kick off another edition of the Web Almanac "state of the web" report!
At this early stage, we're starting with assigning teams of contributors to each chapter. A chapter's content team consists of authors, reviewers, analysts, and editors. See this discussion for more info about how authors are selected.
ℹ️ To get involved, choose a chapter from the list below and reply to its respective issue to indicate which role(s) you'd be interested in. You can also filter issues for those labelled "2021 chapter" and "help wanted" to see what's available.
Here's the current lineup for 2021:
Page Content
User Experience
Content Publishing
Content Distribution
Are there any other major topics on the web that we're missing? Any suggestions to organize the content differently? We'd love to hear your ideas in the comments.
For all chapter-specific questions/discussions, head over to the issues linked above.
And if you're interested to contribute to the project beyond a specific chapter, there are also opportunities to join the translators, developers, and designers teams!
The Web Almanac is supported entirely by the web community, so thank you all for your interest and support to keep this valuable resource going year after year!
The text was updated successfully, but these errors were encountered: