Impacts of changing repo name

[dan-bowerman]

Links on every Storylines product contain a link back to this repository, which is still called story-ramp.

How much headache would it cause to rename this repo to storylines?

[yileifeng]

An update across all schema and type interfaces to storylines would also be nice to include in this issue (e.g. StoryRampConfig).

[spencerwahl]

Potentially non-exhaustive list of things that would be affected:

• Prod storylines links that you mentioned
• Marketing site link?
• Need to update local repos with new URLs

We may need to also rename our forks, unsure if github handles those at the same time.

I don't think its a huge headache but probably want to time it with a storylines release so that the links dont break for a long period of time.

[james-rae]

Another idea to mitigate the need to update links in every existing product.

1. Rename the repo.
2. Fix everything "buildy" (e.g. update or re-clone forks, setup new npm, point Respect to new npm).
3. Update Storylines source so every fresh build has github link pointing to proper repo.
4. Make new repo called story-ramp. It contains a readme saying "we've moved, click here" with link to new repo.

Over time every site that gets updated will have the correct link. But in the interim, or for a site that never gets updated, the curious clicker will still end up where they want to go, just with an extra page hop.