-
Hi,
And thank you for very promising new white-label website builder. I purchased a starter license for testing and may move later to professional one until the software has matured a bit. My wishlist for important improvements is as follows:
1. The concept of "global elements" and especially used with menu structure need some improvement. The fundamental idea of ticking "global" for menu component and placing it on every newly created page manually may work well for professional web designers, but for newbies the idea is a bit confusing. The menu element (or header or footer) is something user would expect to automatically and consistently to be same from page to page. I would like to see implementation where global elements are automatically added to newly created pages (which would allow easier page creation as the very same global elements like header, menu or footer would not need to be dragged and dropped to every new page manually. Could you consider implementing this (and possibly adding an admin setting for this feature to be enabled/disabled if someone wants to use the old way).
2. Also menu elements would benefit from some automation. Now every link must be added manually to menu element which is something that any modern wysiwyg editor should not necessary require. Could you consider changing the page feature to be more menu oriented, so that when user creates a new page he/she could set the page order with arrow icons and also define on which menu level page would appears (or with simple tick "hide" would be hidden). Then after saving the page, the menu would be automatically reconstructed on every page from defined page order.
3. I also would like to see pulldown menu structure, where menu's can have second level drop down submenus (or possibly a third level too). Now the problem is that on single horizontal menu you cannot stuff very many pages that limits the amount of pages quite a bit.
Menu creation automation (from the "pages" settings) would solve this easily as user could define if newly created page is set on first level (horizontal menu) or second level (dropdown menu). The idea is very similar like for e.g. in now obsolete Plesk Web Presence Builder.
4. What comes to user admin interface it got its limitations. Some of your clients have requested billing system. The more important (and easier to implement) would be a API that would allow integration of any order system / billing system to be implemented. I would really like to see some API that would allow creating new users, disabling them, deleting them including the pages they have created. Also there should be a setting to disable registration trough Bloxby if API is used for registration gateway (as then registration, payment processing etc is done with other software).
Also many payment gateways (like Stripe) already provide a billing system that would fit most needs. However the data provided by Bloxby during user registration phase is very limited. There should be at least a following fields implemented:
- First name, Last name
- Company name (not required) and VAT code
- Street address, phone number, e-mail address
- Country and state (that would go to Stripe)
- Possibility to set VAT percentage for products (that would be forwarded to Stripe/Paypal and correctly applied to orders)These are the data that should be implemented to Bloxby to meet also the legislation requirements of European Union. Currently the order system without any VAT prices support is more or less unusable.
I also encourage you to implement a payment gateway to meet the requirements of Stripe security policy where credit card numbers are not directly submitted to order page, but instead using the Stripe checkout system for more security (and to allow also other payment methods, like Sepa payments etc.)
The topic ‘My wishlist for Bloxby improvements’ is closed to new replies.
