Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shut down public view of WC blog #635

Closed
1 task done
jennpb opened this issue Mar 1, 2017 · 14 comments
Closed
1 task done

Shut down public view of WC blog #635

jennpb opened this issue Mar 1, 2017 · 14 comments
Assignees

Comments

@jennpb
Copy link
Contributor

jennpb commented Mar 1, 2017

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

  • In Drupal, replace all blog references with corresponding next. link
    - [ ] Redirect DNS
@jennpb jennpb added the backlog label Mar 1, 2017
@jennpb jennpb added this to the Explore section (R2) milestone Mar 9, 2017
@jennpb jennpb removed the backlog label Mar 9, 2017
@jennpb
Copy link
Contributor Author

jennpb commented Mar 21, 2017

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:

  • with 0 associated posts
  • slight variations of other tags
  • a few incomplete/misspelled
  • with overlaps of Categories (e.g. when a blog post is assigned the same tag and category)

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?

@jennpb jennpb self-assigned this Mar 21, 2017
@dannybirchall
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor

@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
Copy link
Contributor Author

jennpb commented Mar 21, 2017

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
Copy link
Contributor Author

jennpb commented Mar 21, 2017

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
Copy link
Contributor

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

@jennpb
Copy link
Contributor Author

jennpb commented Mar 21, 2017

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
Copy link
Contributor

dannybirchall commented Mar 21, 2017 via email

@jamesgorrie
Copy link
Contributor

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

@jamesgorrie
Copy link
Contributor

jamesgorrie commented Mar 27, 2017

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
Copy link
Contributor Author

jennpb commented Mar 28, 2017

@jamesgorrie Yes to that ^

@jennpb jennpb removed this from the Explore section (R2) milestone Mar 31, 2017
@jamesgorrie
Copy link
Contributor

We can't forget about the RSS!

@jennpb jennpb changed the title Shut down WC blog Shut down public view of WC blog Apr 24, 2017
@jennpb jennpb closed this as completed Apr 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants