cityofaustin / cityofaustin/techstack

Fire page migration - Serve on the Austin Fire Department Community Advisory Board

Open
#4,995 0 comments 0 reactions 0 assignees View on GitHub
Content debt Department: Fire Team: Content
Dominant language
No language data
Stars
11
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Page or pages that needs to be migrated:
Service page:
http://austintexas.gov/department/f-cab

Form:
This page has a broken link. Waiting to hear back if this advisory board still exists.

- [ ] Create pages using current content types.
- [ ] Make no additions to the text, you may delete redundant text.
- [ ] Log content debt.
- [ ] Note common term usage in the [word bank 'Monstro'](https://docs.google.com/spreadsheets/d/1gEyX6ayn1TW7CQxngsMT9pej-egMWxCtxAzRWXAeLfM/edit#gid=0).
- [ ] Create Github issues (tag as content debt).
- [ ] Record content debt in Joplin notes content debt includes: fact-checking, reading level, length, accessibility, questions about the user or the necessity of this page, user research debt, service design debt, policy lab work, and new features to dev.
- [ ] Move to review and tag another content strategist for review.
- [ ] Reviewer uses [checklist] (https://docs.google.com/document/d/1FVP_ZiQyT2P5F6GUNET327L6hyyexrkA-IzKXQjjzXw/edit#heading=h.7aga879dvzu9) for guidance.
- [ ] Reviewer documents new alpha URL in the department's inventory spreadsheet.
- [ ] Reviewer documents all newly created Contacts, Locations, documents and other snippets, if applicable

**target date: **

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Austin Fire Department Community Advisory Board source page and the issue's migration checklist; confirm whether the advisory board still exists before proceeding. Create the page with current content types, record any content debt and new content references, then use the linked review checklist and move the work to review.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.