Change Logo and Branding #295
-
Hi All I just want to know if we are allowed to change the images in the container (Logo and Branding) and what would be the best way to have this done? Idea is to give it a better look and feel not to pass the software off as my own. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
Definitely - I have no objections or requirements beyond what the open source licensing would enforce. It's a Rails application so it would entail modifying ERB templates and changing the assets (images & CSS) in I've thought about making the branding configurable but it hasn't been implemented yet mostly because of scope. Changing logo requires also attention to the CSS media queries which flip themes based on user preferences. For example, you could replace the images in this header file to change the logo: Then the application name and tag line are internationalized strings so you could substitute with just raw strings: There is a feature request for this filed at #248 |
Beta Was this translation helpful? Give feedback.
-
For others coming to this discussion, branding is now supported. Documentation is here: https://github.com/pglombardo/PasswordPusher/blob/master/Configuration.md#rebranding |
Beta Was this translation helpful? Give feedback.
-
Hi all - beyond the branding support that was added last year, I put together some instructions on how to download and apply any theme to Password Pusher. It's a short term work around but works well. I hope this helps! |
Beta Was this translation helpful? Give feedback.
-
Hi all - I'm updating the answer here with the latest information. As of v1.26.10 Password Pusher now
With this framework and foundation, we'll be able to make sure that future changes don't break any existing user customisations. If there are any questions or issues, please let me know! |
Beta Was this translation helpful? Give feedback.
Hi all - I'm updating the answer here with the latest information.
As of v1.26.10 Password Pusher now
With this framework and foundation, we'll be able to make sure that future changes don't break any existing user customisations.
If there are any questions or issues, please let me know!