Open Shelmith-Kariuki opened 1 year ago
Hi @Shelmith-Kariuki,
Thanks for using bs4Dash! I can certainly look at 1 and try a fix.
However for 2, I think this is a wrong pattern to have nested cards. From a UX/UI point of view this is not a good experience for the end user. I can definitely add it in the documentation.
@DivadNojnarg , thanks for the reply. We look forward to the fix.
Our app requires users to provide data for several sections, each of which is presented as a card. However, one of the sections contains a large amount of information. To make it more manageable, we've divided that section into four separate cards. How would you approach this differently?
What kind of information would you like to see in 2)? Could you provide me a quick example?
For 1, you could put the icon under the title element:
bs4Dash::updatebs4Card(
id = "card1",
action = "update",
options = list(
title = h1(
icon("table"),
paste0("First Card ", emo::ji("banana"))
),
status = "primary"
)
)
Dear @DivadNojnarg and everyone who contributed to this package, thank you for your hard work.
My colleague and I are building an app that uses the bs4Card() function, and our app looks great. However, we have encountered two issues that we would like to raise:
Please find the following code, which reproduces both issues:
Thank you for your help!
cc @arthur-shaw