Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Structured Data 2022 #2882

Closed
6 tasks done
rviscomi opened this issue Apr 12, 2022 · 91 comments · Fixed by #3094
Closed
6 tasks done

Structured Data 2022 #2882

rviscomi opened this issue Apr 12, 2022 · 91 comments · Fixed by #3094
Assignees
@allen-oneill
Labels
2022 chapter Tracking issue for a 2022 chapter ASAP This issue is blocking progress
Milestone
2022 Content Writing

Comments

@rviscomi
Copy link
Member

rviscomi commented Apr 12, 2022 •
edited by tunetheweb
Loading

Structured Data 2022

Structured Data illustration

If you're interested in contributing to the Structured Data 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
@DataBytzAI @cyberandy @DataBytzAI @JohnBarrettWDW @SeoRobt @jasonbellwebdataworks @jonoalderson @rviscomi @JasmineDW @siakaramalegos
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 Structured Data 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-structured-data on Slack for team coordination
@rviscomi rviscomi added 2022 chapter Tracking issue for a 2022 chapter help wanted Extra attention is needed labels Apr 12, 2022
@rviscomi rviscomi added this to the 2022 Content Planning milestone Apr 12, 2022
@cyberandy
Copy link
Contributor

Hi @rviscomi happy to contribute as author 🤓

@github-actions github-actions bot mentioned this issue Apr 12, 2022
Closed
@allen-oneill
Copy link
Contributor

Hi @rviscomi happy to help as author .... lot of work to be done in this space!

@jonoalderson
Copy link
Contributor

Would love to lead this one again!

@cyberandy
Copy link
Contributor

@jonoalderson please do 🙏

@siakaramalegos siakaramalegos added help wanted: reviewers This chapter is looking for reviewers help wanted: analysts This chapter is looking for data analysts labels Apr 15, 2022
@JasmineDW
Copy link

Hello @rviscomi I'd like to be an editor!

@SeoRobt
Copy link
Contributor

SeoRobt commented Apr 21, 2022

Hey everyone, would be thrilled to participate as a reviewer!

@allen-oneill
Copy link
Contributor

@jonoalderson @cyberandy would be great to have a call for intros and planning ... esp since you folk have been there before :D

@jonoalderson
Copy link
Contributor

Hey @DataBytzAI yep, sounds like a plan! Carved out some time later this week to start getting things in motion 👍

@carducci
Copy link

Hello! I spend my days hands-on with semantic web technologies; particularly defining, describing, and linking structured data in a distributed KG system. These are also topics I speak about at tech conferences. If there is any room to participate as an author, I would be honored to be considered.

If not, perhaps I can add value in another role. Either way, I thank you for the consideration :)

@allen-oneill
Copy link
Contributor

allen-oneill commented Apr 27, 2022 •
edited
Loading

@jonoalderson when suits Today/Thur/Fri for an intro call? .... I am London/Dublin time zone ... anyone else available to call?
@cyberandy @carducci ?

sorry @JasmineDW @siakaramalegos @SeoRobt meant to mention you as well to join call if possible!!

@carducci
Copy link

@DataBytzAI I'm available almost anytime tomorrow after 4:00PM London/Dublin time.

Friday I can connect anytime after 2:00PM London/Dublin time.

@SeoRobt
Copy link
Contributor

SeoRobt commented Apr 27, 2022

Thanks @DataBytzAI great to e-meet you! I'm available anytime tomorrow or Friday, currently in Central Standard Time zone.

@jonoalderson
Copy link
Contributor

Hey folks, any time Friday afternoon works for me.
Shall we aim for 4pm UTC on Friday?

@allen-oneill
Copy link
Contributor

Structured data call Friday 16:00 UTC (17:00 London time), good for everyone else?
@cyberandy @carducci @JasmineDW @siakaramalegos @SeoRobt

cc: @jonoalderson

@carducci
Copy link

carducci commented Apr 28, 2022 •
edited
Loading

Assuming the time works for everyone, I have created a zoom room.

Michael C (He/Him) is inviting you to a scheduled Zoom meeting.

Topic: Structured Data 2022
Time: Apr 29, 2022 04:00 PM Universal Time UTC

Join Zoom Meeting
https://us06web.zoom.us/j/81102069402?pwd=UDBqclNMWWtZK0tVdzBtTUY1ajBDUT09

Meeting ID: 811 0206 9402
Passcode: 312040
One tap mobile
+12532158782,,81102069402#,,,,*312040# US (Tacoma)
+13462487799,,81102069402#,,,,*312040# US (Houston)

Dial by your location
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 929 436 2866 US (New York)
Meeting ID: 811 0206 9402
Passcode: 312040
Find your local number: https://us06web.zoom.us/u/kcti4pHfFj

@cyberandy @DataBytzAI @JasmineDW @SeoRobt @siakaramalegos

cc: @jonoalderson

@SeoRobt
Copy link
Contributor

SeoRobt commented Apr 28, 2022

Hey @carducci thanks for setting that up. Confirming that the meeting will be at 6 UTC? The invite shows 4 UTC. Talk tomorrow!

@carducci
Copy link

Structured data call Friday 16:00 UTC (17:00 London time), good for everyone else?

Are we moving to 18:00 UTC? Happy to update the meeting but I want to confirm

@allen-oneill
Copy link
Contributor

Structured data call Friday 16:00 UTC (17:00 London time), good for everyone else?

Are we moving to 18:00 UTC? Happy to update the meeting but I want to confirm

fine here (7pm London time)

@jonoalderson
Copy link
Contributor

I'm flexible.

@SeoRobt
Copy link
Contributor

SeoRobt commented Apr 28, 2022

Sincere apologies @carducci, the Zoom invite for 16:00 UTC is correct and works for everyone.

@jonoalderson
Copy link
Contributor

I'll be there, though annoyingly I have a hard stop for another call at 16:30 UTC. :(

@cyberandy
Copy link
Contributor

cyberandy commented Aug 8, 2022 via email

@siakaramalegos
Copy link
Member

@DataBytzAI when do you think you can begin the draft? Just as a reminder, the due date at the end of the month is for post-review and post-edit, so you'll need to set aside at least a week for those and preferably more.

@allen-oneill
Copy link
Contributor

allen-oneill commented Aug 12, 2022 via email

@rick
Copy link

rick commented Aug 16, 2022

you rang?

@rick rick mentioned this issue Aug 16, 2022
Open
@rviscomi
Copy link
Member Author

Sorry for the disruption @rick! 😆

@siakaramalegos
Copy link
Member

Hi all, great job getting started on the draft! Can it be ready for review within the next 1-2 days? The reviewers need time to review it and then authors need time to incorporate feedback, and then we need to do a writing style/usage editing cycle all before August 31 to stay on track. Let us know your status

@DataBytzAI | @cyberandy @DataBytzAI @JohnBarrettWDW | @SeoRobt @jonoalderson

@allen-oneill
Copy link
Contributor

Hi @siakaramalegos ... we expect to have the main body of it completed today, tomorrow latest...
Andrea is doing the sankey chart for relationship data ...@cyberandy can you give us an update on that?
Otherwise I have sent a message to the other on the list for any contributions they can add or for them to please commence input/editing! .... I think we are good to be on track for final review before Monday!

@tunetheweb tunetheweb mentioned this issue Aug 28, 2022
Merged
@siakaramalegos
Copy link
Member

Great progress so far team! What's next to finish up the draft and reviews? We'd really like to get this published in the first cycle. @DataBytzAI @cyberandy @DataBytzAI @JohnBarrettWDW | @SeoRobt @jonoalderson

@allen-oneill
Copy link
Contributor

allen-oneill commented Sep 2, 2022 •
edited
Loading

Thanks @siakaramalegos ... late start but glad we were able to bring it together!
We feel we have the core of things complete ... @cyberandy was doing some charts that I think are complete - Andrea you might comment please? .... also @jonoalderson and @SeoRobt are currently doing their final review I think - folks can you comment on where you are with that? ... finally, hats off to the amazing @JasmineDWillson who has wielded her quill and ink and brought excellent structure to bear on the overall document as it now stands :D

@jonoalderson
Copy link
Contributor

I'm unexpectedly behind due to some illness this week 😩

I'm aiming to carve out a chunk of the weekend to review, but don't wait on me if I'm too late to the party.

@SeoRobt
Copy link
Contributor

SeoRobt commented Sep 2, 2022

I'm planning on adding a couple of small comments over the weekend for my final input. Nothing major on my end!

@allen-oneill
Copy link
Contributor

allen-oneill commented Sep 2, 2022 via email

@rviscomi rviscomi added the ASAP This issue is blocking progress label Sep 3, 2022
@allen-oneill
Copy link
Contributor

@cyberandy what do we need to do to add your charts (and any related comment) to the document? ...
Far as I can see that's the only thing we have outstanding now?

cc: @siakaramalegos @rviscomi

@SeoRobt SeoRobt closed this as completed Sep 4, 2022
@SeoRobt SeoRobt reopened this Sep 4, 2022
@siakaramalegos
Copy link
Member

@DataBytzAI | @cyberandy @DataBytzAI @JohnBarrettWDW @SeoRobt @jonoalderson what's the status on the chapter? Are all parts written? It looks like it only has 1 technical review so far - any way to get another? We're already more than a week behind schedule and the editing cannot happen until technical review is complete.

@allen-oneill
Copy link
Contributor

@siakaramalegos working on a technical - brb!

@allen-oneill
Copy link
Contributor

@DataBytzAI | @cyberandy @DataBytzAI @JohnBarrettWDW @SeoRobt @jonoalderson what's the status on the chapter? Are all parts written? It looks like it only has 1 technical review so far - any way to get another? We're already more than a week behind schedule and the editing cannot happen until technical review is complete.

@siakaramalegos ... done - we have @jasonbellwebdataworks onboard ... will have that review completed today fingers crossed!

@rviscomi
Copy link
Member Author

@DataBytzAI any update on resolving the remaining feedback in the doc and regarding the sankey diagrams? Getting close to the deadline to be included in the Monday release.

@allen-oneill
Copy link
Contributor

allen-oneill commented Sep 25, 2022 via email

@allen-oneill
Copy link
Contributor

allen-oneill commented Oct 11, 2022 via email

@cyberandy
Copy link
Contributor

Sorry to hear about @jonoalderson, @DataBytzAI shall I review the document on Drive or here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@allen-oneill allen-oneill

Labels
2022 chapter Tracking issue for a 2022 chapter ASAP This issue is blocking progress
Projects
None yet
Milestone
2022 Content Writing
Development

Successfully merging a pull request may close this issue.

2022 Structured Data chapter HTTPArchive/almanac.httparchive.org