Bootstrap 5.3.8 • Chapter 30 • Responsive LTR + RTL
Cards
Every topic includes its own Bootstrap coding example, explanation, ten teaching examples, expected result, practice, and responsive Persian/Arabic checks.
30.1 card
card is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For card in Chapter 30, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test card at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
card is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest profile screen that demonstrates card. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 30, topic 1, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the checkout example for card. Compare the mobile layout with the tablet or desktop layout. Chapter 30, topic 1, example 2.
Example 3: Long translation
Replace a short English label in the contact form with a much longer translated label while using card. Confirm wrapping does not widen the viewport. Chapter 30, topic 1, example 3.
Example 4: Persian test
Translate the article to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 30, topic 1, example 4.
Example 5: Arabic test
Translate the settings panel to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 30, topic 1, example 5.
Example 6: Accessibility review
Use card in the gallery and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 30, topic 1, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the support page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 30, topic 1, example 7.
Example 8: Utility comparison
Rebuild one part of the event page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 30, topic 1, example 8.
Example 9: JavaScript-state test
If card uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the analytics page. If not, verify the example works without JavaScript. Chapter 30, topic 1, example 9.
Example 10: Production review
Review card in the account page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 30, topic 1, example 10.
Bootstrap coding example
<article class="card"><div class="card-body">Card content</div></article>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for card.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates card with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for card from Chapter 30. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
30.2 Card Body
Card Body is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Card Body in Chapter 30, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Card Body at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Card Body is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest contact form that demonstrates Card Body. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 30, topic 2, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the article example for Card Body. Compare the mobile layout with the tablet or desktop layout. Chapter 30, topic 2, example 2.
Example 3: Long translation
Replace a short English label in the settings panel with a much longer translated label while using Card Body. Confirm wrapping does not widen the viewport. Chapter 30, topic 2, example 3.
Example 4: Persian test
Translate the gallery to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 30, topic 2, example 4.
Example 5: Arabic test
Translate the support page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 30, topic 2, example 5.
Example 6: Accessibility review
Use Card Body in the event page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 30, topic 2, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the analytics page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 30, topic 2, example 7.
Example 8: Utility comparison
Rebuild one part of the account page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 30, topic 2, example 8.
Example 9: JavaScript-state test
If Card Body uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the lesson page. If not, verify the example works without JavaScript. Chapter 30, topic 2, example 9.
Example 10: Production review
Review Card Body in the admin page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 30, topic 2, example 10.
Bootstrap coding example
<article class="card"><div class="card-body"><h2 class="card-title">Title</h2><p class="card-text">Text</p></div></article>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Card Body.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Card Body with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Card Body from Chapter 30. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
30.3 Card Header and Footer
Card Header and Footer is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Card Header and Footer in Chapter 30, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Card Header and Footer at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Card Header and Footer is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest settings panel that demonstrates Card Header and Footer. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 30, topic 3, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the gallery example for Card Header and Footer. Compare the mobile layout with the tablet or desktop layout. Chapter 30, topic 3, example 2.
Example 3: Long translation
Replace a short English label in the support page with a much longer translated label while using Card Header and Footer. Confirm wrapping does not widen the viewport. Chapter 30, topic 3, example 3.
Example 4: Persian test
Translate the event page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 30, topic 3, example 4.
Example 5: Arabic test
Translate the analytics page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 30, topic 3, example 5.
Example 6: Accessibility review
Use Card Header and Footer in the account page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 30, topic 3, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the lesson page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 30, topic 3, example 7.
Example 8: Utility comparison
Rebuild one part of the admin page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 30, topic 3, example 8.
Example 9: JavaScript-state test
If Card Header and Footer uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the booking page. If not, verify the example works without JavaScript. Chapter 30, topic 3, example 9.
Example 10: Production review
Review Card Header and Footer in the course page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 30, topic 3, example 10.
Bootstrap coding example
<article class="card"><div class="card-header">Header</div><div class="card-body">Body</div><div class="card-footer">Footer</div></article>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Card Header and Footer.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Card Header and Footer with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Card Header and Footer from Chapter 30. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
30.4 Card Images
Card Images is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Card Images in Chapter 30, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Card Images at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Card Images is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest support page that demonstrates Card Images. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 30, topic 4, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the event page example for Card Images. Compare the mobile layout with the tablet or desktop layout. Chapter 30, topic 4, example 2.
Example 3: Long translation
Replace a short English label in the analytics page with a much longer translated label while using Card Images. Confirm wrapping does not widen the viewport. Chapter 30, topic 4, example 3.
Example 4: Persian test
Translate the account page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 30, topic 4, example 4.
Example 5: Arabic test
Translate the lesson page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 30, topic 4, example 5.
Example 6: Accessibility review
Use Card Images in the admin page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 30, topic 4, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the booking page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 30, topic 4, example 7.
Example 8: Utility comparison
Rebuild one part of the course page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 30, topic 4, example 8.
Example 9: JavaScript-state test
If Card Images uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the dashboard. If not, verify the example works without JavaScript. Chapter 30, topic 4, example 9.
Example 10: Production review
Review Card Images in the profile screen for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 30, topic 4, example 10.
Bootstrap coding example
<article class="card"><img src="photo.webp" class="card-img-top" alt=""><div class="card-body">Image card</div></article>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Card Images.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Card Images with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Card Images from Chapter 30. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
30.5 Responsive Card Layout
Responsive Card Layout is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax. The example uses Bootstrap classes or APIs directly so you can connect the class name to its visual or interactive result.
For Responsive Card Layout in Chapter 30, inspect the DOM structure, Bootstrap class names, responsive breakpoint, and any data-bs attributes or JavaScript initialization. When Google Translate is active, also verify that longer labels wrap and the correct LTR or RTL Bootstrap stylesheet is enabled.
Test Responsive Card Layout at phone, tablet, laptop, and wide-screen sizes. Then translate the example to Persian and Arabic, increase browser zoom, and inspect whether rows, columns, forms, menus, overlays, and labels remain inside the viewport.
Concept in plain language
Responsive Card Layout is part of Bootstrap 5.3.8 covered in Chapter 30. Read the Bootstrap class names as a layer over CSS layout, spacing, components, utilities, and JavaScript behavior rather than as magic syntax.
10 teaching examples
Example 1: Minimal component
Build the smallest analytics page that demonstrates Responsive Card Layout. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 30, topic 5, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the account page example for Responsive Card Layout. Compare the mobile layout with the tablet or desktop layout. Chapter 30, topic 5, example 2.
Example 3: Long translation
Replace a short English label in the lesson page with a much longer translated label while using Responsive Card Layout. Confirm wrapping does not widen the viewport. Chapter 30, topic 5, example 3.
Example 4: Persian test
Translate the admin page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 30, topic 5, example 4.
Example 5: Arabic test
Translate the booking page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 30, topic 5, example 5.
Example 6: Accessibility review
Use Responsive Card Layout in the course page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 30, topic 5, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the dashboard. Adjust the Bootstrap structure without hiding meaningful content. Chapter 30, topic 5, example 7.
Example 8: Utility comparison
Rebuild one part of the profile screen using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 30, topic 5, example 8.
Example 9: JavaScript-state test
If Responsive Card Layout uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the checkout. If not, verify the example works without JavaScript. Chapter 30, topic 5, example 9.
Example 10: Production review
Review Responsive Card Layout in the contact form for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 30, topic 5, example 10.
Bootstrap coding example
<div class="row g-3"><div class="col-12 col-md-6 col-xl-4"><article class="card h-100"><div class="card-body">Responsive card</div></article></div></div>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Responsive Card Layout.
- Read the HTML nesting first. Bootstrap components often depend on a specific relationship between wrappers, controls, and content.
- Resize the viewport and observe which responsive classes become active at each breakpoint.
- Translate the visible content. Long labels must wrap, .row children must be able to shrink, and tables should use a local responsive wrapper instead of widening the page.
- Switch to Persian or Arabic and confirm that the page has dir=rtl, Bootstrap's RTL stylesheet is active, start/end utilities behave correctly, and code examples remain LTR.
Expected result: The browser demonstrates Responsive Card Layout with responsive behavior. Persian and Arabic use RTL layout without creating page-wide horizontal scrolling; genuinely wide code or tables scroll locally.
Practice exercise
Build a new Bootstrap 5.3.8 example for Responsive Card Layout from Chapter 30. Test it at 320px, 768px, and desktop width, translate its visible text to Persian and Arabic, and explain which Bootstrap classes or JavaScript API create the final behavior.
Chapter 30 review — 10 questions and answers
1. What should you inspect when card does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in card. Then inspect computed styles to see which declaration wins.
2. How should card be tested before publishing?
Answer: Test card on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
3. What should you inspect when Card Body does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Card Body. Then inspect computed styles to see which declaration wins.
4. How should Card Body be tested before publishing?
Answer: Test Card Body on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
5. What should you inspect when Card Header and Footer does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Card Header and Footer. Then inspect computed styles to see which declaration wins.
6. How should Card Header and Footer be tested before publishing?
Answer: Test Card Header and Footer on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
7. What should you inspect when Card Images does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Card Images. Then inspect computed styles to see which declaration wins.
8. How should Card Images be tested before publishing?
Answer: Test Card Images on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.
9. What should you inspect when Responsive Card Layout does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Responsive Card Layout. Then inspect computed styles to see which declaration wins.
10. How should Responsive Card Layout be tested before publishing?
Answer: Test Responsive Card Layout on narrow and wide screens, with long translated text, in Persian and Arabic RTL mode, at increased zoom, and with keyboard navigation where the component is interactive.