Closed aurel-l closed 7 years ago
Actually, I had a look at downtime.js, could you explain to me why this is there (even on the current version of the guidelines).
I see the copyright says “2013”, are we loading this script for nothing for every single request of every page at the EBI since, at least 2013? 😧
disabled the function that loads these scripts early in the dev process -- with the intention of revisiting later. Thanks for reminding!
Purpose here is to ensure the correct and latest version of the EBI scripts are always loaded.
Short version:
Tasks to do:
Have migrated downtime.js and made some initial optimisations [52d4b0d]
And has downtime.js ever been use recently? I think that every team already displays downtime information in its own way anyway and I don't remember any team or service using this prior to the “Great Shutdown of August 2016”. If this is set to remain in the codebase the possibility to use this should be more publicly communicated.
Yeah, in my 16 months at EBI, I've only know in to be used twice.
There's certainly provision to better refine and improve the value proposition of it.
I'll make a new issue that narrows to the downtime script.
The idea was to have a place that web-dev could add messages to "any page" using the template. It does this by inserting html into the DOM.
In reality it has only ever been used on /, /services, /research, /about, /industry, /support and /ebisearch.
It has been used 5-6 times in the past 3 years.
I think there's still a lot we could do here, structural changes at this level are unlikely/risky for the v1.1 release that is effectively in Release Candidate status.
Leaving as open but moving to v1.2.
We've achieved a lot at improving these scripts, and there's a separate ticket for downtime ( #26 ), so closing this one.
This script adds responsify.js and downtime.js which are not in the repo. Is that because: