Skip to content
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.

Plan for the site's post-launch maintenance and ownership #94

Open
5 tasks
willcahoe opened this issue Apr 10, 2018 · 5 comments
Open
5 tasks

Plan for the site's post-launch maintenance and ownership #94

willcahoe opened this issue Apr 10, 2018 · 5 comments
Assignees

Comments

@willcahoe
Copy link
Collaborator

Tasks

  • Develop a cadence for how often the site should be updated
  • Identify roles and responsibilities
  • Estimate how much of a time commitment will be required to maintain the site
  • Contingency planning: site is down, emergency content updates, who holds the keys, etc.

it's done when …

  • The person or people who will be responsible for the site's post-launch stewardship understand what is expected of them
@willcahoe
Copy link
Collaborator Author

Does anyone know if there is an TTS-specific "how to keep a website alive and thriving" playbook? If not, is there something similar from outside sources that someone can recommend?

@carodew
Copy link
Contributor

carodew commented Apr 10, 2018

I am not aware of any but it would be a great thing to ask some of our product folks and gather/share what comes out of it, although for something as simple as our site is, I'm guessing you've covered all the bases in your checklist above.

@willcahoe willcahoe self-assigned this Apr 13, 2018
@willcahoe
Copy link
Collaborator Author

I'm going to pause this one until we can see the status of the site on Launch day and figure out what further work needs to happen

@RyanSibley
Copy link

@willcahoe When you have time, we should have a work session where we establish the work flow for updating content, etc.

@willcahoe
Copy link
Collaborator Author

@RyanSibley That would be extremely helpful to me, I'm in

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants