-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complete overhaul of website #51
Comments
In my opinion, it lacks personality. We try to infuse a lot of positivity and parts of ourselves into everything we do but at the website at the moment just feels generic. It doesn't say anything about the wonderful dwyl community or make it clear what dwyl actually does. Visually, it also feels quite bland. It's mostly words on a page. A blog post on the subject of the line between 'simple' and 'bland' would probably be very apt here. Aims:
|
Do you have the #dwylsummer photo of the all the people in the Pool Garden in High Res...? |
Agree _unequivocally_! Thanks for digging it out. ✅ |
So... You know how we said we weren't going to use a CSS Library for the dwyl website...? |
On PureCSS, totally agree: dwyl/learn-to-send-email-via-google-script-html-no-server#4 (comment) |
I had a hard time finding a browser support table for pure, but instead found this:
(which is good to know because they certainly use flexbox which is unsupported in many browswers (pre-IE10: http://caniuse.com/#search=flexbox) |
The websummit milestone portion of this is done with PR #56. We should open a new issue for this post websummit. |
@hdrdavies This was in the days when were on our way to launching our time management product (before we took on external clients because of https://github.com/dwyl/ateam-proposal |
@iteles I thought so! It won't be quite the same message but the overall tone is interesting and does a good job of differentiating dwyl from the pack 👍 |
There are a few issues with the website as it stands:
Given that we're at the web summit in the next couple of days, this should be our top priority at the moment.
The text was updated successfully, but these errors were encountered: