Hi all - the new documentation set is getting very...
# infrastructure
c
Hi all - the new documentation set is getting very close, when I say very close, we're ready to merge. It would be nice to archive the old site. Is there appetite to stash this or have it sitting somewhere? A branch? A tagged version? Another repository? A Netlify site? Also, do you have a preference for redirects? We have a loose map of old and new pages (full credit to @James Fellows Yates for keeping track), which we can use to capture 80-90% of pages without too much fuss.
woohoo 1
m
we can have it as a branch and make a deployment from there
j
My only fear is someone would go and start editing that
c
Branch protection?
m
we can have branch protection on it 😉
🦥 1
j
I liked the GATK approach of copying all the markdown files to a separate repo, and then archive it. Also because then it's a a less nice experience (not rendered) so discourages people to look at it 😉
m
for redirects, I would put them inside the netlify _redirects file
👍🏻 1
j
But #C078586GZ5X