Clone 2017.drupalcampcolorado.org to drupalcampcolorado.org

Hi Juaneclark,

Thank you for the questions. I will clarify.

1. No, we are only dropping the year from the "Pantheon project name" not the domain. Sites for the previous years will remain hosted on Github Pages in their current static condition.
2. To build a new site in Drupal 8, start a new project on Pantheon for it.
3. This change has nothing to do with SSL certificates. We will continue to use the SSL that is offered.

To be clear this change is only an internal process change to save (me) a bunch of time. In the past years I left the old sites running on Pantheon and I provided the security updates. I would clone the site from last year (make a new Pantheon project for the next year) and the team would get to work on it.

Last spring I created static versions of all the past sites (https://www.drupal.org/node/2886290) and hosted them on Github. I have already created the static archive for the 2017 site and hosted it on Github. Pending DNS updates before we take down the 2017 Pantheon site down.

The change will be for the future years. We will create the static archive of the previous year right away and use the same Pantheon project for the next year.

Instead of cloning the site from previous year into a new Pantheon project where I would have to configure backups, new SSL, invite the team etc... This will save a bunch of time and prevent development delays. The web team would perform all of the same tasks like changing the theme, cleaning off the old users, updating content etc. The subdomain would advance to the next year (2018.drupalcampcolorado.org) for next year, the year after that would be 2019.drupalcampcolorado.org and on.

Effectively, there is no visible change for the web team or the users. It just saves me needless labor hours of cloning, configuration and maintenance of the old sites and it make is easier for the web team can get to work on updating the existing site for the next year.

Keep in mind that the wheels are also in motion to host the static sites on the drupal.org infrastructure: https://www.drupal.org/node/2908337#comment-12256468. The domain would be different and it is at our discretion if we want to end the Github Pages hosting using our *.drupalcampcolorado.org domain. The drupal.org infrastructure folks recommend we use a 301 redirect to their URL.

1. Completed the clone of the 2017.drupalcampcolorado.org site on Pantheon and sent out invites to existing web team. If there is anyone out there who wants to be added, please post a request here.
2. Completed the static archive 2017.drupalcampcolorado.org and posted it to Github Pages for hosting.
3. Created an issue for hosting the Archive on drupal.org: https://www.drupal.org/node/2908418
4. Sent a request to Joel by e-mail to make the DNS updates for the 2017.drupalcampcolorado.org Github pages hosting.

When the DNS is complete for the static site, I will take down the 2017 site.

When the DNS task is complete, I will take down the 2017 Pantheon project and close this issue.

@switzern, I added you to the Pantheon team.