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

Add Worldwide Corporate Information Page content item #2399

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

jkempster34
Copy link
Contributor

@jkempster34 jkempster34 commented Jun 8, 2023

Note
I'll add an example later!

Currently, the corporate information pages associated with worldwide
organisations are published as placeholder content items.

This creates a new content item for them.

The existing content item for corpoarate information pages could be used
instead. However:

  • We require a link to the associated worldwide_organisation. Having a new
    content item means that we don't have to attach multiple optional links to the
    corporate information page content item.
  • We will need a new template for this page in government-frontend as the
    worldwide organisation corporate information pages are quite different when
    compared to the organisation corporate information pages. Because
    government_frontend maps content items to templates through their
    schema_name (except for a few exceptions), it would make sense to follow this
    pattern.
  • Many of the attributes of the corporate information page schema are not
    needed in order to render the worldwide organisation corporate informaiton pages.

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

This application is owned by the publishing platform team. Please let us know in #govuk-publishing-platform when you raise any PRs.

Follow these steps if you are doing a Rails upgrade.

Currently, the corporate information pages associated with worldwide
organisations are published as `placeholder` content items.

This creates a new content item for them.

The existing content item for corpoarate information pages could be used
instead. However:
- We require a link to the associated `worldwide_organisation`. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in `government-frontend` as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  `government_frontend` maps content items to templates through their
  `schema_name` (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton pages.
Copy link
Contributor

@chrisroos chrisroos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍

@jkempster34 jkempster34 merged commit 212f23a into main Jun 12, 2023
@jkempster34 jkempster34 deleted the add-ww-cip-content-item branch June 12, 2023 09:22
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 12, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 13, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/government-frontend that referenced this pull request Jun 13, 2023
We have added a new content item to represent Corporate Information Pages that
are associated with Worldwide Organisations 
(alphagov/publishing-api#2399).

Because the Worldwide Corporate Information Pages have a link to their
Worldwide Organisation, much of the rendering code added for Worldwide Offices
and Worldwide Organisations works with this page.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 14, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 14, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 14, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/government-frontend that referenced this pull request Jun 14, 2023
We have added a new content item to represent Corporate Information Pages that
are associated with Worldwide Organisations
(alphagov/publishing-api#2399).

Because the Worldwide Corporate Information Pages have a link to their
Worldwide Organisation, much of the rendering code added for Worldwide Offices
and Worldwide Organisations works with this page.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 26, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 26, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 26, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 27, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
brucebolt added a commit to alphagov/content-data-api that referenced this pull request Jun 27, 2023
The Worldwide Corporate Information Page schema was added in
alphagov/publishing-api#2399.

This adds that schema type to this application.
jkempster34 added a commit to alphagov/government-frontend that referenced this pull request Jun 27, 2023
We have added a new content item to represent Corporate Information Pages that
are associated with Worldwide Organisations
(alphagov/publishing-api#2399).

Because the Worldwide Corporate Information Pages have a link to their
Worldwide Organisation, much of the rendering code added for Worldwide Offices
and Worldwide Organisations works with this page.
jkempster34 added a commit to alphagov/whitehall that referenced this pull request Jun 28, 2023
Following the work to add a new content item
(alphagov/publishing-api#2399) and move over the
rendering of the worldwide corporate information pages
(alphagov/government-frontend#2824), we can switch the
rendering of all of these pages to government-frontend.

This includes the "about us" CIPs, which are published as placeholder content
items (see #7844), these now show a 404 page as desired.
ryanb-gds pushed a commit to alphagov/whitehall that referenced this pull request Jun 28, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
syed-ali-tw pushed a commit to alphagov/whitehall that referenced this pull request Jun 28, 2023
We have decided to publish the Corporate Information Pages associated with
Worldwide Organisations as a separate content item
(alphagov/publishing-api#2399) for the following
reasons:
- We require a link to the associated worldwide_organisation. Having a new
  content item means that we don't have to attach multiple optional links to the
  corporate information page content item.
- We will need a new template for this page in government-frontend as the
  worldwide organisation corporate information pages are quite different when
  compared to the organisation corporate information pages. Because
  government_frontend maps content items to templates through their
  schema_name (except for a few exceptions), it would make sense to follow this
  pattern.
- Many of the attributes of the corporate information page schema are not
  needed in order to render the worldwide organisation corporate informaiton
  pages.

This adds a presenter for the new content item. Any shared attributes are DRYed
up through a shared PayloadBuilder.
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

Successfully merging this pull request may close these issues.

2 participants