Remove the config of /news-tv-and-events/ from news page set up in platform about campaign HOT 11 CLOSED

As proposed in planning - articles will inherit the category into the url (but not /article)
e.g. /new /press-release

from campaign.

It turns out that the overview page itself (the news landing page) is a landing page that can be controlled by the editor using pathauto, and the path can be changed.

One problem however is that the article itself by default uses this pattern for the URL

pattern: '/news-tv-and-events/news/[node:title]'

(see https://github.com/comicrelief/campaign/blob/develop/modules/cr_article/config/install/pathauto.pattern.article.yml#L9 for the code)

This means, while we can control the article landing page URLs, the article node page itself by default will use the above pattern. An editor can overwrite this on a node-by-node basis however.

Having different patterns in different sites will be messy I think, so I'd rather have us keep this as the default state. Can we not find a URL pattern that works for all sites @CarolineRennie?

from campaign.

I guess the most logical thing is to just have all articles to have /news/[node:title] but then this only works for news - if we are using articles for press releases then I guess the pattern needs to relate to the use of the article.

E.g. if we are applying the exclude from 'all' logic for things like press releases or grants initiatives then these should inherit press-release/[node:title] or grants-initiative[node:title]

from campaign.

We need to find a generic pattern here, as using press-release/[node:title] would mean all articles now will change their paths to something like first-taxonomy-term/[node:title], as press-release is just a tag on the article, much like TV, appeal-films etc. This means also these articles would read tv/[node:title] etc. which I think wouldn't work.

Alternatively, we need to look at a different way, e.g. an article type, and a pattern could be like /article/[article-type]/[node:title], so you'd have:

• /article/press-release/title-of-the-press-release
• article/general/title-of-the-article

It'd be simpler to not add any type to the articles, and always go with the article_or_news/[node:title as you say, then have different landing pages under different URLs (e.g. news landing page, press release landing page, ...)

from campaign.

Would article type not make the 'only display here' rules a bit more simple though?

In that the rule would be only display article type X rather than looking at categories? I think that this may be the rule on current CR.com so maybe it's an antiquated way of thinking?!

from campaign.

why do we need different url?
Do we know which kind of articles are gonna need? and what make them different?

from campaign.

Only apply URL change for the 2 article 'Types':
/news/
/press-release/

from campaign.

As discussed with @gusliedke
Content manager user flow would be:

1. Create article
2. Select 'category' (news or press release) from drop down
3. Tag article with terms for SEO and search terms (Grants, Women and Girls, Sara Cox, Whatever)

Display rules:
Url to inherit the Category /press-release/[article name]
"Related news" defined by closest tag matches between articles of the same Category (e.g. only news articles or grants initiatives, not a mix of both)

from campaign.

When we have done this work we need to update our "Paragraph Feature Articles" to filter by tag instead categories. The category will be always News. Ping me to explain it.

from campaign.

@bimsonz @pvhee just double checked with Caroline and the task is how we described here. This issue is the one with highest priority now. I was wondering Zach if you would be able to pick it up?

from campaign.

@gusliedke @CarolineRennie picking this one up now!

from campaign.