See a problem with the code? Need a new component? Have feedback? We'd love to hear it all! The success of the Bluemix Design System relies on great people like yourself. Fill out the form below to submit your issue to our GitHub repo.
A member of the Bluemix Design System's team will be in touch within 48 hours.
Your issue, , is now in the bluemix-components repo. Click the issue number to track the progress or make edits to your issue.
We will get back to you within 48 hours. Feel free to reach out to us on one of our slack channels if you have additional questions:#bluemix-components
Category Pages exist one level below the main Bluemix console. These areas are owned, built, and designed by category owners in order to provide focused experiences for their target users. It is important to maintain a level of consistency across these experiences, while allowing for the flexibility to address the specific needs of the target users.
The core purpose is to allow end users to discover platform capabilities, see current assets, and do productive work. Category pages should ultimately enable users to efficiently achieve productive use. They provide a prescriptive, contextual, streamlined experience focused on user workflows.
Various types of users, such as data scientists and developers, may learn about a specific task or capability offered by Bluemix. Thoughtfully expose users to the breadth of our capabilities. Embed information within the experience, and present capabilities and tasks intuitively, using industry standard language.
Clearly prioritize data so users can quickly gain insight. Information is specific and digestible. Users are able to understand how data affects them at a glance and dive deeper, if necessary.
Frame a contextual experience based on user behavior and intent to enable users to effectively accomplish tasks they set out to do. Reaching productive use is straightforward, and dynamic assistance is built in at each step.