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

Allow overriding / removal of OGL logo in the footer #189

Conversation

andymantell
Copy link
Contributor

As per #188, I am working on a service for which I have been asked to remove the OGL logo and message from the footer. The reason being that some of the information contains personal information such as names and addresses and is not "open". In addition, users are required to purchase the information - it is not freely available.

I have tried to follow the conventions used by the licence message in the footer but I am quite new to using the kit so not 100% sure if I have done this in the right way.

One thing I am aware of is that I might need to make a corresponding change to this file in the govuk_elements repo? https://github.com/alphagov/govuk_elements/blob/master/lib/template-config.js

@@ -110,7 +110,12 @@
<%= yield :footer_support_links %>

<div class="open-government-licence">
<p class="logo"><a href="https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/" rel="license">Open Government Licence</a></p>
<% if content_for?(:licence_logo) %>
<%= yield :licence_logo %>
Copy link
Contributor

Choose a reason for hiding this comment

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

There doesn't seem to be an obvious way to remove the logo without providing an alternative.

How would you use this in your app?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@fofr I guess I would override it with a zero length string in my local copy of this file:

https://github.com/alphagov/govuk_elements/blob/master/lib/template-config.js

Though I could be wrong. Part of the difficulty with this kind of thing is the need to target so many templating languages?! I.e. with mustache being "logicless"

Copy link
Contributor

Choose a reason for hiding this comment

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

Using an empty string doesn't feel like the right way of achieving this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@fofr I don't disagree with you, just not sure what the alternative would be within the constraints of the multiple templating languages we have to deal with?

Happy for this PR to be declined for now though until a better solution comes up...

@NickColley
Copy link
Contributor

Hey @andymantell did you manage to work around this? Want to see if we can get this resolved..

@andymantell
Copy link
Contributor Author

@NickColley Yeah I just edited the template we were using. Probably just worth declining this PR, it may only be me that even wanted this. And I don't know that my proprosed changes were necessarily the right way of doing it.

@NickColley
Copy link
Contributor

Okay, feel free to reopen if anything changes 👍

@NickColley NickColley closed this Sep 21, 2016
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