Design improvements

[ErikBjare]

The current design is, well... plain.

I'd be interested in trying to step up my designer-game and create a higher-conversion landing page with greater chance of attracting users. It would be nice if we actually wanted to point people toward the website instead of the GitHub (definitely not the case currently).

I found a couple interesting/relevant links & articles:

• A WYSIWYG landing site generator for startups - Could be a good way to explore the design-space.
• Article on how to create a high-conversion landing page

We should probably include a big fat link/button to the GitHub that is seen by users immediately upon arrival; programmers/hackers are likely to find that more interesting than a landing page.

[ErikBjare]

I've thought more about this.

• The landing page should probably be more pitchy and lower the barrier to usage by providing clear instructions for how to install.
• Some of the good stuff from the README (feature comparison, introductory text) should probably be on the first page.
  • I'd want to have some text on multiple places. For example I'd like to have the feature table and introductory text in the README, docs, and on the website. Probably best to have one canonical text (the docs?) and then copy from it with added comments to highlight how it is frequently overwritten with stuff from the canonical source.
• Nothing too flashy, we should keep it simple.

[ErikBjare]

I've made several significant improvements since 2017 when this issue was first written, with a significant part done very recently.

The site now better explains and contains more useful information about ActivityWatch, but it still lacks some things that are in the README. Maybe that's for the better since otherwise it might get cluttered, but I honestly don't know.

[abena07]

hi @ErikBjare do you still need some help with this? like including the stuff int the readme to the main website? i am open to help