Meeting minutes
<Jem> Meeting agenda: https://
<Jem> https://
<Jem> https://
<Jem> https://
<Jem> we will review the project board
<Jem> mck: first, we can review "in review" section
<Jem> ... issue #26
<Jem> ... it will moved to done section when it is merged
<Jem> shawn: will update template to address the issue #28
<Jem> https://
<Rich_Noah> https://
<Jem> mck: there are two <div>s in the banner which casaues the problem with screen reader.
<Jem> ... the second div will be the paragraph tag instead.
<Jem> with Shawn's template change.
<Rich_Noah> https://
<Jem> steve will work on the issue 28.
<Jem> shawn: then we can add that to QA list.
Create page footers for example pages #32
<Jem> mck:how the date is updated in the footer?
<Jem> mck: we can correct the date later in the footer.
<Jem> shawn: I think it will be fine for now.
landmark issue #46
<Jem> mck: it is not trivial work to be done before the release
<Jem> but links are working
Move "read me first" content, issue 48
<Matt_King> read me first page: https://
<Jem> https://
<shawn> https://
<Jem> shawn: feedback on the image of person pointing
<Jem> ... we prefer not to use any hand gestures in the image to accomodate different cultures
Matt_King: I looked at the readme, content wise it looks all good
Rich_Noah: Matt, is "Readme" different than "read me first?"
Matt_King: no..
Rich_Noah: preview 63 is different from preview 62, just so you know -- they point to different things
Matt_King: the standalone read me first page looks to be right
shawn: looking at preview 62, everything looks correct.
shawn: when do we expect all these PRs to get merged into main?
Rich_Noah: current plan is on the 11th (tomorrow - wednesday)
shawn: to confirm, we're gonna get an okay to publish on the 11th; we can publish on the 12th, then Bocoup will be available for fixes after that?
Rich_Noah: yes - I didn't see an ask for our availability but we are available
Matt_King: we'll do the quiet launch thursday the 12th at 9am ET
Matt_King: so tomorrow, all the things we're reviewing now get merged (in the review column of the project) -- right?
Rich_Noah: that's the plan, waiting on a couple PRs to be created for what's already in progress, but yes
shawn: if the email was missed - what i'm most interested in gettin done first is the underlying template and site-wide things. smaller things can be fixed later on
shawn: basically, if we need to tweak the image, or make smaller text/HTML changes, we can do that later on. But let's get the bigger things done first so we can get tests going
Matt_King: so the other issues in the review column, about the headings on the fundamentals pages; help improve; create email; including apg in the title tag -- these all look good to _me_
Matt_King: issue 49, about fixing broken links, those all look working to me now. i didn't find any other issues related to links etc.
Matt_King: seems like the only thing we're really waiting on is issue 96
Matt_King: moving the ToC to the right side, are we coordinated on this?
issue 24
shawn: yes, steve said he updated the template. so once we have the new one, that should be fixed
<Jem> https://
Matt_King: rich, do you know when a PR will be ready?
Rich_Noah: should be within the body of work that should be updated by end of the day today
Issue 66
Matt_King: removing obsolete content from the about page - will this be in a PR today?
<Jem> https://
Rich_Noah: i expect it to be
<Jem> Remove obsolete content from About page and move list of editors under acknowledgements #66
Matt_King: is there a PR associated with this?
Rich_Noah: preview 62
Matt_King: i still see editors listed at the top, abstract, etc
Matt_King: the new intro content isn't in here yet
Rich_Noah: it's not complete yet
Jem: are we removing the major contributors to 1.1 section?
Matt_King: i may edit some of _that_ content
Matt_King: right now, under the heading "About" we have the list of all versions - that's going away
Matt_King: editors will go under acknowledgements
Matt_King: information about feedback will be removed, as well as abstract
Matt_King: intro is staying, but will be modified with the content in the main branch
Matt_King: status of the document will be gone too
Matt_King: so there will be 4 subheadings
Matt_King: i'm not sure how cleaned up everything under acknowledgements will be on launch day. it won't be inaccurate, but maybe not polished
shawn: right
shawn: that's easy to update
shawn: rich, we probably want to have the change history and acknowledgements collapsed by default - we have a standard control for that
Matt_King: after launch I want to talk about the about page design. i imagine it being lots more like fundamentals and practices pages, linking off to more content
Matt_King: i love the way the top level nav got sorted out
shawn: i'm not sure it's been propogated _everywhere_ yet though
Matt_King: we have 6 in the next up section
Matt_King: 55 - can be done later without causing issues, right?
shawn: yep
Matt_King: 52, this is a template one... but it's done right? yeah, labelled feedback, so it's done, in preview 62
Matt_King: issue 70, I'm anxious to test this on Thursday to see if it might be a Netlify thing.
Matt_King: my experience with JAWS, VO, Narrator in Chrome and Safari is not good
Matt_King: JAWS doesn't activate those links on the first try
Matt_King: narrator is the same on chrome. Safari, if you read with the next item key, content isn't read
Matt_King: if you strip down to the basic HTML, removing everything from head (except content type), problems disappear. so that's why I'm thinking it's related to netlify
Rich_Noah: alex could reproduce this locally, so it's not netlify. he's looking at it, trying to isolate. can't promise anything today
Matt_King: i opened a chrome bug (linked) - if we can isolate the cause, let's add that to the chrome bug. it feels like a browser bug, chrome and safari (webkit) have problems. firefox, though, is fine
Matt_King: could be that Firefox is behind and hasn't broken something
Matt_King: (yet)
Matt_King: testing the href on the WAI link, trivial?
shawn: just a test ;)
Matt_King: URI is all good?
shawn: yep
shawn: what about issue 60 though?
Matt_King: is 60 in the next up column?
<Jem> Adjust primary navigation to remove "fundamentals" conflict and improve link/title consistency #60
Matt_King: that's a definite P0 for launch, but could be done on thurs or friday, right?
Rich_Noah: yes - we just haven't started yet. other things to do, but it should be simple
shawn: if it's just a text change that's no problem
s3ththompson: i wanted to ask - would your respective institutions be interested in teweeting or otherwise sharing?
Jem: sure
MarkMcCarthy: yep!
Matt_King: i want to put our comms person on it
s3ththompson: we're hoping to have something to you tomorrow Matt
shawn: there's a google doc with our recent work on that
s3ththompson: i'll send an email to James to see about Adobe
s3ththompson: oh right - I've got this
shawn: i did make some updates, but this is the latest i know of
Matt_King: this is exciting!! it's really happening!!
Matt_King: proud of everyone, great work