Feedback From a New User
Great tool overall with some really nice features. Makes building full-featured sites a snap. Thought I'd take the time to provide some feedback to hopefully help you improve on it. Some of this may already exist, if so, please provide links to the resources :)
- CSS needs to be fully documented. Took a fair bit of rooting around and experimentation to get all the styles tweaked to my liking. A fully documented list of classes, what they are used for, and some examples would go a long way towards making this product even easier to customize.
- Documentation on creating and inserting custom modules would be extreamly useful.
- Would be nice to have the option to place moduals in the center column. Seams like that should be fairly straghtforward to code given the existing mechanisms.
- The image insertion tool only accepts 3 didgets for mesurements and does not accept percentages. 4 didgets may be needed for sites designed for 1024x768 or larger. Percentages are vital.
- Headers for empty menus do not auto-hide. They should. For examiple I created a custom menu for all the admin related links. Anon visitors still saw the menu header even though all the links were hidden.
- Log display active column classes need a little tweaking to allow for light/dark row and alert type coloring. IE/Win is known to ignore all but the last class in a multi-class style, so its impossible on IE to get reliable matching on say tr.msg.alert.shade. This problem could be resolved by simply constructing the class="msg alert-shade" where shade is the light/dark row value.
- There's a minor display issue with the first tab and sub tab objects when the browser width is reduced. The tab bank doesn't appear to be forcing the proper minimum width, resulting in the first tab's text being misaligned. This bug seams to exist on every scaleable theme.
- Several of the stock themes have glaring problems with various moduls, the claendar is most obvious.
Again, great product. No earth shattering problems. I'm just a firm believer in giving feedback. PM me with contact info/time if you wish to discuss these points or anything relating to the product or sit dev :)
Comments
Great Feedback!
1. Re: CSS documentation: all the classes are listed in the drupal.css file, but you're right, that's not the most friendly way to document something.
2. There is documentation for developers at the excellent drupaldocs.org. It's not a user's guide, but rather for programmers getting started. There is documentation on installing modules for Drupal, but that applies to the standalone version of the software. Bryght is a hosted service, and modules can only be installed by the Bryght technical staff.
3. Not sure what you mean by being able to place modules in the centre column. Did you mean blocks? Block can actually be placed anywhere on the page using the theme, but it requires a bit of PHP knowledge outside the realm of most. In future versions of the software, this will be a lot more straightforward.
4. You're right. 3 digits isn't enough. I'll feed that back to the developers.
5. It should definitely not show if there's no data, which is how blocks normally work. I'll feed that back as well.
6, 7, and 8 are related mostly to the themes' CSS, which we can also feedback on. Specifically with #8, the event module often interacts strangely with themes, which we are working on fixing.
This is really great feedback, and I'll be sure to pass the items mentioned above along to our developers.
Almost forgot...
Would be nice to have a button constructor template for image generated buttons. Tipically this would be a 3x3 table filled with 4 corner images, tiled backgrounds for edges and center. The center cell contains button text. The table or text recieves javascript event handlers for mouseover/off effects and click action.