Closed (fixed)
Project:
DrupalCamp Colorado
Version:
7.x-5.x-dev
Component:
Website
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Feb 2017 at 22:08 UTC
Updated:
13 Sep 2017 at 15:11 UTC
Jump to comment: Most recent
Comments
Comment #2
proofoftom commentedFrom @matthews "Any way we can convert old sites to be flat archives easily? Perhaps install boost and grab the static files?"
For the 2016 (7.x-4.x) site, let's install https://www.drupal.org/project/boost and https://www.drupal.org/project/static to convert the site to HTML.
Comment #3
gregglesAnother solution is listed in https://www.drupal.org/node/27882
Also, it should ideally be archived on drupal.org as was done in https://www.drupal.org/node/2761033 for the 2016 new jersey site.
Comment #4
switzernComment #5
gregglesHi switzern - I'd be happy make an archive of the 2016 and 2017 sites to host them on d.o which was suggested in #2/3, so reopening and retitling.
It seems there's a problem with the d.o archive sites right now: https://www.drupal.org/node/2908287 but once that's fixed I can do this.
Comment #6
larsdesigns commentedgreggles: Here is the URL to the archive: https://github.com/larsdesigns/2016.drupalcampcolorado.org. The static site is also being hosted on github.com at the URL: http://2016.drupalcampcolorado.org.
Comment #7
larsdesigns commentedgreggles: Here is the URL for the 2017 static archive: https://github.com/larsdesigns/2017.drupalcampcolorado.org. I am working on the Github Pages hosting in issue: https://www.drupal.org/node/2908337.
Also, the archives are available on the Drupal Camp Colorado Github account: https://github.com/DrupalCampColorado. I am planning to switch the hosting over to that account to make it feel more community accessible.
Comment #8
gregglesThat's great news. Thanks for your work on those, Justin. It seems ideal to me to host these on drupal.org vs. github. Any reason you prefer github?
Comment #9
larsdesigns commentedgreggles, it seems ideal to me also and that was my initial intention. When creating the hosting issue, Github is a good place to complete steps two (part 1), three, and four of the hosting issue requirements as found: https://www.drupal.org/drupalorg/docs/drupalcamp-sites-archive#how-to-host.
2. Github provides the place to download the archive from.
3. Github Pages allows the community members to test and review the static pages of the archived site.
4. Test and confirm that the forms are disabled.
Also, could there be SEO considerations when keeping the sites at their original domains?
Comment #10
gregglesThanks, Justin!
On the last point about SEO, I believe the best solution is to do a 301 redirect from the old subdomain to the new camps location.
Comment #11
larsdesigns commentedCreated issues to post static archives to the Drupal Camp site archive page: https://www.drupal.org/drupalorg/docs/drupalcamp-sites-archive
2017.drupalcampcolorado.org
https://www.drupal.org/node/2908418
2016.drupalcampcolorado.org
https://www.drupal.org/node/2908420
2015.drupalcampcolorado.org
https://www.drupal.org/node/2908421
2014.drupalcampcolorado.org
https://www.drupal.org/node/2908422
Comment #12
switzernNice - thanks larsdesigns and greggles! Let me know if there's anything I can do to help.
Comment #13
switzernShould we go ahead and close this issue in favor of https://www.drupal.org/node/2908337?
Comment #14
greggles@switzern - yep, agreed this issue is fixed and the other is good for tracking the archiving.
Comment #15
switzernSounds good.