assets-conference / assets2024 Goto Github PK

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

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

See #17, for parent

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.

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

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.

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.

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

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

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!

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)

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 subtasks:

• See #18

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

gives a 404 error

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

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

I'm thinking this might work just fine.
David

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/

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

hsdajkfhdsakjhf

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