Add your idea
We value your feedback. You can vote for existing ideas, discuss them or add your own.
Powered by FeedBear
Use 'Article' instead of 'Blog' whenever appropriate
Originally, the word 'Blog' was used to describe a website that contained a collection of 'Articles' (or 'Blog Articles'). More recently, some sites have started referring to their 'Blog Articles' as 'Blogs', which is confusing, specially for non-English speakers - i.e., this is a 'Blog in a Blog' is not as clear as this is an 'Article in a Blog'. This confusion is exemplified in the WebBoss interface. When the item says 'Create new Blog', does it mean 'create an entire new collection of articles (blog)', or 'create a new article for the (only) blog'? When you say 'Blog Layout', do we mean 'they layout of the page where the blog articles are LISTED' (i.e., the main blog page), or do we mean 'the layout of a blog ARTICLE'? These not-so-subtle differences in meaning can make learning to navigate the system, and understanding its options and capabilities, more difficult than it needs to be. Precision of language here would be helpful. Sidebar items such as 'View All Blogs', 'Add New Blog', 'Blog Groups' and 'Blog Layout' should be renamed to 'View All Articles', 'Add New Article', 'Article Groups' (or 'Blog Categories'), and 'Article Layout'. In addition, we should do a search through every instance where the word 'blog' is used in the interface, to make sure that it would not be clearer to replace it with the word 'article'.
Agency/Re-Seller Billing
Incorporate client subscriptions or billing so that agencies can bill web design clients from within the platform.
Theme Designer Colour Schemes UI
Looking at updating the UI for this area. If you've used it, leave some feedback/suggestions on what you think could be better.
Get rid of 'Plugins'
It seems every sub-item in the 'Plugins' sidebar item can be safely moved and integrated into other areas of the UI, where they can be logically grouped. For example: - '3rd Party Adverts' can be moved into the 'Pages' item (as it relates to page content), or alternatively 'Website Settings' (if it is a global setting that somehow changes the behaviour of the entire website) - 'TinyMCE Plugins' and 'TinyPNG Image Compression' should be moved into a 'TinyMCE' category under Modules (after all, that's what TinyMCE is). - 'Stock Photos' can be moved into 'Import Tools' (if we see its function as 'importing an image') or 'File Upload' (if we see it as 'uploading an image') - 'SendFox Integration' can be moved into 'Modules'
FeedBear or OSTicket: pick one, but not both
Right now, bug reporting for WebBoss seems a little inconsistent and somewhat 'broken'. When we use the 'Submit a Support Ticket' form in the 'Help & Support' page, it creates a ticket in OSTicket. But the title 'Found a bug?' link at the footer of the Dashboard - which also appears elsewhere in the interface - redirects the user to reporting the bug here on FeedBear. So...which is the 'right' system for reporting bugs? Also, the 'knowledgebase' is provided in the 'Help & Support' page via a (somewhat quick-and-dirty) iFrame embed of the OSTicket site. It doesn't display well on systems with small screens (horizontal scrolling is required on laptops and iPads), and once the user finds an article, navigating BACK to an upper level is either clumsy or impossible - so the solution feels 'broken', like a temporary patch...
Rename 'Banner' to 'Slideshow' or 'Carousel'
Most UI frameworks call them carousels or slideshows: - Bootstrap: https://getbootstrap.com/docs/5.3/components/carousel/ - UIKit: https://getuikit.com/docs/slideshow - Foundation: https://get.foundation/sites/docs/orbit.html If you do a search for 'CSS carousel', or 'CSS slideshow', or 'JS slideshow' or 'JS carousel' you will see dozens of projects. The term 'banner', on the other hand, is commonly used in 2 contexts when talking about websites: - Banner Ads - the 'banner' is the most common format for website ads - Hero Banner - a common style of layout often used at the top of home pages and landing pages, including a large image, text and often a call-to-action button.
Remove buggy breadcrumbs
Honestly, if your Dashboard needs *breadcrumbs* to help your users navigate, you failed. Go back to the drawing board, and SIMPLIFY, SIMPLIFY, SIMPLIFY. On top of that, the current breadcrumbs as just annoyingly buggy - to the point I have to go every 2 or 3 hours and 'clear the cache' to reset it to a usable state. All it's doing is helping ruin my trust in the tool, as I've not *ever* used it to 'go back' or 'up a level'.
WebBoss Knowledgebase and FAQs should be built in WebBoss
Instead of using OSTicket inside an iFrame, WebBoss' own FAQs and Knowledgebase should be built using WebBoss itself - after all, this should be a case of 'eat your own dog food!'
Remove 'Website Settings' from main Dashboard menu
We already have a 'Website Settings' item in the Sidebar, which is very visible. The item in the Sidebar has 3 sub-items, while the item in the menubar is just a simple link - there is no UX consistency. If we keep the menubar item, it should be converted into a dropdown menu with the same 3 sub-items we have in the Sidebar. But it is a redundant menu item, and removing it would actually make the interface simpler, cleaner and more polished.
More/custom currencies in the shop
PayPal accepts more currencies now and the shop needs to match. Also having the ability to add custom currencies would be very useful too.
Remove 'Custom Links' from Sidebar
The 'custom links' item in the Dashboard sidebar seems to be nothing but a very simple bookmark manager - i.e., it doesn't do anything more than the 'bookmarks' function of any browser already does, does it? Am I missing something? Otherwise, we could safely remove it and help declutter that sidebar...
Remove 'Take a Screenshot' Functionality
All major operating systems - including Windows, MacOS and just about every flavour of desktop Linux - ship with screen capture tools baked-in. There is no need to add another (buggy) tool that will be difficult to maintain and keep working on all browsers, in all platforms, when the users already have access to better tools in their computer. This will help declutter the Sidebar, and hopefully free the WebBoss developers to focus their time on other, nicer and more important tasks. ;-)
Remove 'Help & Support' from the main Dashboard menu
We already have a 'Help & Support' item in the Sidebar, so no need to also have a 'Help' icon cluttering the main menu bar. As the 'Help & Support' item in the Sidebar is sub-divided into 3 different areas, if we have a 'Help' item in our main menu, then that item should also have a sub-menu with the same 3 areas, for consistency of UX. But it would be simpler to just remove the item from the menubar, as it is redundant - the one in the Sidebar is impossible to miss.
Remove 'Live Updates' from Sidebar
The 'Live Updates' section of the sidebar has 2 sub-sections: - 'Live Updates', which seems to show us the latest activity in WebBoss' Twitter, Facebook and Instagram account. They all look stale, and honestly, this section is redundant. Nobody is coming here to see your latest posts - we'll look at them in the social media platforms, if we use them. - 'News & Messages', whose functionality should really be integrated into the 'notifications' menu (no need for separate UI items that perform essentially the same function - i.e., notifying the user). So, how about if we just receive news notifications under the normal 'Notifications' menu, and then we can just get rid of the 'Live Updates' item from the Sidebar completely, and help declutter it a little?
One Dashboard is always better than many
Right now, it seems that rather than having a single Dashboard, WebBoss has *several* - which is puzzling, and very bad UX. For example, the eComm module has its own Dashboard. The blog and advert modules also have 'stats' and 'home' areas which are basically 'mini-Dashboards'. Why not simply add (optional) extra 'tiles' to the main Dashboard, when these modules are 'on'? - or even add a whole new tab to the Dashboard, for that module?
What else requires an onboarding tour?
What other areas could do with an onboarding tour to help familiarise yourself with the features?