Skip to content

Concerning Website Redesign #211

@OmegaAOL

Description

@OmegaAOL

The website shouldn't be redesigned drastically because this is the most functional version of the site; many of the mock-ups that have been posted are designed to look aesthetically pleasing but either diminish compatibility with all screen sizes and browsers, or dumbdown the existing website by removing features. The current website is not the most beautiful - but fast, well-coded, and functional.

A suggestion as to what to do with the website is to refine it, not redesign it. Examples:

  • The header logo image with the glossy wordmark and the 3D dragon's egg [https://www.qbittorrent.org/img/qb_banner.webp] could be replaced with the logo and a simple "qBitTorrent" wordmark in the same font of the logo. The drab blue could also become a lighter, more vivid shade of blue.
  • The main color of the site could be changed from blue to a toggle of white or very dark grey, for light and dark modes.
  • The website could be optimized for larger screens (stretch content across screen) without removing its usability for smaller screens.
  • Color scheme could be implemented better. For example take all the OS logos from the site and change their hue to the same vivid blue in Photoshop or GIMP. Suggestions: vivid blue, drabber blue, blue-white, white, grey, dark grey, black.
  • Add an "About" subsection (instead of the main page being About). The main page could host screenshots of qBitTorrent and a download button which automatically detects the client operating system.
  • Basically tinker with the style, but the site itself change minimally.

An example of bad redesigning is the uTorrent client. Since its buying-out from version 2.04, it has declined, becoming slow, using "modern" buttons and non-native UI elements that slow it down and break its compatibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions