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
Instance Dashboards are used for showing information and details of an instance that exist in the user's dashboard. They appear when a user clicks on a specific item in their dashboard. Typically, these instances can include CF Apps, Services, Virtual Machines, and Containers. Use these templates as a starting point and foundation for your design.
Content aiding in a user's productive use workflow and any additional learning content should surface in the Manage page. Consider providing introductory material such as links to service-specific API documentation and demos so users can quickly and effectively get up and running.
Service dashboards may be accessed from the Global dashboard, or after a user provisions a service from the Bluemix catalog. Service dashboards serve as locations for users to learn more about services, configure their service instance and connect it to an existing app or service instance.
As shown in the example above, Service dashboards are comprised of a series of tabs that are defined in the service broker meta-data.
Getting Started at the instance level should be all about getting a user up and running as fast as possible.
Upon creation of a service instance, the content on the Getting Started page is the first thing a user encounters and will likely dictate how successful they are with the service.
Content aiding in a user's productive use workflow, and any additional learning content should surface in the Manage page. Consider providing pertinent introductory material such as links to service-specific API documentation and demos so users can quickly and effectively get up and running.
The Service Credentials page shows the service instance credentials to an end user. Currently, users have the ability to create mulitple sets of credentials.
Services that do not use credentials are not required to have this.
This provides a way for users to bind their service instance to an existing app or service instance.
We understand that more complex interfaces may require a launch out experience. If your service validates this need, use the Launch out template below. Include a basic description of the capabilities your service offers, as well as a description to what the user can expect to happen once they launch out.