Make all the site-specific labels configurable
#4 Updated by Phil Hodgson over 7 years ago
On review it seems to me that there is every reason to use the #2518 functionality to override views on a site-specific basis. The fact is that it is much more than simply the name "The PGP" and so on that need to be reviewed and re-rewritten by each site, so it seems pointless to parameterize these phrases within the views. I therefore limited my changes to the minimal ones that would remove from anything outside of the views those occurrences of certain strings identified by Joe. A much more thorough job could be done, but it will take a lot of time, and many of the non-view hard-codings of strings should actually be refactored in a more consistent way to begin with. Furthermore, we will probably change the way many enrollment forms work in a fundamental way, to make the system more dynamic and configurable, and that will be the best time to refactor all the many, many other hard-coded strings.
#5 Updated by Ward Vandewege over 7 years ago
This change is not correct; the signup path linked here should be changed to a configuration parameter that, for Harvard, will be set to
So please add a signup_link parameter to config/config.defaults.yml and set the default to '/signup'. I will override it in our Harvard deploy config to the link above. And please add a comment there that signup_link should probably be changed to the signup page for the project on the personalgenomes.org site.
Other than that, I agree with your assessment to make the changes outside views this way, and let the references to 'the PGP' etc be inside the views, since they can now be overridden via the site_specific directory.
Good to merge once the above change is made!