assets-conference / assets2024 Goto Github PK

gives a 404 error

General Chairs at top.
Then TPCs.
Then Treasurer.
Then Posters.
Then everyone else in any order.
Thanks!

Add an alert to somewhere (will discuss in meeting today) that PCS is now open for Posters & Demos, Workshops, Doctoral Consortium (DC), Student Research Competition (SRC), and Experience Reports (ERs).
I think this alert could visually follow the 'alert' on the Workshop Call-for-Papers (CfP) page (an update on Workshop format).
Possible locations are the individual CfPs for the tracks listed above.
Another possible location is on the main conference page itself above the important dates.
David

please add two new deadlines to technical papers CfP - email from TPCs was:
we have set dates for the technical program camera-ready (7/24) and video presentation (7/31) deadlines. A summary of these dates can be found at the top of the CfP doc.

Original text: A workshop proposal must be prepared according to the ACM Master Article Submission Templates (single column). It must be submitted via the PCS Submission System as a single PDF file.

Change requested: A workshop proposal must be prepared according to the ACM Master Article Submission Templates (single column). The submission should not be anonymized and must be submitted via the PCS Submission System as a single PDF file.

in the banner, "computing and accessibility" should be "computers and accessibility"

• Posters and demos
• Workshops
• SRC
• DC
• Experience reports

currently: "[email protected]"
please update to: [email protected]

• Become a sponsor page
• Put up current sponsors page (Already have Google)

Shari used to be at IBM, but recently switched to Google.
Thanks!

This is a accessibility requirement which must be met.

See the following resources for implementation details:
https://www.w3.org/TR/WCAG20-TECHS/G1.html
https://design-system.service.gov.uk/components/skip-link/

As the full committee is still being confirmed, we can start with:

• GCs,
• Treasurer and Reg
• TPCs
• Mentoring Chair
• Web Chairs

Could you please update the banner text to 'Deadline: Wednesday, July 3rd, 2024? It currently says Due Date: June 07, 2024.

See #17, for parent

Reference: https://blog.openreplay.com/creating-a-table-of-content-widget-in-react/

As discovered by some members of the community, it seems like we're missing alt-tags in some of our images, as well as have some inaccessible elements such as "on this page" which need to be corrected.

create "Scholarships" subpage under the "Attending" menu item

I'm thinking this might work just fine.
David

on the landing page, in the logo at the bottom, st. john's is missing an apostrophe

Current, our way to create pages will quickly become untenable and cause a lot of headaches and overhead as copy on pages becomes more complex. A way out of this likely could be using mdx, a modified version of Markdown to create the pages instead.

This seems pretty well supported by NextJS. See: https://nextjs.org/docs/app/building-your-application/configuring/mdx

On https://assets24.sigaccess.org/authors/posters-and-demos/, in Further Information (right at the bottom of the page), the email should be [email protected] (rather than [email protected])

See subtasks:

• See #18

add new Virtual Chair to the OC page (details in an email)

Create new "Attending" menu item, and "Registration" subpage (details in an email)

Apple contributed at 'Gold' level ($10k).
Logo design and layout details in email forwarded by Faustina.
Set this up on the 'testing' server so we can send a link and/or screenshot to Apple for approval prior to making it live.
Thanks!

replace the link to the hotel on the landing page with this one, which offers the group rate:

https://www.marriott.com/events/start.mi?id=1716409363485&key=GRP

Currently deployment to production involves us manually building the site and deploying. This results in updates being batched rather than continuous. We should explore automating this deployment, but need to ensure things like the Main branch gets protected with rules to rule out accidental deploys.

hsdajkfhdsakjhf

1. Update link from 'sponsors' to 'how to become a sponsor'
2. Update table of contents links.
3. Add 'Sponsoring Organizations': SIGACCESS and ACM (see previous year's websites for spelling)

Documentation & other setup chores such as GitHub actions set up should be done before moving the repo over to the ASSETS conference org