Use netlify! Or s3 bucket w hosting
Tiny websites are great
201–210 of 227 posts
Re: Tiny websites are great
#202Re: Tiny websites are great
#203Re: Tiny websites are great
#204I was nodding reading this and then: > No libraries or frameworks (the exception being analytics) There has got to be a better way of collecting analytics than to inject a bunch of crappy JS from some company (probably Google).
Re: Tiny websites are great
#205https://whoami.dijksterhuis.co.uk
- Pure html and CSS (except embedded iframes like soundcloud).
- hosted on GitHub.io
- domain name from AWS
Only "server side" thing I had to do was put a special file in the GitHub repo.
Super cheap too. I have a free pro GitHub account (student ftw) so the only real cost is the AWS hosted zone for dijksterhuis.co.uk
I also have subdomains I set up for machines I SSH into because I'm that lazy.
Re: Tiny websites are great
#206Re: Tiny websites are great
#207Re: Tiny websites are great
#208Earlier quoted context omitted.
There are also "tiny" solutions for analytics. I'm working on Plausible Analytics which is only 1.4 KB right now and provides a modern dashboard. It also doesn't use cookies and doesn't collect personal data so you're not required to show the cookie/GDPR prompts which would make tiny websites much less tiny. See https://plausible.io/ There's an issue on our Github which will help us perhaps reduce it to under 1 KB to…
You claim that using your analytics doesn't require user consent: > "Plausible does not use cookies and does not collect any personal data. This makes us compliant with the different cookie laws and privacy regulations. It means that you are not required to annoy your visitors with a cookie notice if you’re using Plausible analytics." [1] > "Compliant with privacy regulations: Google Analytics places cookies and coll…
Instead of setting a cookie with a unique user ID, we simply count the number of unique IP addresses that accessed your website to determine the visitor count.
To enhance the visitor privacy, we don’t actually store the raw visitor IP address in our database or logs. We run it through a one-way hash function to scramble the raw IP addresses and make them impossible to recover.
To further enhance visitor privacy, we add the website domain to their IP hash. This means that the same user will never have the same IP hash on two different websites. If we didn’t do this, the hash would effectively act like a third-party (cross-domain) cookie.
Network Address Translation allows many unique users to share the same public IP address. For this reason we also add the User-Agent string to the hash, although we don’t store the actual User-Agent string.
Re: Tiny websites are great
#209Earlier quoted context omitted.
I don't understand why changing a title tag would require any code. Is it the framework or the code? (I don't know Vue, but this smells a bit.)
It's not about Vue (or React for that matter). Incompetent developers will take whatever tools they have at their disposal and turn a few hours project into an unmaintainable monstrosity.
Re: Tiny websites are great
#210>“ Things have really changed since I began learning, and rightly so. Instead of coding in plain HTML, CSS and JS, I'm now using endless frameworks, modules and libraries to build increasingly more complex web and mobile applications. It's great, if I didn't use these tools my code would be an unmaintainable mess.” How sad that this has become the widely accepted narrative. There’s a lot of value right now in NOT bui…
From my experience complexity often hides hidden and undocumented requirements, which will only become apparent after the complexity is removed. However, I've also seen simple pages that are line by line copies of tutorials for whole sites, pared down to a single page. Frameworks aren't bad, unstructured working practices and environments often breed this sort of toxicity in code.