User:Eeggert/Work Plan

From Education & Outreach

SLH:EE 1:1

SLH to ask:

  • traveling this week?
    • traveling Friday, as noted in Absence.
  • ✅ e-mail where Netlify said OK to subscription in exchange for listing
    • forwarded. subject: “Fwd: Subject: Open Source Plan for the efforts of the W3C Web Accessibil...”

transition

What is needed for comfortable transition? For example:

  • What do we need to set up?
    • Netlify (W3C needs to get someone(s) set up in Netlify, and then Eric can transfer the W3C WAI "organization" to them/us.)
    • @@ (what else?)
  • What will Eric finish?
    • Transitioning the Tutorials into the new site. (confirmed with EO Chairs that not need EOWG review)
      • Still hope this works out.
    • ✅ Change WAI site secondary navigation of overview pages per https://github.com/w3c/wai-website/issues/126
  • What needs additional documentation and/or coordination to hand-off comfortably?
    • ✅ QuickRef — Eric to write documentation (v. similar to website, main difference where to put files)
    • ✅ Policies — simple documentation on how to do it.
      • Shawn asks: Please put the relevant info in EOWG- &/or Team-space (maybe here?) so Andrew and others can do what they need to do. :-)
        • Eric replies: That’s what I did on Tuesday before our meeting.
    • ✅ Documentation on how to do pages not in main nav to get correct breadcrumb, e.g., Acknowledgements pages.
    • @@ (what else?)
  • Other?
    • @@ (what else?)
  • (What's not needed:)
    • Eval Tools List documentation - Shadi has been doing that


Maintenance skills and time:

  • ✅ CVS for uploading site
  • @@ for @@
  • time: @@-@@ hours / week


New creation skills:

  • CSS for new visual design aspects
  • @@ for @@


priorities - any discussion needed?:

  1. https://wai-website-theme.netlify.com/technical/ documentation for W3C staff to update site, other documentation such as where things are: site design components, in which GitHub repo, etc.
  2. SVG components images for other translators - for components (also stds overview) & 1 in bcase
  3. handing off some development and technical support — e.g., Laura presentation CSS, Laura Easy Checks filtering?, Laura updating links, ...
    • reached out 2020-02-04
    • talked to Laura on 2020-02-11: She’s happy to do content review and minor edits, but not CSS or HTML
  4. Tutorials

other:

Work Plan

CW 41

  • W3C Days: Tuesday, Wednesday, Friday (for meeting)
  • Hidde info about GitHub Actions
  • Some documentation
  • Worked on the Images Tutorial
  • Working on the Tables Tutorial
  • Hope to bring ideas, comments, considerations to EO somehow next week.

Other/Ongoing

  • Helping new people to get oriented around documents
  • Helping Shadi with some github/development questions, picking up from WAI-DEV
  • Ongoing: Github Issue grooming
  • Ongoing: Publishing website when asked to do so
  • EOWG participation

Out of office

  • October, 21–29

Done

CW 17:

  • Priority 1: Links for translations (look into options to simplify this) (Likely Week of April 15 & April 22)
  • Priority 1: Fix high priority bugs to close out translations (https://github.com/w3c/wai-website/labels/prevent-merge) (Likely Week of April 15 & April 22 & April 29)

CW 18:

CW 19:

CW 20:

CW 21:

CW 22

CW 23

CW 24

  • W3C Days: Tues & Fri
  • Hidde Onboarding
  • & Documentation
  • Website issues?
  • Quickref
  • Likely, hope to wrap up: Quickref issues & 2.1 JSON (done in CW 23)

CW 25

  • W3C days: Thursday & Friday
  • Documentation
  • SVG for translations
  • Website issues

CW 26

  • W3C Days: Mon, Tue, Fri (but all not fully)
  • ✓ All translations
  • Documentation?
  • Finalize Website issues.

CW 27

  • W3C Day: Tuesday
  • Out of Office: July 4&5
  • Quickref Techniques
  • If time: Video Player Page
  • Start with Tutorial work.
  • Documentation

CW 28

  • W3C Days: Tuesday & Friday
  • Meet with Hidde on Friday
  • Website additions & Changes
  • Documentation Translations Cleanup
  • Start with Tutorial work.

CW 29

  • W3C Days: Wednesday(?) & Friday
  • Translations release
  • Website fixes
  • Documentation
  • Start with Tutorial work.

CW 30

  • W3C Days: Wednesday & Friday
  • Documentation
  • Start with Tutorial work.

CW 31

  • W3C Days: Monday & Thursday
  • Documentation
  • Start with Tutorial work.

CW 32

  • W3C Days: Monday & Thursday
  • Documentation/Sick :-/
  • Start with Tutorial work.

CW 32

  • W3C Days: Monday/Tuesday/Friday bits
  • Documentation
  • Start with Tutorial work planning

CW 33

  • W3C Days: unsure yet
  • Documentation (finalize 🤞)
  • Start with Tutorial work plan
  • Shook out differently than expected

CW 34

  • W3C Days: unsure yet
  • Bring tutorials plan to EO Plan
  • Bring tutorials plan to EO?
  • Shook out differently than expected

CW 35

  • W3C Days: unsure yet
  • Tutorials into new layout: Images & Tables
  • Shook out differently than expected

CW 36

  • W3C Days: Some Tue/Thur/Fri
  • Documentation
  • Start with Tutorial work plan

CW 37

  • W3C Days: unsure yet
  • Finalize Documentation
  • Bring tutorials plan to EO Plan
  • Bring tutorials plan to EO?
    • Especially asking for prioritization

CW 38

  • W3C Days: unsure yet
  • Tutorials into new layout: Images & Tables

CW 39

  • W3C Days: unsure yet
  • Tutorials into new layout: Menu & Forms

CW 40

  • W3C Days: unsure yet
  • Tutorials into new layout: Page Structure & Carousels

OUTDATED

High Priority

  1. Documentation (so others can find the site design components, etc.)
  2. Tutorials – 2.1 updates & links (after approach agreed upon with EOWG & AG -- has happened now)
    • Needs review through EO survey again, heads-up to AGWG
  3. MISC Website Issues, October/November Edition
    • Ensure meets WCAG 2.1 Level AA, and AAA where feasible (can ask AG for review or input if needed)
  4. ongoing: meta back into WAI pages 87 (or higher priority if easy!)

Waiting for OK

  1. Translations (coding/UI)
    1. rough mock-up of final proposal!

Medium Priority

Lower Priority

  • Presentations (CSS)

Waiting

  1. Waiting for the green light for implementation: old WAI pages - redirects, robots, outdated note

Next

  1. Tutorials – put into new design (not only visuals, but also re-format examples, put JS into new format…)

Q1 2019

  1. Components list: Carry out approach as discussed with Shadi

Other Potentially Upcoming

  • Laws & Policies backend updates
  • Tutorials – New content (for 2.1)
  • EasyChecks Next Gen (coding/UI)
Retrieved from "https://www.w3.org/WAI/EO/wiki/index.php?title=User:Eeggert/Work_Plan&oldid=30531"