Developed for ACADIA 2026, the platform organized the work between peer-review acceptance and conference delivery. Its Author Portal served as the author-facing entry to an integrated management system spanning publication production, participation requirements, and presentation logistics.
Connected workflows after peer review
The system brought Papers, Projects, Field Notes, PhD Workshop submissions, and Book Forum contributions into a shared framework, with requirements adapted to each track.
| Workflow | What the system connected |
|---|---|
| Publication preparation | Reviewer feedback, author information, abstracts, website images, camera-ready files, and track-specific posters or proceedings materials. |
| Author proof | Release of copyedited PDFs, return of annotated proofs, supporting figures, and confirmation of the completed correction package. |
| Participation | Attendance confirmation, registration records, copyright and recording consent, acceptance letters, and visa invitation letters. |
| Conference presentation | Session time, venue, room, chair, presentation order, fellow presenters, calendar invitations, and PowerPoint templates and uploads. |
| Coordination and follow-up | Per-task progress, recent activity, deadlines, file versions, and submission status within one author dashboard. |
One submission, a connected record
Submission identifiers linked author information, task states, uploaded files, and presentation details. Authors could save a draft, submit an individual task, and return to the same record as later stages opened. Track-specific tasks and release conditions kept the interface aligned with the work required at each stage.
The HTML, CSS, and JavaScript interface communicated asynchronously with a Google Apps Script backend. Google Sheets held submission records, configuration, task data, and activity logs; Google Drive held the associated files. This separation kept the working records editable for organizers while giving authors a focused interface for completing requirements.
File transfers were divided into chunks. Publication materials used Apps Script-mediated uploads, while presentation files used resumable transfers directly to Drive. The presentation workflow checked saved upload progress and file identity before resuming, verified completion, and retained earlier versions for organizers. Session information was refreshed from the conference schedule so presentation instructions and submitted files remained associated with the correct contribution.
Using the portal
- Select the submission type and open the accepted record with the original submission details. Papers, Projects, Field Notes, and PhD Workshop entries use the submission ID and original title; Book Forum entries use the complete book title.
- Open an available task, review its instructions, and save or submit the requested information and files. The dashboard shows the resulting status and recent activity.
- Return when the proof stage is released and when preparing the conference presentation. Review session details, download the relevant templates, and upload or resume the presentation file.
Task availability follows the conference’s current settings.
Development contribution
I designed and developed the system as ACADIA 2026 Technical Chair, translating the conference’s publication and participation requirements into connected data records, task interfaces, and file-handling workflows. The work combined interface design with operational infrastructure: a consistent submission identifier connected activities that otherwise involved separate forms, folders, and correspondence.
The conference website and this project page embed the same deployed application. Updates to its workflows and records remain centralized in the working system.
