Open nelsonic opened 1 year ago
Looks like a great idea. I've been eyeing https://www.solidjs.com/ for a while (instead of doing vanilla JS + HTML, which might take a much more considerable amount of time) and it might be a good fit for this job.
I've previously done a proof-of-concept site at https://github.com/LuchoTurtle/dwyl-site just for fun, as I wanted to try out Spline3D and learn how to do a scrolling experience. It's just a reference of what a landing page could look like (obviously not the same, as it doesn't meet the performance requirements detailed on this issue).
Warning: This is an
Epic
β οΈThere is at least a month worth of work in this
Epic
. β³ It needs to be broken down in to sub-issues/tasks to be "ready fordev
". Right now I'm just trying to answer a quick question: Why is thedwyl
website so out-of-date? π€·ββοΈThe fast/short answer is: we haven't been focussed on the website for the last year because: a. Nelson was working full-time doing FinTech Consulting to get funds to re-start the
App
work. π° β b. Nelson didn't have time to build theApp
and do the full-time consulting + parenting. πΆ βNow Nelson does have time. and is "all-in" on building the
App
. π¨βπ»Context β³
In our quest to be revenue-funded we got massively side-tracked from our original plan of building an
App
. π We built many Web/Mobile Apps for great clients and gave good career experience to lots of people. β€οΈ ... but ultimately it was a distraction and it means theApp
is still not built! π€¦ββοΈThe current website https://github.com/dwyl/dwyl-site/issues/143#issuecomment-1274520735 reflects the "services" business model. It will be archived/replaced very soon. π We haven't focussed on the website because we want to build the
App
first. see: https://github.com/dwyl/mvp/issues/140 There's zero point updating the website until at least the "core" functionality is available in theApp
.Almost none of the current site will remain. βοΈ Except the color scheme. π But even that has been lost along the way. π€·ββοΈ
So everything on the current site should be considered "legacy" including the copy, images, layout, links, etc.
New Site:
App
-focussed Landing PageThe new site will be a single HTML file landing page with all the info necessary for someone to make an on-the-spot decision to try our
App
.VIDEO
of a generic use for theApp
: https://github.com/dwyl/app/issues/307Performance Focussed ποΈ
0.5 sec to interactive
. πWe should do everything we can to make it load faster than any other SaaS landing page.
How You Can Help?! π
Design / Layout π§βπ¨
We're going to need a slick fast & responsive design/layout.
SaaS
landing pages, e.g: https://dribbble.com/tags/saas_landing_pageTechnical π©βπ»
Our focus is on raw performance. We definitely don't want anything client-side rendered it's way too slow. Server rendered and cached preferably on the fastest available cache service. We are currently using
Cloudflare
and it's OK. We can switch if needed; please open an issue! If we can get compact/compress our page, optimise any images (which are loaded after the HTML so that's OK) and get it below50kb
for everything i.e. inline the CSS and any JS on the page, then we have a much better chance of "wow-ing" the reader with the speed. That means zero trackers or Google Analytics. We're going to have to hand-write our own. Don't worry this isn't as complicated as it sounds. See: https://github.com/dwyl/technology-stack/issues/127Once we decide how we're going to build/deploy the site, update the docs!
README.md
of this repo to reflect the new setup.Accessibility + SEO π
The current website scores "OK" on web.dev/measure: https://web.dev/measure/?url=https%3A%2F%2Fdwyl.com![image](https://user-images.githubusercontent.com/194400/195117695-1118f107-ee93-4375-8de2-3bc91580c314.png)
But we've managed to get the
MVP
up to 100 in everything (_except "Best Practices" which is limited by our use ofLiveView
... π) see: https://github.com/dwyl/mvp/issues/129#issuecomment-1221622079 We could easily score 100 in all areas and get Time to Interactive below0.5 sec
if we focus on performance and cache everything we can.before
a PR updating the site can be merged. That way our Accesibility, SEO & Perf never slip below100
. (sub-task/side-quest required!)More to come! β
More to come! this is just off the top of my head. But the main point is this: we're focussing on building the
App
before building the "marketing" site to "pitch" theApp
to people as the solution to their personal effectiveness woes.So if you haven't already used and provided feedback on our "scrappy" feature-poor MVP: https://github.com/dwyl/mvp/issues/140 Please do that before even thinking about "fixing" the dwyl.com website. We need "all hands on deck" to focus on the
App
. There's a lot of work to do. π