Custom Padding for Embedded Dashboards with Domo Everywhere

Currently, the desktop version of Domo Everywhere has default padding on the left and right side of the dashbaords making the cards all centered. Sometimes when embedding into external websites this default padding is no longer included, making the cards off kiltered or even too close or far away from one another.

Solution: Have padding be customizable for embedded dashboards

Tagged:
6
6 votes

In Review · Last Updated

Comments

  • I submitted a request for customizable padding when I first started using Domo. Why limit padding options for only embedded dashboards. All cards and dashboards should have options for padding, border thickness and color. These were among the first things available in html.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

  • MattTheGuru
    MattTheGuru Contributor

    @OliverLange & @ArborRose although I completely agree with this statement there is now a wonderful workaround.

    If you recreate the dashboard and an App Studio app and embed the app the padding on the sides will be maintained! Although this doesn't work for all cases it can sometimes be a good workaround.

    BUT I would like the ability to send a "max_width" value to the Domo Everywhere embed api so that I can let Domo's iframe take up 100% of the screen.
    **Below is a screen shot of WHY we need the iframe to be 100% and the dashboard to be constrained to s a certain width, because if I create the "padding" on the sides then there is the issue of when you click on individual cards the modal that pops up has a backdrop only goes to the edge of the iframe's defined space which looks weird). BUT if I make the dashboard 100% it expands to the edges even on 4k screens and doesn't mirror what the analyst builds in Domo.

    ** Was this post helpful? Click 💡/💖/👍/😊 below. **
    ** If it solved your problem. Accept it as a solution! ✔️ **

    Or do you need more help? https://calendly.com/matthew-kastner/15-minute-chat
    Did I help you out? Feedback is priceless and will help me more than you know.Write a review!

  • @MattTheGuru - We shouldn't have to have extensive work arounds for something as basic as padding. App Studio gives better padding options but even NIL or zero pixel padding isn't zero. I can't even get a Domo logo to align left with a card due to padding and width limitations.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

  • MattTheGuru
    MattTheGuru Contributor
    edited September 2024

    It would be AMAZING

    ** Was this post helpful? Click 💡/💖/👍/😊 below. **
    ** If it solved your problem. Accept it as a solution! ✔️ **

    Or do you need more help? https://calendly.com/matthew-kastner/15-minute-chat
    Did I help you out? Feedback is priceless and will help me more than you know.Write a review!

  • cadellfalconer
    cadellfalconer Domo Product Manager

    To everyone in this thread as it seems related, but off on a tangent a little - how do you feel about using iframes to embed content in Domo Everywhere today? Have you used any other "embedded content" providers (be that analytics or otherwise) which used alternative methods than an iframe which you preferred?

    Cadell Falconer
    Principal Product Manager
  • This feels like a deflection from the actual issue. The main concern here is the inconsistency in padding when embedding dashboards and our ability to control it.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

  • cadellfalconer
    cadellfalconer Domo Product Manager
    edited 2:53PM

    @ArborRose - It's unfortunate it came across that way, apologies, as the thinking behind it is the polar opposite to deflection! 😁
    The DOM in iFrames cannot be modified or controlled from the outer DOM of the parent page - an alternative method (should it exist), would provide a solution to not only controlling the padding, but would also allow for ultimate flexibility, as the outer DOM could then apply CSS and styling to the embedded content.

    My current train of thought is that I'd rather provide a less "locked down" experience for embedding content, that didn't limit you to GUI controls, and didn't require us to implement a new feature each time an embedding user had a request for different behavior/appearance.
    For example, you could adjust padding values as easily as changing the style's value, "padding: 10px".

    However, perhaps the more controlled experience with GUI options, higher ease of use for base use cases, but less options and control is more what users are looking for?

    Feel free to help me understand your perspective, perhaps my concept of an alternative embed method is an overshoot?

    Cadell Falconer
    Principal Product Manager