New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instruct user about API Profile tabs after adding an API #1445
Comments
Link to BootStrap Tour: |
Need to review the scenarios and associated wireframes. |
@Nazarah Suggestion for the text in wireframe 3 in scenario 1: Save the proxy settings and the different API management features like Dashboard are available for your API. Scenario 2: only admin can add a proxy to the platform |
@brylie: need to discuss the scenarios with you |
I have started working on this task, but quickly encountered trouble when trying to import Bootstrap Tour:
I will try a different library, while this issue hopefully is discussed/resolved upstream. @frenchbread , @jykae, @marla-singer, and/or @NNN: do any of you have any ideas how I can properly import the |
@brylie : as you recommended I looked with http://introjs.com/, and it seems well. |
@Nazarah lets move the second scenario into a 'Guided tour for Apinf administrators' task, where we can show a new administrator how to configure Apinf. |
@Nazarah thanks for your feedback on the visual appearance of the tour. I have used the 'brand primary' color to indicate the current step, with help from @NNN. @Nazarah Relatedly, I would like to add the Quick tour button as part of this task, as you suggested. One open question, what FontAwesome icon might be good for the Quick tour button? |
I had to deviate from the definition of done here:
|
Implement a Bootstrap Tour that instructs the user to go to the proxy settings after the user has added an API. Otherwise, users who want to use a proxy might not know they need to set it in the Proxy tab.
Definition of done
Design
Scenarios
Wireframes
Tab gets highlighted (if possible)
(wireframe pending as the new settings tab UI is still not available)
The text was updated successfully, but these errors were encountered: