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

improve the presentation of legacy events #292

Closed
bridgetkromhout opened this issue May 8, 2016 · 2 comments
Closed

improve the presentation of legacy events #292

bridgetkromhout opened this issue May 8, 2016 · 2 comments

Comments

@bridgetkromhout
Copy link
Collaborator

I went with a fast-and-hackish way of getting ~51 event migrations finished in an afternoon; I imported the old index.html pages into welcome.md via the files I added in #290 used thusly:

for foo in $(cat events-to-migrate);do echo $foo | ./migrate-events.sh;done

I deleted the files for the ones that didn't happen: e40512c

I then viewed the start dates from the webby directory:

$ pwd
/Users/bridget/github/devopsdays-webby/site/content/events
Bridgets-MacBook-Air:events bridget$ more */_event_date_start.txt 

and manually edited the start and end dates into the yaml:

for foo in $(cat events-to-migrate);do vi data/events/$foo.yml ;done

Yes, that kinda sucked. No, there was no reasonable way to get that data from the inconsistently-set-up date files.

. Known side effects:

  • Lots of broken images (their paths are mostly relative and need to be absolute)
  • without the "OLD" (or equivalent text), the imported text showed as blank. (That could be sedded out to something less visible.)
  • Currently a bunch of cruft shows:

screen shot 2016-05-07 at 10 22 07 pm

I would be fine with any additional migration option that preserves as much history as possible while de-duplicating sponsor images that make the repo too big.

I regard this as temporary so we don't have to have too many old events offline for any amount of time. I think real migration/de-duplication/binary-delete of a given event's extraneous logos would still be ideal.

@bridgetkromhout bridgetkromhout added this to the Future Enhancements milestone May 8, 2016
@bridgetkromhout bridgetkromhout changed the title improve the migration of the legacy events improve the presentation of legacy events May 8, 2016
@mattstratton
Copy link
Member

This will be handled by the redirect setup from #854

@mattstratton
Copy link
Member

This should be resolved; there may be some DNS cache issues for the next few days, but all the legacy stuff shoudl be displaying properly now.

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

No branches or pull requests

2 participants