Skip to content
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

Add press resource files to /resources/ content-s3 bucket #3451

Closed
3 tasks done
Tracked by #138
patphongs opened this issue Jan 7, 2020 · 1 comment · Fixed by fecgov/fec-proxy#170
Closed
3 tasks done
Tracked by #138

Add press resource files to /resources/ content-s3 bucket #3451

patphongs opened this issue Jan 7, 2020 · 1 comment · Fixed by fecgov/fec-proxy#170
Assignees
Milestone

Comments

@patphongs
Copy link
Member

patphongs commented Jan 7, 2020

Summary

What we're after:
We need to add press resource files which include PDF, excel, or doc files over to the content-s3 bucket under a new /press/ directory so that those files linked in press releases and digests will not be broken.

Related issues

Below is an example of linked resource files in a press release that are broken because the files don't exist in the new website structure

This is the folder directory structure that will need to be combed through to grab all the resource files from the classic server
Screen Shot 2020-01-07 at 11 47 02 AM

Completion criteria

  • Create a new press directory in the /resources content-s3 bucket found /news_releases/ directory on content-s3. Will use that instead.
  • Move any PDF, XLS, or DOC files over to the content-s3 press folder mirroring the folder structure of press[YEAR] Cross checked files for classic archive with files in content-s3 /news-releases/ directory, only needed to move over a few additional PDF files.
  • Make generic transition and www redirects for anything going to /press/press[YEAR]/*
@patphongs
Copy link
Member Author

Found press resource files within the /news_releases/ directory on the content-s3. We can redirect to those files.

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

Successfully merging a pull request may close this issue.

6 participants