Mobile Web 2022

[rviscomi]

Mobile Web 2022

If you're interested in contributing to the Mobile Web chapter of the 2022 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
@rviscomi	@Suzzicks	@foxdavidj @dwsmart @hemanth @CodeMartian @dknauss	@siakaramalegos	@rviscomi	@foxdavidj

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 1: The content team has at least one author, reviewer, and analyst

1. Plan content

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

2. Gather data

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

• June 1 - 15: HTTP Archive runs the June crawl

3. Validate results

• August 1: Analysts have queried all metrics and saved the output to the results sheet

4. Draft content

• September 1: The content team has written, reviewed, and edited the chapter in the doc

5. Publication

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

• September 26: Target launch date 🚀

Chapter resources

Refer to these 2022 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
💬 #web-almanac-mobile-web on Slack for team coordination

[Suzzicks]

I can help if you want me to Lead or Author this topic.

[rviscomi]

Thanks @Suzzicks! If you had to pick between Mobile Web and PWA, which would you prefer? Could you also share a brief summary of your experience with each? (sorry to ask, your GitHub profile doesn't have a lot of info)

[dwsmart]

Happy to be a reviewer this year

[hemanth]

Count me in on this! :)

[foxdavidj]

Hey @Suzzicks, do you have a preference between the Mobile Web and PWA chapters? Being an author is a large commitment, so we'd like to know which chapter you'd be most excited to write about.

Also if you could share a brief summary of your experience that'd be terrific!

[foxdavidj]

Hey @dwsmart @hemanth, need some help. In the case @Suzzicks doesn't get back to us, we won't have a Lead for this chapter... which means we'll likely miss our first milestone (May 1st) and will put the chapter at risk of being dropped.

Can you all reach out to anyone you feel may be a good fit for a Lead/Authoring role for the chapter?

Thanks so much for your interest in helping us assemble the chapter this year

[rviscomi]

⚠️ @Suzzicks @dwsmart @hemanth it looks like this chapter still doesn't have a lead or an analyst and the outline hasn't been started yet. As @foxdavidj noted, we might have to drop this chapter if it doesn't seem like there's enough interest to sustain it.

Could you help us find contributors who can staff this chapter? Meanwhile, it'd be great to start brainstorming ideas in the doc and when we get the team fully formed we can hopefully get back on track quickly.

[dwsmart]

Will see if I can drum up some interest, it would be a shame to see it dropped.

If nothing is forthcoming by Monday, I'll try and draft some stuff in the doc!

[rviscomi]

Thank you @dwsmart! If needed, would you be able to take on the lead/author role?

[dwsmart]

I know time is short, but let me get back to you by end of Monday on that, need to make sure I don't overcommit, sorry!

[dwsmart]

Hey @rviscomi, see I promised Monday and here we are Tuesday. I just don't think I can take on author and do a good job too, real sorry!

[rviscomi]

No worries, thank you for following up @dwsmart!

[Suzzicks]

Hi guys - sorry. I have been traveling, and don't spend much time day to day in Github. I can start outlining this week. In terms of credentials, I have specialized in mobile SEO since 2006, my company is MobileMoxie, and I wrote a book about mobile marketing including mobile SEO. I can try to help with mobile web and PWA if you want, as long as that is ok.

FYI: The best way to reach me is always DM on Twitter.

Book: https://g.co/kgs/5duKmr
Company: https://mobilemoxie.com/
LinkedIn: https://www.linkedin.com/in/cindykrum
YouTube: https://www.youtube.com/user/mobilemoxie/videos
Twitter: https://twitter.com/Suzzicks

[rviscomi]

Thanks for the update @Suzzicks! Excited to have you back. 🎉

@Suzzicks @dwsmart @hemanth @foxdavidj make sure you all have access to the planning doc and start adding your ideas to the outline. What's new in the mobile web world this year, or what would be interesting to revisit from previous years? @Suzzicks SGTM to start outlining later this week, but everyone else is encouraged to add notes ASAP.

@Suzzicks as the only author for this chapter, you're the de factor team lead. You'll be responsible for setting the narrative for the chapter's contents, coordinating with the rest of the contributors, and generally keeping it on schedule. The top comment contains all the information/links you need, otherwise let me or @foxdavidj know if there's anything we can clarify.

We're unfortunately unable to check off Milestone 0 as we're still missing an analyst. @rvth @foxdavidj @ymschaap any interest in returning to be the analyst again this year?

[foxdavidj]

@Suzzicks @dwsmart @hemanth @foxdavidj

Hey everyone, excited to see we've got a full team (aside from an analyst) for the chapter!

To kick things off, I'd love to set up a 30 minute call within the next week to put any new faces to names, and give @Suzzicks feedback on her ideas for the chapter's outline.

@Suzzicks as the Chapter Lead can you assist in finding a time that works for everyone? You can see my availability via my calendly here (no need to book through it): https://calendly.com/foxdavid/30min

Also, @Suzzicks here is an agenda template for some other topics you may want to discuss on the kickoff call: https://docs.google.com/document/d/1To1XMnLAO8WPPjHvi0GnrdSWYCL9SOqm9AsUOlOlP2I/edit?usp=sharing

[foxdavidj]

Regarding being an Analyst, my time is unfortunately much more limited this year so I won't be able to take on the role. If others have any questions about the metrics and queries I'm more than happy to answer them

[foxdavidj]

@dwsmart @hemanth Friendly ping. @Suzzicks has written a pretty extensive outline in the chapter planning doc. Can you both take a loot over it?

[polyglotyeoja]

Hey everyone–@jeffmartin and I are interested in pairing as analysts for this chapter

[foxdavidj]

Filled out 👍

[foxdavidj]

@hemanth @CodeMartian @polyglotyeoja see above

[Suzzicks]

Ok - This is booked for tomorrow (Tuesday) at 4pm-5pm MST. A link to the calendar invite with the meeting room is in a comment in the shared doc.

[dknauss]

I’m not sure I’ve come to the right place! I would like to help with any editing and WordPress-related material or similar open source CMS content. It looks like most of the current activity is data collection and analysis.

On Mon, Jun 20, 2022 at 4:24 PM Suzzicks ***@***.***> wrote: Ok - This is booked for tomorrow (Tuesday) at 4pm-5pm MST. A link to the calendar invite with the meeting room is in a comment in the shared doc. — Reply to this email directly, view it on GitHub <#2893 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACCZEWU6SIHM75XQV3HCVDVQDVTBANCNFSM5TH72BIA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

-- –––––––––––––––––––––––– *Dan Knauss* newlocalmedia.com Design. Build.. Sustain... Canada: (780) 394-2700 United States: (515) 329-6560

[tunetheweb]

Hi @dknauss , the CMS chapter is being tracked in #2896 so that might be better fit for you if you want to comment there?

Just to explain the difference between the reviewer and editor roles in each chapter team:

• A reviewer has subject matter expertise and is expected to help suggest chapter direction, review the chapter outline, and then read the text the authors produce for technical accuracy.
• An editor is not necessarily that familiar with the chapter subject but is more tasked with copy editing the text, and ensuring standards across the Web Almanac so it reads as one cohesive text.

So if you have specific CMS knowledge then maybe the reviewer role is better for you?

Anyway, let us know what chapter and role you’d be interested in contribute to.

[dknauss]

Will do, thanks. I can help in either role — whichever is needed more.

…

On Tue, Jun 21, 2022 at 12:43 AM Barry Pollard ***@***.***> wrote: Hi @dknauss <https://github.com/dknauss> , the CMS chapter is being tracked in #2896 <#2896> so that might be better fit for you if you want to comment there? Just to explain the difference between the *reviewer* and *editor* roles in each chapter team: - A *reviewer* has subject matter expertise and is expected to help suggest chapter direction, review the chapter outline, and then read the text the authors produce for technical accuracy. - An *editor* is not necessarily that familiar with the chapter subject but is more tasked with copy editing the text, and ensuring standards across the Web Almanac so it reads as one cohesive text. So if you have specific CMS knowledge then maybe the *reviewer* role is better for you? Anyway, let us know what chapter and role you’d be interested in contribute to. — Reply to this email directly, view it on GitHub <#2893 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACCZEVRBL4HIOILSM5INJDVQFQA5ANCNFSM5TH72BIA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[foxdavidj]

@Suzzicks @polyglotyeoja @CodeMartian

Just a friendly heads-up that the June crawl has completed and all of the data is available to start being queried.

Ideally, to give as much time as possible for writing and editing, it's nice to have all of the queries written by the end of the month. How are you feeling about meeting that deadline?

Looks like a good first step would be for @polyglotyeoja and @CodeMartian to take the metrics that were discussed and put into the Google Docs and make a draft PR (example) listing them all

[foxdavidj]

From the looks of it, it feels like many of the queries can be taken from the ones I wrote in prior years. Which should save a lot of time.

[siakaramalegos]

👋 Adding myself as an analyst. I'm also a section lead for another section so can't do much more than copy from last year. Just linked up the queries PR and will start running them.

[siakaramalegos]

@Suzzicks FYI, I ran all the queries from last year (with updated dates), and have finished putting the data into the results spreadsheet. The charts will take some more time, but you can start exploring the data now. If you'd like to help with the charts, let me know. It doesn't look like they made charts for all the queries last year, and I don't know which ones you want.

[rviscomi]

📟 Calling all reviewers: @foxdavidj @dwsmart @hemanth @CodeMartian @dknauss

@Suzzicks has started drafting the chapter in the doc and she's asked me to step in to help with coordinating on getting everyone's feedback.

1. Request edit access to the draft doc if you haven't already. Also join us in the #web-almanac-mobile-web channel on Slack for higher bandwidth discussions.
2. Read through the draft and leave any suggestions/comments. We're already a bit behind meeting Milestone 4, so in an effort to catch up, please complete your review by September 7.
3. Once @Suzzicks has addressed all feedback, I'll find an editor to give it a non-technical pass. Please aim to have all content changes locked down by September 14.
4. I'll get the chapter converted to markdown and submitted to GitHub for publication on or around September 19.
5. The chapter will be released live on September 26! 🚀

Thanks everyone for your contributions and getting this chapter in shape for launch!

[dwsmart]

I will make sure to jump in and take a look in good time!

[rviscomi]

👋 Hi @foxdavidj @dwsmart @hemanth @CodeMartian

At risk of being redundant, I just wanted to echo my pings in Slack and the draft doc: the chapter is ready to be reviewed and we've altered the schedule so that you have a week to get your feedback in, starting now. I'll be nagging sending you "friendly pings" periodically throughout the week until your review is done or you give me a good excuse 😁