My pals in BBC World Service have been doing some awesome work on "lite" versions of their news articles (other page types to follow).
They essentially skip the Server-Side React hydration which means you end up with a simpler HTML+CSS page, no JS.
Page sizes drop significantly:
@tdp_org This makes me so happy. I still shrink and compress images all the time for email, web, etc. because 99% of the time a huge multi-megabyte image just isn't needed.
“The simplicity of HTML and CSS now feels like a radical act. To build a website with just these tools is a small protest against platform capitalism: a way to assert sustainability, independence, longevity.” — Jarrett Fuller
After several days of work, I finally pushed several commits to my website to accommodate those who rely on high contrast themes. Huge thanks to @acidiclight for helping me out by sharing a lot of feedback!
And a request to the broader community - feedback wanted and highly appreciated.
Hey @MDN, with Stack Overflow’s ongoing community implosion, now would be an excellent time to launch MDN Answers so people have a better place to help each other learn.
@liaizon honestly I'm interested in this purely just to see how badly Mastodon will muck things up if I start sending NodeBB Q&A topics as a Question activity, because Mastodon currently uses it for Polls.
But they don't have a monopoly on using it, and I can make the argument that my use case is more in spirit to the protocol 😸
Ever since I quit Google I've stopped receiving junk emails, used to come about 10 a day and would end up in promotions folder, or updates, or socials, which google created. Now, I get nothing. Only newsletters, some of which are industry related so I don't mind them. #email#google#webdev
@protonprivacy@carturo222@thunderbird My complaint is that Thunderbird doesn't handle proton folders well, and leads to a lot of clutter and more inconvenience since it creates duplicate folders under each email address
What's the simplest way to deploy a Ruby web app these days? Still Heroku? Something else?
I need a basic means of storage (database, even filesystem would be ok) and serving web requests under a domain I control.
Traffic will be low and it'll only be online for a few weeks. Low price would be appreciated but ease of use is more important. I really don't want to set up a whole server for this.
@esther might a shared hoster like https://uberspace.de work? i did use them for some “off the shelf” ruby software in the past, though not recently. definitely have very easy database and custom domain support
tegut's website continues to evolve with the expert support of #TYPO3 and the dedicated team at DMK E-Business GmbH . Discover their journey and latest enhancements in the new case study: https://typo3.com/customers/case-studies/tegut
Hmm I'm wondering if declarative Shadow DOM in Web Components would open the path to new patterns of making nicer without-JS-fallback than with <noscript> elements
But some experiment gonna be… as always… for some other days
I earn my money selling my skills to people who think they're going to make money from making a website.
My logic is that - During the California gold rush, pickaxes sellers fared much better than gold miners.
Edit: I've had various personal websites for decades. They haven't earned me a dime, directly. But indirectly, they make an amazing professional portfolio.
I know this may not answer your question, but I would suggest to flip your thinking pattern.
By creating a solution that's looking for a problem, you're likely to not add much value to a prospective customer.
Instead, look at some of the problems and friction points in your own life, and see if you can create a solution to those problems.
Worst case scenario: you make your life easier, even if you don't make any money.
Best case scenario: Other people have this problem too, and might pay you to solve it for them.