Who has control over the druid.io domain? Charles would that be you? We'd need support from them for the DNS redirect.
On Tue, Mar 5, 2019 at 2:04 PM Jonathan Wei <jon...@apache.org> wrote: > We still need to complete the website migration to Apache infrastructure. > > I'll propose the following plan: > > Proposed Apache Druid website migration plan > ======================================== > > These links have some previous discussion on the website migration: > > > https://lists.apache.org/thread.html/7cae100b684e0b33e0adda993efea3d6088978700988a0ae632fdd80@%3Cdev.druid.apache.org%3E > https://issues.apache.org/jira/browse/INFRA-17340 > > From the discussions above, the recommendation is to have 2 separate repos > for the website: one for source and another for built content that will be > served. > > Generating site files > ======================= > > The Apache site update process will be similar to our current process. > > Current process: > 1. Push changes to https://github.com/druid-io/druid-io.github.io/tree/src > 2. metamx bot picks up changes, builds, and commits to > https://github.com/druid-io/druid-io.github.io/tree/master > 3. https://github.com/druid-io/druid-io.github.io/tree/master is served by > github pages > > Apache process: > 1. Push changes to https://github.com/apache/incubator-druid-website-src > 2. Jenkins bot from Apache will build the website from source repo, commit > to https://github.com/apache/incubator-druid-website > 3. Apache Druid website will be served from the content in > https://github.com/apache/incubator-druid-website (asf-site branch) > > > Hosting and SEO > ================ > > The Apache site will be hosted at druid.apache.org on Apache > infrastructure: http://www.apache.org/dev/project-site.html > > To preserve our search rankings, we can setup 301 redirects from the old > druid.io site to the corresponding pages on the druid.apache.org site. ( > https://moz.com/learn/seo/redirection) > > However, Github pages (which currently hosts the druid.io site) does not > support 301 redirects, so we propose the following: > - Setup a new Nginx server that will perform 301 redirects to > druid.apache.org for the druid.io. Imply can host this if needed. > - Update the druid.io DNS entry to point to this new Nginx server > - Shut down Github pages hosting for druid.io > > In addition, we can also set canonical tags on our pages: > https://moz.com/learn/seo/canonicalization > > > Action items > =============== > - Setup a Jenkins bot that builds the Apache website content from source > - Get the Apache website up > - Setup Nginx redirect server for druid.io > - Shutdown github pages and redirect DNS for druid.io to Nginx redirect > server > - Add canonical tags to pages >
