This interacts badly with the "focal point scale and crop" effect; I
think that if we start by downscaling a large image, the position of the
saved focal point still refers to the original image rather than the one
that results from the first effect.

I think the presence of this effect on the style is just a hangover from
my earlier attempts of how I thought this style should behave. Note this
also means this style works more closely to the other styles we
implement in this module.

moved to
ucam_profile@f16a456e

We manage this in our teaser templates, to allow us to make use of the
optional 'teaser link' on a node.

This leads e.g. to default and unwanted read more links being added to
teasers. We'll manage our own links.

Having removed the left nav bar, see

pl9nav@8ffeccd7
pl9@369dc021

we now often have pages on microsites that have a full 12-col content
region rather than 9-col. Rendering the leading images at full height
often leads to them being far too big.

I've gone for 432 rather than 288 for the height because 1177x288 is
quite an extreme aspect ratio which makes it increasingly difficult for
content editors to find good images.

We use specific carousel_itme bundle type for carousel purposes.

In 946132d0 I manually edited yaml when switching from body to
field_summary. But, I entirely removed the settings key from what used
to be body rather than setting it to an empty array. This causes
multiple errors to be thrown because core assumes that 'settings'
exists.

Having switched to ucam_profile we don't deploy the core search module.

I'm not sure where the local_tasks blocks are/were coming from. They
don't appear in the block placement GUI on a site built from
ucam_profile so let's take them out of the list of blocks to remove and
see what happens.

This reverts commit 8ae15bfe.

I thought this was being provided by the standard profile, but the
config object is provided by the core node module.

More work to move away from using the default body field.

Previously assumed to have been installed by the standard profile. No
longer true with ucam_profile.

I should probably move all the display mode definitions to the profile.
Perhaps once I've made our standard site setup work with it..

This presumes we are being installed on a site that was installed
from ucam_profile

Ensures that newly created carousel item nodes are added to the
entityqueue by default.

This makes jquery.cycle interact oddly with our js which sets the width
property on slides in order to be sensibly responsive. I've not
attempted to analyse the underlying issue and am content with finding a
setting that seems to give the results I'm after (i.e. carousel loads
properly on mobile and desktop variants, and responds appropriately to a
window resize)

On D7 this was applied to the <ul> that contains the <li> elements that
constitute the individual slides.

The markup in our pl9 slideshow implementation is somewhat different.
Adding the campl-slides on the view doesn't quite map one-to-one to the
D7 use of the class but it achieves the desired results in practice.

I used the same name for the bundle and the display mode, which makes
naming templates hard given we might need to pick from:

- node--NODETYPE-DISPLAYMODE.html.twig
- node--NODETYPE.html.twig
- node--DISPLAYTYPE.html.twig

..especially when the last two are the same.

I'm renaming the view mode because we have far fewer uses of it so the
refactoring is hopefully easier.

Required as of c333488f

NB this reverts 644f81a9

Rather than trying to define everything in yml, or everything in code, I
think I get better outcomes if I:

- bootstrap minimal sensible settings via yml
- selectively update settings in hook_install

not least of all because of Drupal's firm ordering of "install config
settings from yml, then invoke hook_install".

NB minimal config here because I intend to do more in hook_install().

This reverts commits fc3d0667, cd2da89f, b630459d.

This was uninstallable due to the way the dependencies between the
various bits of config work, and the order of importing config/install
vs running hook_install.

Let's revert and try again.

In general we use a preprocess function in the pl9 theme to produce
teaser links

https://gitlab.developers.cam.ac.uk/ch/co/drupal-9/pl9/-/blob/9ad954fbfffbe6d0020658281c7fe83535ec5155/pl9.theme#L98

but the link used in carousel items is optional. Thus, we will directly
use field_link in a suitable template.

It's optional on D7, and we have plenty of sites where the carousel
items are there for visual interest only without linking to content.