Feature #2851
closed[WEBSITE] Modernize Wt Website
0%
Description
The Wt website is build with wt, and this is good so (any application framework should use itself, as much as possible).
Although the current layout / appearance is functional, it does not showcase the abilities of Wt, mainly the ones to handle "modern look" responsive design.
I understand that Wt has build-in support for responsive designs (e.g. bootstrap library), so it should not be very difficult to update the website.
And even without a responsive design, a basic design update could showcase immediately, on the first sight: a modern web framework.
(Set priorty to "High", as this is about the "first impression" a visitor gets about Wt)
Updated by I. Lazaridis about 10 years ago
As for an example of a nice site structure / information / layout (not responsive), see the poco project (which is a C library, too):
Updated by Kirill Brutyev about 10 years ago
the website look depends on your taste. I find that the website is really nice. the only downside is there is no mobile version (responsive design). What got me into wt in the first place is that design and how fast the website is. I wouldn't want wt webpage to look like an apple page. wt/widgets site is a good showcase. a link to showcase earlier, would be nice. either way, i think there are higher priorety things.
Updated by I. Lazaridis about 10 years ago
Kirill Brutyev wrote:
the website look depends on your taste.[...]
of course, but this is more about functional design and demonstration of capabilities.
>[...] either way, i think there are higher priorety things.
This issue affects just the design / layout ("Although the current layout / appearance is functional, it does not showcase the abilities of Wt, mainly the ones to handle "modern look\" responsive design.\").
Showing what wt can do is a must.
-
If I rate additionally the structure (navigation) and content (text) of the website, then a redesign has an absolute top priority. Many text is outdated, misleading etc., and there are additionally issues with too much text (see e.g. #2833).