JS docs formatting tweaks

[mdo]

This PR revisits the options, methods, and events sections for each component's JS section. Builds off @rohit2sharma95's suggested changes for the dispose method and takes a more holistic approach to the sections.

• All sections are now Markdown-powered tables
• All tables are using the bs-table short code to add our .table-* classes as needed
• Does a little bit of wordsmithing, but could use more editing overall

I'm waiting on @Johann-S or someone else to tell me what happens with dispose before calling content final here, but wanted to open the PR for when we're ready.

TODO:

• Convert the remaining HTML tables to Markdown
• Verify that the CSS still works and is adapted
• When we are done converting all tables, see if the markdown shortcode is still used

Preview: https://deploy-preview-31337--twbs-bootstrap.netlify.app/

Fixes #31189

[XhmikosR]

We should make the table responsive BTW.

EDIT: And maybe use normal font-size? Not sure what the rationale behind this choice was.

[mdo]

And maybe use normal font-size? Not sure what the rationale behind this choice was.

I knocked down the font-size to ideally help with readability. Bump it up in the inspector and see how it feels for you. For me it really helped with reading a table to downsize the font vs the body text. These tables are super content dense as well, and my secondary goal is to show more table contents to make it easier to scan the whole thing.

[Johann-S]

@rohit2sharma95 summarized everything here: #30838 (comment)
so you can use it @mdo

[XhmikosR]

It just feels weird not having the tables responsive though. font-size might be objective :)

[mdo]

It just feels weird not having the tables responsive though.

Oh sorry, oversight on my part. I'll revisit and update.

[XhmikosR]

After we merge #31803, I can switch to responsive tables in this branch, assuming we no longer use raw HTML tables.

[XhmikosR]

@mdo I rebased this and switched to responsive tables too. Needs a thorough review just in case I missed something in the rebase (we should also check the whole docs again for more instances).

Otherwise, I'd say we can proceed with this.

EDIT: it seems we need to tweak the docs CSS for responsive tables to work properly.

[XhmikosR]

@ffoodd what's your take on this? Mostly the CSS stuff.

I say we land this as is and we migrate any missing components later, otherwise we'll have this hanging forever.

[ffoodd]

I think it needs some tweaks, e.g. the content table doesn't overflow properly and makes body overflow.

Not sure what happens for now.

[XhmikosR]

@mdo @ffoodd should we land this after a rebase? We can't keep rebasing it :/

We just need some help with the CSS comments.

[GeoSot]

I think it needs some tweaks, e.g. the content table doesn't overflow properly and makes body overflow.

Wasn't wrapped with .table-responsive.

Added some more, and wrapped these that use html customization inside.

[mdo]

Updated this with some new copy changes to clean up <br> usage in a few JS tables and redo the containers and contents tables in Markdown. There are now no more responsive tables in our docs not using the table shortcode.

[ffoodd]

Nice work! This'll be really helpful 🚀

[XhmikosR]

Let's land this and revisit any remaining instances later :)