Facebook
TwitterWPB offers two basic layout types: fixed and liquid. A liquid layout is pretty nice as it adapts to the screen size. Responsive Design with media queries goes one step further and it also brings printed web pages into shape. So for WPB, I wonder if there is anything in the pipe?
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Responsive Design
- Thread starter dave-ha
- Start date
Hi Dave,
We are starting to use Responsive Design in 11.0.10 to make websites easier to browse on mobile devices. We are also investigating the possibility of improving and developing our Responsive Design in the next versions of WPB. If you have any specific ideas or recommendations on this topic, I'd love to hear them. Thanks!
We are starting to use Responsive Design in 11.0.10 to make websites easier to browse on mobile devices. We are also investigating the possibility of improving and developing our Responsive Design in the next versions of WPB. If you have any specific ideas or recommendations on this topic, I'd love to hear them. Thanks!
Hi Custer,
Thanks for the news, I am looking forward to it!
My recommendation is to bring blocks of content into the order of their priority in the code itself. That's advantageous for users with small screens, for SEO and for the success of people using WPB. The style sheets should take care of presenting the content on the appropriate device. In other words, the priority of content influences the order in the code as well as the styling.
A challenge could be how to determine the priority of content blocks for making them appear in the right order. A no-brainer is the two column layout with the main navigation on the left, the main content in the middle: Priority: 1-2 (left - right column). Or if the main navigation is in the right column: Prioritiy: 2-1. The navigation is more important than the main content. But what about e.g. a two column layout with the main navigation across on top: Should it be 1-2-3 or rather 1-3-2 (top - left - right)? Would it make sense if the priorities could be assigned as an option in the WPB user interface?
Thanks for the news, I am looking forward to it!
My recommendation is to bring blocks of content into the order of their priority in the code itself. That's advantageous for users with small screens, for SEO and for the success of people using WPB. The style sheets should take care of presenting the content on the appropriate device. In other words, the priority of content influences the order in the code as well as the styling.
A challenge could be how to determine the priority of content blocks for making them appear in the right order. A no-brainer is the two column layout with the main navigation on the left, the main content in the middle: Priority: 1-2 (left - right column). Or if the main navigation is in the right column: Prioritiy: 2-1. The navigation is more important than the main content. But what about e.g. a two column layout with the main navigation across on top: Should it be 1-2-3 or rather 1-3-2 (top - left - right)? Would it make sense if the priorities could be assigned as an option in the WPB user interface?
Last edited:
Hi Dave,
Thanks a lot for your input, this is very useful -- I've forwarded this information to our developers for further consideration. It's difficult to say at this point whether users should have the ability to assign the priorities of content blocks. We need to do more research on possibilities of Responsive Design before I can promise anything specific. Your feedback is very useful, though -- thank you!
Thanks a lot for your input, this is very useful -- I've forwarded this information to our developers for further consideration. It's difficult to say at this point whether users should have the ability to assign the priorities of content blocks. We need to do more research on possibilities of Responsive Design before I can promise anything specific. Your feedback is very useful, though -- thank you!
Hi Custer,
These recommendations from Google could be interesting for your developers: https://developers.google.com/webmasters/smartphone-sites/?hl=en
These recommendations from Google could be interesting for your developers: https://developers.google.com/webmasters/smartphone-sites/?hl=en
