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 editable banner to the top of the site #589

Merged
merged 4 commits into from
Jul 21, 2023

Conversation

AlanJIsaacson
Copy link
Contributor

I have tested locally with both a published banner and then a draft.

The page behaves as expected.

Miro has said that he can tidy up the inline styles for me when he is working on frontend work next week.

I have updated the background colour for WCAG AA.

Instructions for this will need adding to the Docs site too.

*
* @return array
*/
public static function getAnnouncement() {
Copy link
Contributor

Choose a reason for hiding this comment

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

On second thought @AlanJIsaacson , we should probably change this method name to something like getGlobalAnnouncement.

It will also need changing in the blade template file.

@@ -47,8 +47,30 @@


<!-- Nav bars -->

@if(
(!empty(SiteHelper::getAnnouncement()['data'][0]['status']) && SiteHelper::getAnnouncement()['data'][0]['status'] == 'published')
Copy link
Contributor

Choose a reason for hiding this comment

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

It would be useful to add a comment in here explaining what the code is for, e.g.

{{-- If the client has a global announcement published in the CMS, then output it at the top of the page --}}

@AlanJIsaacson AlanJIsaacson merged commit 347f74a into master Jul 21, 2023
2 checks passed
@AlanJIsaacson AlanJIsaacson deleted the feature/add-customisable-banner branch July 21, 2023 14:39
@portableant
Copy link
Member

This is quite useful for announcements, but if the museum is having any planned downtime for some of the internal services run off their infrastructure, you may not even get to the site. There's api driven calls to solr, a couple of proxied apis - these were too expensive to run on aws hardware at the level needed. I would suggest php artisan down and customise the view and message displayed and bring it back up after downtime. (Collections site would need same doing and is at greater risk of going down due to the api calls made.)

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.

3 participants