Bootstrap 5.3.8 • Chapter 47 • Responsive LTR + RTL
Sass Customization
Every topic includes its own Bootstrap coding example, explanation, ten teaching examples, expected result, practice, and responsive Persian/Arabic checks.
47.1 Sass Variables
Sass Variables is part of Bootstrap 5.3.8 covered in Chapter 47. 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 Sass Variables in Chapter 47, 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 Sass Variables 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
Sass Variables is part of Bootstrap 5.3.8 covered in Chapter 47. 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 lesson page that demonstrates Sass Variables. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 47, topic 1, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the admin page example for Sass Variables. Compare the mobile layout with the tablet or desktop layout. Chapter 47, topic 1, example 2.
Example 3: Long translation
Replace a short English label in the booking page with a much longer translated label while using Sass Variables. Confirm wrapping does not widen the viewport. Chapter 47, topic 1, example 3.
Example 4: Persian test
Translate the course page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 47, topic 1, example 4.
Example 5: Arabic test
Translate the dashboard to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 47, topic 1, example 5.
Example 6: Accessibility review
Use Sass Variables in the profile screen and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 47, topic 1, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the checkout. Adjust the Bootstrap structure without hiding meaningful content. Chapter 47, topic 1, example 7.
Example 8: Utility comparison
Rebuild one part of the contact form using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 47, topic 1, example 8.
Example 9: JavaScript-state test
If Sass Variables uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the article. If not, verify the example works without JavaScript. Chapter 47, topic 1, example 9.
Example 10: Production review
Review Sass Variables in the settings panel for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 47, topic 1, example 10.
Bootstrap coding example
<pre><code class="language-scss">$primary: #6f42c1;
@import "bootstrap/scss/bootstrap";</code></pre>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Sass Variables.
- 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 Sass Variables 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 Sass Variables from Chapter 47. 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.
47.2 Maps
Maps is part of Bootstrap 5.3.8 covered in Chapter 47. 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 Maps in Chapter 47, 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 Maps 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
Maps is part of Bootstrap 5.3.8 covered in Chapter 47. 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 booking page that demonstrates Maps. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 47, topic 2, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the course page example for Maps. Compare the mobile layout with the tablet or desktop layout. Chapter 47, topic 2, example 2.
Example 3: Long translation
Replace a short English label in the dashboard with a much longer translated label while using Maps. Confirm wrapping does not widen the viewport. Chapter 47, topic 2, example 3.
Example 4: Persian test
Translate the profile screen to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 47, topic 2, example 4.
Example 5: Arabic test
Translate the checkout to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 47, topic 2, example 5.
Example 6: Accessibility review
Use Maps in the contact form and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 47, topic 2, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the article. Adjust the Bootstrap structure without hiding meaningful content. Chapter 47, topic 2, example 7.
Example 8: Utility comparison
Rebuild one part of the settings panel using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 47, topic 2, example 8.
Example 9: JavaScript-state test
If Maps uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the gallery. If not, verify the example works without JavaScript. Chapter 47, topic 2, example 9.
Example 10: Production review
Review Maps in the support page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 47, topic 2, example 10.
Bootstrap coding example
<pre><code class="language-scss">$theme-colors: map-merge($theme-colors, ("brand": #6f42c1));</code></pre>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Maps.
- 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 Maps 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 Maps from Chapter 47. 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.
47.3 Mixins
Mixins is part of Bootstrap 5.3.8 covered in Chapter 47. 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 Mixins in Chapter 47, 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 Mixins 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
Mixins is part of Bootstrap 5.3.8 covered in Chapter 47. 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 dashboard that demonstrates Mixins. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 47, topic 3, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the profile screen example for Mixins. Compare the mobile layout with the tablet or desktop layout. Chapter 47, topic 3, example 2.
Example 3: Long translation
Replace a short English label in the checkout with a much longer translated label while using Mixins. Confirm wrapping does not widen the viewport. Chapter 47, topic 3, example 3.
Example 4: Persian test
Translate the contact form to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 47, topic 3, example 4.
Example 5: Arabic test
Translate the article to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 47, topic 3, example 5.
Example 6: Accessibility review
Use Mixins in the settings panel and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 47, topic 3, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the gallery. Adjust the Bootstrap structure without hiding meaningful content. Chapter 47, topic 3, example 7.
Example 8: Utility comparison
Rebuild one part of the support page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 47, topic 3, example 8.
Example 9: JavaScript-state test
If Mixins uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the event page. If not, verify the example works without JavaScript. Chapter 47, topic 3, example 9.
Example 10: Production review
Review Mixins in the analytics page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 47, topic 3, example 10.
Bootstrap coding example
<pre><code class="language-scss">@include media-breakpoint-up(md) { .feature { display: grid; } }</code></pre>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Mixins.
- 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 Mixins 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 Mixins from Chapter 47. 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.
47.4 Import Order
Import Order is part of Bootstrap 5.3.8 covered in Chapter 47. 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 Import Order in Chapter 47, 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 Import Order 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
Import Order is part of Bootstrap 5.3.8 covered in Chapter 47. 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 checkout that demonstrates Import Order. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 47, topic 4, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the contact form example for Import Order. Compare the mobile layout with the tablet or desktop layout. Chapter 47, topic 4, example 2.
Example 3: Long translation
Replace a short English label in the article with a much longer translated label while using Import Order. Confirm wrapping does not widen the viewport. Chapter 47, topic 4, example 3.
Example 4: Persian test
Translate the settings panel to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 47, topic 4, example 4.
Example 5: Arabic test
Translate the gallery to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 47, topic 4, example 5.
Example 6: Accessibility review
Use Import Order in the support page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 47, topic 4, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the event page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 47, topic 4, example 7.
Example 8: Utility comparison
Rebuild one part of the analytics page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 47, topic 4, example 8.
Example 9: JavaScript-state test
If Import Order uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the account page. If not, verify the example works without JavaScript. Chapter 47, topic 4, example 9.
Example 10: Production review
Review Import Order in the lesson page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 47, topic 4, example 10.
Bootstrap coding example
<pre><code class="language-scss">@import "bootstrap/scss/functions";
@import "bootstrap/scss/variables";
@import "bootstrap/scss/bootstrap";</code></pre>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Import Order.
- 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 Import Order 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 Import Order from Chapter 47. 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.
47.5 Custom Bootstrap Build
Custom Bootstrap Build is part of Bootstrap 5.3.8 covered in Chapter 47. 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 Custom Bootstrap Build in Chapter 47, 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 Custom Bootstrap Build 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
Custom Bootstrap Build is part of Bootstrap 5.3.8 covered in Chapter 47. 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 article that demonstrates Custom Bootstrap Build. Keep the Bootstrap classes visible in the markup and explain which class provides the behavior. Chapter 47, topic 5, example 1.
Example 2: Responsive variation
Add a breakpoint-specific class to the settings panel example for Custom Bootstrap Build. Compare the mobile layout with the tablet or desktop layout. Chapter 47, topic 5, example 2.
Example 3: Long translation
Replace a short English label in the gallery with a much longer translated label while using Custom Bootstrap Build. Confirm wrapping does not widen the viewport. Chapter 47, topic 5, example 3.
Example 4: Persian test
Translate the support page to Persian. Verify start/end spacing, text alignment, component direction, and that the Bootstrap RTL stylesheet is active. Chapter 47, topic 5, example 4.
Example 5: Arabic test
Translate the event page to Arabic. Check buttons, forms, dropdowns, navigation, and offcanvas placement for correct RTL behavior. Chapter 47, topic 5, example 5.
Example 6: Accessibility review
Use Custom Bootstrap Build in the analytics page and verify semantic HTML, accessible names, keyboard interaction, focus visibility, and status messaging. Chapter 47, topic 5, example 6.
Example 7: Content stress
Add long text, nested controls, wide media, and narrow viewport width to the account page. Adjust the Bootstrap structure without hiding meaningful content. Chapter 47, topic 5, example 7.
Example 8: Utility comparison
Rebuild one part of the lesson page using Bootstrap utilities instead of custom CSS, then compare readability and maintainability. Chapter 47, topic 5, example 8.
Example 9: JavaScript-state test
If Custom Bootstrap Build uses Bootstrap JavaScript, test open, close, focus, disposal, and repeated initialization in the admin page. If not, verify the example works without JavaScript. Chapter 47, topic 5, example 9.
Example 10: Production review
Review Custom Bootstrap Build in the booking page for breakpoints, RTL, Google Translate, zoom, keyboard use, performance, and maintainable class choices. Chapter 47, topic 5, example 10.
Bootstrap coding example
<pre><code class="language-scss">$primary:#6f42c1;
$border-radius:1rem;
@import "bootstrap/scss/bootstrap";</code></pre>Step-by-step code explanation
- Identify the Bootstrap class, data attribute, or JavaScript API used for Custom Bootstrap Build.
- 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 Custom Bootstrap Build 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 Custom Bootstrap Build from Chapter 47. 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 47 review — 10 questions and answers
1. What should you inspect when Sass Variables does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Sass Variables. Then inspect computed styles to see which declaration wins.
2. How should Sass Variables be tested before publishing?
Answer: Test Sass Variables 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 Maps does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Maps. Then inspect computed styles to see which declaration wins.
4. How should Maps be tested before publishing?
Answer: Test Maps 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 Mixins does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Mixins. Then inspect computed styles to see which declaration wins.
6. How should Mixins be tested before publishing?
Answer: Test Mixins 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 Import Order does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Import Order. Then inspect computed styles to see which declaration wins.
8. How should Import Order be tested before publishing?
Answer: Test Import Order 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 Custom Bootstrap Build does not behave as expected?
Answer: Check the Bootstrap classes, breakpoint, DOM structure, loaded CSS version, and any JavaScript data attributes involved in Custom Bootstrap Build. Then inspect computed styles to see which declaration wins.
10. How should Custom Bootstrap Build be tested before publishing?
Answer: Test Custom Bootstrap Build 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.