Bugs, Performance & Reliability
Report bugs, performance issues, availability problems, or document update delays. Describe when it happens and how it affects publishing or legal validity.
Share your comment
Termerly creates a default project for every new user at signup, with a generated domain placeholder. Under enough concurrent load, two users signing up at roughly the same time could end up with t...
The marketing site is served from a static build by an edge layer. Both got tuned in the same pass:Third-party scripts defer at the layout level so they cannot block first paint.The edge layer got ...
The marketing site's header navigation and a few colour combinations across the layout were tripping multiple accessibility audit rules. They are now resolved:Muted text colour bumped up to clear t...
Audits on the marketing site kept flagging third-party scripts as the dominant blocker for Largest Contentful Paint. Analytics, embed snippets, tracking pixels — none of them are needed before the ...
The Legal Center got the same compression and deferral treatment the admin app already had:Static assets compress at build time, so CSS and font payloads shrink.Third-party scripts defer until afte...
On the Legal Center, the first request you make to any page used to fire a small chain of dependent queries: fetch the project, then the page, then the related metadata, then the variants. Each one...
A bundle of related perf wins for the admin app landed in one pass:Asset compression at build time on static files (CSS, JS, fonts, SVG) so the bytes on the wire shrink dramatically.The support cha...
One more layer of the sign-out cleanup: when you sign out, the service worker now force-unregisters, the cache APIs flush, and any precached offline pages get invalidated alongside the session cook...