search

wellcomecollection / wellcomecollection.org

🪟 Wellcome Collection's website and services that support it
https://wellcomecollection.org
MIT License
39 stars 5 forks source link

Shut down public view of WC blog #635

Closed jennpb closed 7 years ago

jennpb commented 7 years ago

Phase 1: Continue to use blog for content management, use it as a redirection service

jennpb commented 7 years ago

For the first phase of decommissioning Wordpress, we need to redirect all blog posts, categories, pages to a corresponding place on next.

About pages: /about and /about/terms-and-conditions - 404

Date pages: /date/YYYY/MM/DD/slug becomes /articles/slug

Categories There are 47 of these in Wordpress, one of which has already been mapped to /series/a-drop-in-the-ocean. Following that logic, all /category/slug/slug should map to /series/slug.

Whitelist all parent and child categories Exclude /category/uncategorized

All series require a brief summary, so this is something for @dannybirchall's team! Not urgent, but should be done as/when a series is highlighted on Explore.

Tags We have 2400+ unique tags, including tags:

I would suggest we leave /tag/tagname without a correponding URL on next. until such a point when we decide how to deal with this taxonomic problem (also taking into account Library blog if necessary).

@jamesgorrie does all this make sense?

dannybirchall commented 7 years ago

Content tasks noted, ta.

From a CMS editing perspective, we'll also need to add exceptions for URLs with /stats /posts etc

(it can also get complicated bc there's some functionality that's also available directly at blog.wellcomecollection.org when you're logged in)

We could add IP-based exceptions for when we're in the building, at least?

jamesgorrie commented 7 years ago

In Drupal, replace all blog references with corresponding next. link

I'm not 100% sure what you mean by this?

Redirect DNS

Let's not have this as a task as it's probably not going to be that, but rather building a router service or the likes.

About pages 404

We do have pages like this - would the better option not be to redirect to whatever page we think is most appropriate.

I would suggest we leave /tag/tagname without a correponding URL on next.

We could potentially have a stopgap of having a next.wc.org/search?q=tag:tagname, but let's see how often the tags are used.

jamesgorrie commented 7 years ago

@dannybirchall

We could add IP-based exceptions for when we're in the building, at least?

I'm not sure I 100% see where you would want this?

jennpb commented 7 years ago

In Drupal, replace all blog references with corresponding next. link

I'm not 100% sure what you mean by this?

Ignore this! I thought we'd talked about changing links on wc.org where they occur, but we don't have to worry if we're redirecting to next. URLs.

Redirect DNS

Let's not have this as a task as it's probably not going to be that, but rather building a router service or the likes.

Noted and struck out

About pages 404

We do have pages like this - would the better option not be to redirect to whatever page we think is most appropriate.

Could do. Will we then redirect the redirect if we totally revamp/rename the section About lives in?

jennpb commented 7 years ago

I would suggest we leave /tag/tagname without a correponding URL on next.

We could potentially have a stopgap of having a next.wc.org/search?q=tag:tagname, but let's see how often the tags are used.

'How often the tags are used' - There's no way for us to see this data from WP Stats so I don't know how often they're used. I think it's ok to have the stopgap as you suggest but would that mean having index pages as well?

jamesgorrie commented 7 years ago

@jennpb Are the stats maybe available on the /stats endpoint (that I can't find) that @dannybirchall is talking about?

jennpb commented 7 years ago

No, that's where I'm looking. I've exported a CSV of all pages accessed in ALL TIME and I can't see any evidence that it's counting /tag/tagname. Posts and Pages only.

dannybirchall commented 7 years ago

Editorially, I'm reasonably relaxed about anything that isn't an actual post redirecting to /explore

-------- Original message -------- From: jennpb notifications@github.com Date: 21/03/2017 17:16 (GMT+00:00) To: "wellcometrust/wellcomecollection.org" wellcomecollection.org@noreply.github.com Cc: Danny Birchall d.birchall@wellcome.ac.uk, Mention mention@noreply.github.com Subject: Re: [wellcometrust/wellcomecollection.org] Shut down WC blog (#635)

No, that's where I'm looking. I've exported a CSV of all pages accessed in ALL TIME and I can't see any evidence that it's counting /tag/tagname

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/wellcometrust/wellcomecollection.org/issues/635#issuecomment-288151354, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADluTnbQNNBrGleSk9e0IOB2jXf-a-I-ks5roAXJgaJpZM4MP_28.

This message has been scanned for viruses by Websense Hosted Email Security - www.websense.com

jamesgorrie commented 7 years ago

@jennpb re: about pages. Do we want to just redirect those two pages to: https://wellcomecollection.org/what-we-do

jamesgorrie commented 7 years ago

Or: https://blog.wellcomecollection.org/about/ => https://wellcomecollection.org/what-we-do/about-wellcome-collection https://blog.wellcomecollection.org/about/terms-and-conditions/ => https://wellcome.ac.uk/about-us/terms-use

jennpb commented 7 years ago

@jamesgorrie Yes to that ^

jamesgorrie commented 7 years ago

We can't forget about the RSS!

jamesgorrie commented 7 years ago

RRS

Content