-
Notifications
You must be signed in to change notification settings - Fork 35
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
Allow API owner to add oembed content for an API #2035
Comments
From @Nazarah on January 3, 2017 6:23 @bajiat @brylie : I created low fidelity design as part of issue #83, and there I also included the design idea of adding oembd content. I am adding those wireframes here. The wireframes are based on card components of bootstrap: |
From @Nazarah on January 9, 2017 7:48 Alternate design suggestions
|
"Add an oembd content" should be renamed to be less technical. If you want, you can add a text that explains user that this adds embedded content that user can click and view in the original source. Give examples of content types (blog posts, videos, presentations) |
@Nazarah The changes are looking ok to me. Just one thing to nitpick about: the title of the section "Embedded Contents". In this meaning, the word "content" is an incountable. So keep also the title of section in singular: "Embedded Content" |
From @Nazarah on February 6, 2017 8:18 I will need to add an extra wireframe for the case when API owner has not yet added any Oembed content. |
@matleppa @jawidahmadi To be assigned to you. |
@brylie ready for review. |
From @bajiat on December 13, 2016 12:3
Related to #16
Todo
Definition of done
Open issue: attribution information (added by and/or original author)
Wireframe
On API Profile detail page, a button for adding Oembd content will appear on the Oembd Pane.
On clicking the button, a dialogue would appear with necessary fields to add a new Oembd contents.
Fields included: Name, URL, Description, Preview checkbox (checking this would show in which platform the original content is added. e.g. Youtube, Twitter, Wordpress, etc.
Copied from original issue: Digipalvelutehdas/APIKA#127
The text was updated successfully, but these errors were encountered: