Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-2654

Address Feedback on on Promo Video (Voice Over Content)

XMLWordPrintable

    • Icon: Dev Task Dev Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None

      Address the comments relating to the voice over on the promo video.

      Similarly - RHOAR - that’s a product. I get that we’re using the missions / boosters in the demo so maybe unavoidable, but if we can make clear in the voice over that we’re using the ‘free’ version - or whatever we are using - that would be great. In the drop down menu for runtime there’s an option for Community (IIRC) so could we highlight that?

      Maybe some explanation of the RHOAR website, e.g. go here to get these free templates for running apps on OpenShift.

      It would be good to have some voiceover when the callback URL is being set in Keycloak.

      Pretty straightforward.

      In the video when you create the Keycloak configuration, you mentioned that the realm file that is used to configure Keycloak is provided by the RHOAR template. If I am not mistaken, it looks like the actual file being used is from the api-server app of the mobile security project. So to avoid confusion, I think it's better not to say it is provided by RHOAR at all (Does the zip file provided by RHOAR actually contains a keycloak config file)?

      This is a tricky one. We're not actually using anything from RHOAR. We're using the api-server from the mobile-security project. The keycloak config is provided in that repo.

      It makes sense that if we are pretending this project came from RHOAR, and the keycloak config is actually included in the actual project. Then the current voiceover kind of makes sense... There's no other good explanation we could give about that file...

            pahayes@redhat.com Dara Hayes (Inactive)
            pahayes@redhat.com Dara Hayes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: