This document is a loose collection of standards, policies and guidelines as they pertain to The Michigan Daily Web Team. Think of this as the catch-all bucket for things we should have written down somewhere, but we are too lazy to sort into useful categories.

Bylines and Credits

If you contributed significant research / analysis / writing to a piece, you get a byline. (Would this piece exist without the analysis?)

If you only created a graphic, you don't get a byline, but you get graphic credit.

If you contributed some research / analysis / writing, but not essential to the story, you get contributor credit at the bottom of the piece (e.g. "Naitian Zhou contributed to this piece.")

Developers for special projects get “Developed by…” after the bylines, e.g.

By Michigan Daily Staff
Developed by Rimaz Khan

Naming Schemes

tl;dr: lower-case-dashes

Github

For repositories, use lowercase with dashes, e.g.:

https://github.com/michigandaily/lower-with-dashes/

Additionally, use liberal use of tags:

• #dataviz for cookie-based data graphics

Slack channels

Try to also stick with lowercase with dashes. If possible, refrain from creating a new channel every year (bad: #web-pm2021; good: #web-pms). Prefer to add / remove users instead of creating new channels.

AWS

Name resources after the project. If that is ambiguous, use the naming scheme projectname-descriptor (e.g. adportal-backend, adportal-frontend, adportal-storage).