webconf-camera-ready
Use when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration, and the artifact-badging submission that rides along with the final files.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-camera-ready --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Web Conference Camera-Ready The 2026 notification-to-camera-ready gap was twelve days (January 13 to January 25, 2026) — short enough that de-anonymization, rights forms, registration, and artifact deposit must be prepared *before* the decision arrives. Everything below is anchored to the 2026 edition; the ACM pipeline steps are the publisher's standard flow and the WWW-specific instructions arrive by email after acceptance, so treat the sequence as fixed and the details as 待核实 until that email lands. ## The proceedings budget is a different shape Accepted papers all receive the same maximum length: **12 pages, of which 8 are content pages**, in the ACM Digital Library. Note what did *not* change from submission: the content allowance. Unlike venues that grant an extra page for addressing reviews, the 2026 Web Conference held content at 8 pages, so every rebuttal promise ("we will add baseline B to Table 2") must be paid for by cutting something. Budget the cuts when writing the rebuttal, not after acceptance. | Task | Depends on | Can be done before notification? | |---|---|---| | De-anonymized source with author block | acmart, no `anonymous` option | Yes — keep a parallel bran
- The proceedings budget is a different shape
- De-anonymization sweep
- ACM production pipeline (e-rights → TAPS → DL)
- Registration and presentation
- The artifact rider
- Edge cases the twelve days do not forgive
- Twelve-day sequence
- Output format
Sanity greps on the de-anonymized LaTeX before TAPS upload grep -rn "anonymous\|Anonymized\|redacted\|our institution" *.tex # leftovers grep -rn "\\\\documentclass" main.tex # 'anonymous' and 'review' options removed? grep -c "orcid" main.tex # one per author expected in acmart pdfinfo main.pdf | grep -i "author\|title" # metadata restored, not "anonymous"
What does the webconf-camera-ready skill do?
Use when preparing a Web Conference (WWW) camera-ready after acceptance, covering the uniform 12-page/8-content proceedings budget, de-anonymization and restored acknowledgements, ACM e-rights and TAPS production, ACM Open cost exposure, author registration, and the artifact-badging submission that rides along with the final files.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-camera-ready --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.