Track journal special issue deadlines

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -195,6 +195,32 @@ journals:
 
 **Important**: Hugo reserves the front matter field `url` as a page URL override. `generate_content.py` maps `venues.yaml:url` → front matter field `homepage` to avoid this conflict.
 
+### Journal Special Issues
+
+Journals with `submission_model: rolling` have no fixed deadlines, so WikiCFP yields nothing for them. Special issue CFPs are the only dated journal deadlines worth tracking. Add a `special_issues` list to the journal entry:
+
+```yaml
+journals:
+  - acronym: TPDS
+    # ... existing fields ...
+    special_issues:
+      - title: "Edge AI Systems: Design and Optimization"
+        guest_editors: ["Wei Zhang", "Yong Cui", "Jian Wang"]
+        cfp_url: "https://..."
+        abstract_deadline: "Aug 15, 2026"
+        submission_deadline: "Sep 1, 2026"
+        notification: "Jan 2027"
+```
+
+Special issue deadlines appear in three places:
+- **Journal page** — a "Special Issues" table below the journal metadata
+- **Calendar page** — a "Journal Special Issues" table below the conference deadlines
+- **FullCalendar grid** — events colored purple (`#7b2cbf`), titled `ACR SI — Title — deadline type`, carrying `cfp_url` in `extendedProps`
+
+Dates use the same `MMM D, YYYY` format as conference deadlines. `notification` additionally accepts month-only precision (`Jan 2027`), which lands on the first of that month in the calendar grid; the tables always print the raw string.
+
+These entries are `source: manual` by nature — WikiCFP doesn't cover journal special issues. Add them directly to `site/data/<topic>/venues.yaml`.
+
 ---
 
 ## `topics.yaml` Schema