Mobile Web 2021

[rviscomi]

Part II Chapter 13: Mobile Web

If you're interested in contributing to the Mobile Web chapter of the 2021 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@ashleyish	@ashleyish @fellowhuman1101 @dwsmart @rvth	@fili @OBTo	@ashleyish @OBTo	@logicalphase	@OBTo

Expand for more information about each role

• The content team lead is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress.
• Authors are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report.
• Reviewers are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases.
• Analysts are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly.
• Editors are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit.
• The section coordinator is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule.

Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors.

For an overview of how the roles work together at each phase of the project, see the Chapter Lifecycle doc.

Milestone checklist

0. Form the content team

• May 31: The content team has at least one author, reviewer, and analyst

1. Plan content

• June 15 The content team has completed the chapter outline in the draft doc

2. Gather data

• June 30: Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress

• July 1 - 31: HTTP Archive runs the July crawl

3. Validate results

• September 30: Analysts have queried all metrics and saved the output to the results sheet

4. Draft content

• October 31: The content team has written, reviewed, and edited the chapter in the doc

5. Publication

• November 15: The completed chapter and all required metadata and figures are converted to markdown and submitted to GitHub

• December 1: Target launch date 🚀

Chapter resources

Refer to these 2021 Mobile Web resources throughout the content creation process:

📄 Google Docs for outlining and drafting content
🔍 SQL files for committing the queries used during analysis
📊 Google Sheets for saving the results of queries
📝 Markdown file for publishing content and managing public metadata

[fili]

Happy to contribute as a peer reviewer here.

[rviscomi]

📟 paging 2019/2020 contributors: @OBTo @logicalphase @AymenLoukil @ymschaap @spanicker @mdiblasio @malchata @cheneytsai

Would any of you be interested to contribute to the 2021 chapter? I'd especially like to see more 2019/2020 authors become 2021 reviewers to help ease the transition and similarly I think prior reviewers would make great 2021 authors, being familiar with the process already. And prior analysts would make excellent 2021 analysts 😁

Or is there anyone new you'd like to see?

[ashleyish]

I can be an analyst and/or coauthor here

[rviscomi]

@ashleyish great thanks! I've added you to the contributor table.

@logicalphase I see you've added yourself as an editor. Did you mean "reviewer"?

[logicalphase]

I can do either one. Just let me know.

[rviscomi]

@ashleyish thanks for your interest in authoring this chapter! As the content team lead, you'll be responsible for the scope and direction of the chapter and keeping it on schedule. We automatically monitor the staffing and progress of each chapter based on the state of the initial comment so please keep that updated as you add new contributors and meet each milestone.

We've created a Google Doc for this chapter, which you're encouraged to use to collaborate with the content team on the initial outline, metrics, and ultimately the final draft.

Next steps for this chapter are:

• Due May 31: Complete Milestone 0: Form the content team—you can check this off now since you've already got at least one author, reviewer, and analyst ✨
• Due June 15: Get started on Milestone 1: Plan content by brainstorming some content ideas in the doc (you may need to request edit access)

@OBTo is the section coordinator for this chapter and they'll be periodically checking in with you directly to make sure the chapter is staying on schedule. Reach out here in this issue if you have any questions about the process.

More information about the content team lead and author roles and responsibilities are available for reference in the wiki if needed.

To anyone else interested in contributing to this chapter, please comment below to join the team!

[dwsmart]

I would be happy to co-author, or help with analysis if @fili needs help here. If y'all good, happy as a reviewer?

[ashleyish]

I'm positively jumping on the prospect of co-authoring with Dave. 

[fellowhuman1101]

@rviscomi volunteering to review for the indomitable @ashleyish and @dwsmart

[rviscomi]

Great to have you @fellowhuman1101 and @dwsmart! I'll defer to @ashleyish as the content team lead for this chapter to onboard both of you and start outlining the chapter; just need to add contributor metadata to the top comment, check off the 0th milestone, and share the draft doc.

[ashleyish]

I'm on it. I'll get us together & update the metadata.

[foxdavidj]

Hey @ashleyish excited to work with you and the rest of the group this year on the Almanac. I'm your go to guy if you've got any questions or need help so don't hesitate to reach out to me on github, the Slack (@OBTo) or email ([email protected]).

Few first steps:

1. All authors, reviewers and analysts should add themselves to the Google Doc in the format: Name ([email protected]). But looks like you've already got a good handle on that.
2. I've added links within the doc to the previous years Google doc in case you'd like to mine it for ideas.
3. Would love to set up a 30 minute Zoom call in the next couple weeks to kick-start the chapter planning and brainstorming process, and put some faces to the names of the people we'll all be working with this year. I'll reach out again later this week to find a time that works.

Put myself down as a reviewer and analyst as well, so I'm excited to work with you all this year.

[foxdavidj]

How does Monday (May 24) at 1p ET / 10a PT / 6p BST (timezones here) work for the 30m chat?

@ashleyish @fellowhuman1101 @dwsmart @fili @logicalphase

[fili]

Sorry, can't do Monday

…

On Wed, May 19, 2021 at 3:33 PM David Fox ***@***.***> wrote: How does Monday (May 24) at 1p ET / 10a PT / 6p BST (timezones here <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=5&day=24&hour=17&min=0&sec=0&p1=64&p2=179&p3=224&p4=136>) work for the 30m chat? @ashleyish <https://github.com/ashleyish> @fellowhuman1101 <https://github.com/fellowhuman1101> @dwsmart <https://github.com/dwsmart> @fili <https://github.com/fili> @logicalphase <https://github.com/logicalphase> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2151 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA4EPZW4T4LAL6M5GLBAY3TOO42NANCNFSM43UFNCVQ> .

-- Fili Wiese ***@***.*** Websites ● fili.com ● seo.consulting ● online.marketing

------------------------------ Registered Office: Friedrichstr. 123, 10117 Berlin, Germany VAT: DE290388554 This email may be confidential or privileged. If you have received this communication in error, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks. Non-binding language if applicable: The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.

[logicalphase]

I'm okay with that date and time.

[logicalphase]

Would it be possible to move the meet to Tuesday 1:00 or later PST?

[foxdavidj]

I can't do that time on Tuesday. How does Wednesday (May 26) at 12p ET / 5p BST (timezones here) work?

[dwsmart]

That Wednesday time is great with me @OBTo

[logicalphase]

Wed is good for me.

…

[foxdavidj]

@ashleyish @fellowhuman1101 Does that time for a 30min kickstart/brainstorming session work for you?

[ashleyish]

I'm in! That time works well.

Is there a Slack available? I'm trying to keep up with all of the messages.

[foxdavidj]

I'm in! That time works well.

Is there a Slack available? I'm trying to keep up with all of the messages.

We can have one made for the group. I'll get one made

[foxdavidj]

Just sent out the invite for the meeting. Shoot an email to [email protected] if you didnt get the invite and I'll add you.

The slack is here: https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA

Just browse the channels and join #web-almanac-mobile-web

[rvth]

If you're still looking for an analyst I'd be happy to help with this one too @ashleyish :)

[foxdavidj]

@ashleyish @fellowhuman1101 @dwsmart @fili

Hey everyone, wanted to check in and give you all a few reminder as we close in on our second deadline:

1. Please make sure you've requested edit access to the Google Planning Doc and added your name to the first page as a reviewer, author or analyst.

2. Reminder that we need to have the chapter outline complete by June 15 so we have enough time to update our crawler with any additional metrics you need this year.

3. The team has a channel on slack (#web-almanac-mobile-web), so feel free to join everyone there as well: https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA

If you have any other questions don't hesitate to reach out :)

[foxdavidj]

@ashleyish Please add yourself in the Google Doc metadata as an author.

The chapter outline is due by June 15th, which is just over a week from now and it doesn't look like anything has been written as of yet. How can we help?

[foxdavidj]

@ashleyish

Data for all but one query (client hint directives) are completed and have their data input in our sheet:

Visualizations will be added next week along with comments for how to read the data.

The explanations for 90% of the queries are the same as last years, so please refer to last years sheet for explanations until I'm able to add them directly to our 2021 sheet.

[foxdavidj]

@ashleyish The data sheet has been updated with comments and should be ready to go. Let me know if you have any questions

[dwsmart]

Hey @OBTo,

@ashleyish is pretty tied up on stuff so me and @fellowhuman1101 will be getting a start on this ASAP, @fellowhuman1101 has popped you a message on slack to see if we can arrange a meet or hangout.

[dwsmart]

Hey @rviscomi ,

Jamie (@fellowhuman1101) doesn't appear to have permissions to push to our branch, (mobile-web-2021), does she need to be added to something, or did I do the dumb think settting up that branch? We're keen to get the markdown pushed!

[tunetheweb]

Sent her the invite to the team!

[dwsmart]

Thanks @tunetheweb

[tunetheweb]

You at the stage yet to open a draft PR? Want me to stage it to a URL so others can see it?

[dwsmart]

Very close, we should be today at some-point, so I'll holla then!

[rviscomi]

@ashleyish @fellowhuman1101 @dwsmart @rvth @fili @OBTo

🎉 This chapter is fully written, reviewed, edited, and ready to be launched on Wednesday! Thank you to all of the contributors who put in the time and effort to make this a great chapter.

When you get 5 minutes, I'd really appreciate if you could fill out our contributor survey to tell us (the project leads) about your experience. It's super helpful to hear what went well or what could be improved for next time. 🙏

Congratulations and thank you all again. I'm excited for this to launch soon!