-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quick answers - map content to new site for 3 sections #2402
Comments
I set up the chart and got started mapping content today. Looking to pick back up tomorrow. 🔒 https://docs.google.com/spreadsheets/d/1FzteENgtmXJUcPgVZDwdtG6a-xuouVXTjl_jSrY863Q/edit?usp=sharing 🔒 |
Finished the quick answers inventory. If you'd like different links, feel free to update! @dorothyyeager I have a couple of questions about what we should do next. I'm not 100% sure what the redirect strategy should be. Structure of quick answers section:
Are we able to redirect anchor links? Or can we only redirect the main link? |
I think we need to check with @patphongs on the redirecting anchor links question. I looked at the code for our current redirects and we have one written (seems to be done properly) for https://transition.fec.gov/ans/answers_compliance.shtml#embezzlement1 but it doesn't seem to work. (It's supposed to redirect to https://www.fec.gov/help-candidates-and-committees/keeping-records/misappropriated-funds/.) |
Good to know. Thanks for following up with Pat on this. It looks like we'll have to make general redirects for each of the sections. I have suggestions for those in the spreadsheet as well. |
Redirect plan:
Additional work:
|
Planning and research work is finished. Redirect implementation issue is at #2425. Closing issue. |
We're looking at what to do with "quick answers" section on old site & transition. Before redirecting these three sections, we need to make sure that all of the information in the sections are on the new site somewhere.
Quick answers sections to map to new site:
To do:
The text was updated successfully, but these errors were encountered: