Looks like the 2016 site was spammed: https://2016.drupalcampcolorado.org/taxonomy/term/11

Remove said spam and ensure that we have https://www.drupal.org/project/honeypot enabled and configured correctly for both the 2017 and 2016 sites.

Comments

tommycox created an issue. See original summary.

proofoftom’s picture

From @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.

greggles’s picture

Another 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.

switzern’s picture

Status: Active » Closed (outdated)
greggles’s picture

Title: Ensure honeypot is enabled and configured » Ensure honeypot is enabled and configured - put static site to drupal.org
Status: Closed (outdated) » Active

Hi 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.

larsdesigns’s picture

greggles: 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.

larsdesigns’s picture

greggles: 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.

greggles’s picture

That'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?

larsdesigns’s picture

greggles, 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?

greggles’s picture

Thanks, 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.

larsdesigns’s picture

Created 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

switzern’s picture

Nice - thanks larsdesigns and greggles! Let me know if there's anything I can do to help.

switzern’s picture

Assigned: Unassigned » larsdesigns
Status: Active » Needs review

Should we go ahead and close this issue in favor of https://www.drupal.org/node/2908337?

greggles’s picture

Status: Needs review » Fixed

@switzern - yep, agreed this issue is fixed and the other is good for tracking the archiving.

switzern’s picture

Assigned: larsdesigns » Unassigned
Status: Fixed » Closed (fixed)

Sounds good.