To card or not to card? about ng-bootstrap HOT 8 CLOSED

I don't think we should support these in a component - I already investigated this, and it seems too limited given what Bootstrap's markup supports.

I wouldn't be against using cards where they would make sense, but we should consider a way to allow users to break out of opinionated markup in our components.

from ng-bootstrap.

For reference: http://v4-alpha.getbootstrap.com/components/card/

from ng-bootstrap.

I would agree with you both. It doesn't make sense as a component.

from ng-bootstrap.

Closing as won't support

from ng-bootstrap.

Is there a reason why ng-bootstrap be compatible with bootstrap 3?

This project should be compatible with bootstrap 4 & forward

ng-bootstrap should be forward looking, so it makes very little sense that this issue is closed

from ng-bootstrap.

Keep the issue open so that interested contributors would contribute, rather than blindly closing this issue

from ng-bootstrap.

Why to use Cards:

1. Because it is simple as hell
2. the syntax is very clear and readable
3. The concept of cards is very popular nowadays in web development
4. why do we have to reinvent the wheel
5. bootstrap 4 replaced panels with cards so it is better to be aligned with it !

I think that this decision should be revisited

from ng-bootstrap.

Because it is simple as hell

Because cards are so simple, I don't think it makes sense to abstract that into an ngb component and complicate the simple card structure offered by BS.

This ticket is 1 1/2 years old and cards have been incorporated in various areas. This library does make an artificial "panel" on the accordion (which is not a native BS4 construct), but it is made up of the card component behind the scenes.

My vote is to leave this ticket closed, as there is not really anything actionable based on the information in this ticket.

from ng-bootstrap.