221–227 of 227 posts
Earlier quoted context omitted.
Which is nuts, because you can also just write your own little one-liner to manipulate the title ```ts const setTitle = (t: string): void => document.title = t ```
Yeah, that would've been great but it was a shared codebase among many teams and one of the hard rules was no access to stuff like document :( We also couldn't console.log in this codebase, it was very ideologically pure but it took ages to make any changes
Earlier quoted context omitted.
Once merged and in a release, it will show up on the new project page, after selecting "create from template": https://gitlab.com/projects/new This uses their official CLI RubyGem along with the token you can get through the web interface.
In case you need some more documentation around these templates, here is our relevant docs page: https://docs.gitlab.com/ee/ci/yaml/#workflowrules-templates , sharing as a community advocate at GitLab.
Earlier quoted context omitted.
Is there a way to do time-on-page with backend-only analytics?
Answering a question with a question: Is there a better way to more-meaningfully measure "engagement" than time-on-page? Or, better yet: If it's a tiny site, do you really even have to care about time-on-page?
Is there a server-side tracking way to do it?
Earlier quoted context omitted.
If every tiny website linked to at least two other tiny web sites using something that a crawler could recognize it would be easy. Alternatively, is there a heuristic that reliably classifies websites in to tiny/not-tiny? How could we get this started?
you might want to try wiby.me
Maybe what people are really looking for is simplicity, but this changes depending on the complexity of your project. Therefore the question becomes, "What is the best level of abstraction for this project?"
That changes every time you do something new.