Bootstrap 5.3.8 • Chapter 27 • Responsive LTR + RTL
Navs
Every topic includes its own Bootstrap coding example, explanation, ten teaching examples, expected result, practice, and responsive Persian/Arabic checks.
27.1 nav
nav is part of Bootstrap 5.3.8 covered in Chapter 27. 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 nav in Chapter 27, 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 nav 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
nav is part of Bootstrap 5.3.8 covered in Chapter 27. 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 nav. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 27, topic 1, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the checkout example for nav. Compare the mobile layout with the tablet or desktop layout. Chapter 27, 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 nav. Confirm wrapping does not widen the viewport. Chapter 27, 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 27, 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 27, topic 1, example 5.
Example 6: Accessibility review
Use nav in the gallery and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 27, 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 27, 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 27, topic 1, example 8.
Example 9: JavaScript-state test
If nav uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the analytics page. If not, verify the example works without JavaScript. Chapter 27, topic 1, example 9.
Example 10: Production review
Review nav in the account page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 27, topic 1, example 10.
Bootstrap coding example
<nav class="nav"><a class="nav-link active" href="#">Home</a><a class="nav-link" href="#">Courses</a></nav>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for nav.
- 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 nav 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 nav from Chapter 27. 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.
27.2 nav-tabs
nav-tabs is part of Bootstrap 5.3.8 covered in Chapter 27. 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 nav-tabs in Chapter 27, 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 nav-tabs 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
nav-tabs is part of Bootstrap 5.3.8 covered in Chapter 27. 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 nav-tabs. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 27, topic 2, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the article example for nav-tabs. Compare the mobile layout with the tablet or desktop layout. Chapter 27, 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 nav-tabs. Confirm wrapping does not widen the viewport. Chapter 27, 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 27, 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 27, topic 2, example 5.
Example 6: Accessibility review
Use nav-tabs in the event page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 27, 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 27, 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 27, topic 2, example 8.
Example 9: JavaScript-state test
If nav-tabs uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the lesson page. If not, verify the example works without JavaScript. Chapter 27, topic 2, example 9.
Example 10: Production review
Review nav-tabs in the admin page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 27, topic 2, example 10.
Bootstrap coding example
<nav class="nav nav-tabs"><a class="nav-link active" href="#">One</a><a class="nav-link" href="#">Two</a></nav>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for nav-tabs.
- 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 nav-tabs 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 nav-tabs from Chapter 27. 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.
27.3 nav-pills
nav-pills is part of Bootstrap 5.3.8 covered in Chapter 27. 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 nav-pills in Chapter 27, 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 nav-pills 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
nav-pills is part of Bootstrap 5.3.8 covered in Chapter 27. 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 nav-pills. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 27, topic 3, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the gallery example for nav-pills. Compare the mobile layout with the tablet or desktop layout. Chapter 27, 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 nav-pills. Confirm wrapping does not widen the viewport. Chapter 27, 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 27, 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 27, topic 3, example 5.
Example 6: Accessibility review
Use nav-pills in the account page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 27, 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 27, 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 27, topic 3, example 8.
Example 9: JavaScript-state test
If nav-pills uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the booking page. If not, verify the example works without JavaScript. Chapter 27, topic 3, example 9.
Example 10: Production review
Review nav-pills in the course page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 27, topic 3, example 10.
Bootstrap coding example
<nav class="nav nav-pills"><a class="nav-link active" href="#">One</a><a class="nav-link" href="#">Two</a></nav>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for nav-pills.
- 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 nav-pills 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 nav-pills from Chapter 27. 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.
27.4 Fill and Justify
Fill and Justify is part of Bootstrap 5.3.8 covered in Chapter 27. 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 Fill and Justify in Chapter 27, 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 Fill and Justify 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
Fill and Justify is part of Bootstrap 5.3.8 covered in Chapter 27. 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 Fill and Justify. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 27, topic 4, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the event page example for Fill and Justify. Compare the mobile layout with the tablet or desktop layout. Chapter 27, 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 Fill and Justify. Confirm wrapping does not widen the viewport. Chapter 27, 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 27, 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 27, topic 4, example 5.
Example 6: Accessibility review
Use Fill and Justify in the admin page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 27, 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 27, 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 27, topic 4, example 8.
Example 9: JavaScript-state test
If Fill and Justify uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the dashboard. If not, verify the example works without JavaScript. Chapter 27, topic 4, example 9.
Example 10: Production review
Review Fill and Justify in the profile screen for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 27, topic 4, example 10.
Bootstrap coding example
<nav class="nav nav-pills nav-fill"><a class="nav-link active" href="#">One</a><a class="nav-link" href="#">Two</a></nav>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Fill and Justify.
- 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 Fill and Justify 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 Fill and Justify from Chapter 27. 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.
27.5 Responsive Navs
Responsive Navs is part of Bootstrap 5.3.8 covered in Chapter 27. 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 Navs in Chapter 27, 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 Navs 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 Navs is part of Bootstrap 5.3.8 covered in Chapter 27. 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 Navs. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 27, topic 5, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the account page example for Responsive Navs. Compare the mobile layout with the tablet or desktop layout. Chapter 27, 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 Navs. Confirm wrapping does not widen the viewport. Chapter 27, 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 27, 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 27, topic 5, example 5.
Example 6: Accessibility review
Use Responsive Navs in the course page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 27, 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 27, 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 27, topic 5, example 8.
Example 9: JavaScript-state test
If Responsive Navs uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the checkout. If not, verify the example works without JavaScript. Chapter 27, topic 5, example 9.
Example 10: Production review
Review Responsive Navs in the contact form for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 27, topic 5, example 10.
Bootstrap coding example
<nav class="nav flex-column flex-md-row"><a class="nav-link" href="#">One</a><a class="nav-link" href="#">Two</a></nav>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Responsive Navs.
- 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 Navs 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 Navs from Chapter 27. 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 27 review — 10 questions and answers
1. What should you inspect when nav does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in nav. Then inspect computed styles to see which declaration wins.
2. How should nav be tested before publishing?
Answer: Test nav 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 nav-tabs does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in nav-tabs. Then inspect computed styles to see which declaration wins.
4. How should nav-tabs be tested before publishing?
Answer: Test nav-tabs 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 nav-pills does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in nav-pills. Then inspect computed styles to see which declaration wins.
6. How should nav-pills be tested before publishing?
Answer: Test nav-pills 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 Fill and Justify does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Fill and Justify. Then inspect computed styles to see which declaration wins.
8. How should Fill and Justify be tested before publishing?
Answer: Test Fill and Justify 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 Navs does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Responsive Navs. Then inspect computed styles to see which declaration wins.
10. How should Responsive Navs be tested before publishing?
Answer: Test Responsive Navs 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.