openpaperwork / paperwork

Personal document manager (Linux/Windows) -- Moved to Gnome's Gitlab
https://gitlab.gnome.org/World/OpenPaperwork/paperwork
2.43k stars 148 forks source link

Openpaper.work design / look&feel is bad #707

Closed jflesch closed 6 years ago

jflesch commented 6 years ago

I'm obviously not a good web designer. If someone feels like they can do better than me regarding https://openpaper.work / https://github.com/openpaperwork/openpaper.work , please feel free to do it :)

mjourdan commented 6 years ago

Hi! I gave it a shot : http://mjourdan.frama.io/paperwork-pages/

jflesch commented 6 years ago

Nice :) I'll try to create Django templates based on it

mjourdan commented 6 years ago

As GNOME is hosting it's own Gitlab instance, I thought it could be interesting to use Gitlab pages to host the page. The site is automatically built each time I push to the repo, that's cool! To build the site, I first look at Pelican (as it is written in Python) but could not find any theme appropriate. So I tried with Middleman, which is written in ruby (which doesn't not matter much unless you are concerned with software dependencies I guess). For the UI, I simply used something existing. I didn't thought much about the text, and the screenshots clearly don't match our purpose. That's all for the feedback.

I guess with Django you would have to keep self-hosting at least, also, I have no idea of the effort required to port the theme.

jflesch commented 6 years ago

Gitlab sounds like a good idea, but I'm not sure it would be so easy. While openpaper.work looks static, it isn't. There is the statistics collection mechanism hosted on it. I guess we could split the website from the statistics collection, but then there is also an issue regarding the HTTPS certificate: For good placement in search engine results, nowadays, the website should be available using HTTPS. --> I'm using Let's Encrypt --> To get certificate with Let's Encrypt, I need control over the server hosting the website.

However, Django can serve static content. And running a cronjob nightly to update the website from a Git repository shouldn't be too much work :) I guess it would be the easiest way to go.

@mjourdan : Can I have access to the sources please ? BTW, Openpaper.work is currently GPLv3, is this license ok for you ? (currently I'm the only author for openpaper.work so I can still change the license easily).

mjourdan commented 6 years ago

I guess it would be the easiest way to go.

It seems indeed.

Of course the sources are available! you'll find them here. Regarding the licence, maybe the affero GPL would be better (as visitors benefit of the copyleft too), but I'm ok with the GPLv3.

jflesch commented 6 years ago

Yep, you're right the Affero would make more sense. I'll change it.

jflesch commented 6 years ago

Switched to AGPL: https://github.com/openpaperwork/openpaper.work/commit/ae2891e69a38da1eb9c860da337a6913898e71d8

jflesch commented 6 years ago

Note to myself: http://colorschemedesigner.com/csd-3.5/ (I'll probably adjust a little bit the colors)

jflesch commented 6 years ago

I had a look yesterday. I think mixing Middleman and Django is likely to be a huge complicated mess. I think I will just try to reuse/rewrite the HTML/CSS/JS as Django templates.

jflesch commented 6 years ago

@mjourdan Here is my shot at it (based on yours). What do you think of it ?

jflesch commented 6 years ago

It's live: https://openpaper.work/

mjourdan commented 6 years ago

Not sure about the robotic arm, but overall I like it very much! The folder and blueprint illustrations are really, really good!

jflesch commented 6 years ago

Yeah, I'm not really proud of the arm. I guess I'll have to re-make it later at some point. Anyway, it seems we are both ok with this design, so I can close this ticket :-) Thank you very much for your help :-)