Panel | ||
---|---|---|
| ||
CHEFS = CommonHosted ElectronicHostEd FormSubmissionService |
CHEFS Red TeamClient-Client Focusedfocused. Responds to reported issues, improves and refines existing features.
CHEFS Blue Team - Future-focused. Research and Development. Explores and builds new features to extend the capabilities of Chefs.
CHEFS Team Wish List
We wish CHEFS would… | ||||||
---|---|---|---|---|---|---|
Auto/Incremental Save if I want, with option to only save manually if preferred
| ||||||
Wish in-product and ex-product documentation/help was easier to find, navigate and generally be useful
| ||||||
Wish CHEFS had |
fewer ingress channels for users to ask for support (and those channels were searchable)
| ||||||||||||||||||
Wish components were laid out in a more user-centric / task oriented manner
| ||||||||||||||||||
Wish CHEFS was more common-sense regarding the UX
| ||||||||||||||||||
Wish CHEFS integrated into PayBC to make it easy to add a “Pay Now” button
| ||||||||||||||||||
Wish CHEFS was more modular / loosely-coupled / ‘componentized’ / re-usable
| ||||||||||||||||||
Wish CHEFS could accept input from outside of CHEFS
| ||||||||||||||||||
Wish it had an events Notification System
| ||||||||||||||||||
Wish it could be embedded into other web pages (in a seamless way)
| ||||||||||||||||||
Wish it had server-sided form validation
| ||||||||||||||||||
Wish it had pagination throughout the site
| ||||||||||||||||||
Wish it had an “easy” mode for new users (and could easily be promoted to an ‘Advanced’ mode) |
| ||||||||||||||||||
Wish it were easier to edit forms without so many versions being created and that the upfront question / config were less heavy weight
| ||||||||||||||||||
Had less counter-intuitive moments in the UX ( |
e.g.: more appropriate icons, better precedence between “save” / “submit”)
| ||||||||||||||||||
Would give me the SQL to create the database to store the form data
| ||||||||||||||||||
Had more filtering options on “My Forms” (by date, etc)
| ||||||||||||||||||
Notification indicator on the dashboard for submissions / tagged as reviewer / etc.
| ||||||||||||||||||
Better documented and consistent API |
| ||||||||||||||||||
Had a ‘Shared With Me’ folder (or section), and a ‘My Own Forms’ folder (or section)… How can |
people manage their various forms and know which are which?
| ||||||||||||||||||
Can we have a “Try It Out” Button or space where we can have a POC or test model running for |
people to try the tech in a safe, non public way.. to see how they’re using or IF they’re using it.
| ||||||||||||||||||
Can we have an ‘Events notification System’? Where |
people can opt-in for notifications for particular ‘events’ or part of a form?
| ||||||||||||||||||
Can we do specific and tailored components and libraries for each ministry? ie: Tailored headings / footers
| ||||||||||||||||||
Can we have a better filtering option in search under My Forms |
ie
? e.g.: by date.. name… ministry?
| ||||||||||||||||||
How can we let folks know there have been updates made, or new changes added, to a specific feature? Could be a notification they can check at their convenience as opposed to |
a pop up.
| ||||||||||||||||||
If a feature is in testing or beta, how do we let |
people know when |
it's out of testing and official? A badge, notification, colour change, state change?
| ||||||||||||||||||
Can we let |
people know, when they’re using a specific feature a lot, our AI (or a suggestion) pops up and says |
“Hey I see you use this feature a lot, there is another feature you may like as well… here it is”
|