-
It might be sensible to make as small tweak to the wording on the PR playbook docs, on following line in Why section to make it more inclusive to wider dev community, as sometimes not just FEDs change…
-
Not namespacing stuff is a very bad practice in general. That that npm and most other tools have proper support for namespacing, we should aim to namespace every new project node-based project that we…
-
Found something interesting whilst using my templated error pages.
If `/this-will-404` is requested, all good.
If `/this-will-404.txt` is requested, the code here;
https://github.com/springernat…
-
JSCS has merged with ESLint and it seems like it's not under development any more. We should consider replacing it.
-
That is, if I open, e.g. http://www.springernature.com/scigraph/things/journal-brands/ec761180bff4f7276190f23adb4e74f9, will get RDF returned (possible after content negotiation)?
egonw updated
7 years ago
-
A while ago, when we added the [Accessibility guide](https://github.com/springernature/frontend-playbook/blob/master/practices/accessibility.md), we discussed the need for a ["Common concerns"](https:…
-
It would be good to clarify somewhere that we enforce linting of templates using for example [dustmite](https://github.com/springernature/dustmite).
This helps us prevent issues like the ones menti…
-
We seem to be using the expression `train-case` in [three different places in our playbook](https://github.com/springernature/frontend-playbook/search?utf8=%E2%9C%93&q=train-case), with the meaning _"…
-
The index has some keywords as empty:
"keywords": "///;//;///;////",
e.g. for sdata201551
-
The information is currently published on the intranet so that people inside the business can see it. Now that the Playbook is open source, perhaps we should think about moving it here instead?