Private corporate batches, live online cohorts and 1-on-1 mentoring in responsive grids, components and a themed, budgeted Bootstrap build in your pipeline — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches Bootstrap as a framework you compile rather than a stylesheet you link — the flexbox grid and its breakpoint model, the component and utility layers, and the JavaScript plugin API including the differences between version 4 with jQuery and version 5 without it. Sessions concentrate on what teams get wrong after the first page: theming through Sass variables instead of override stylesheets, importing only the components in use, purging and budgeting the bundle in CI, verifying component accessibility, and sequencing a version upgrade that nobody wants to start.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Bootstrap that means a trainer who has run it in production — responsive grids, components and a themed, budgeted Bootstrap build in your pipeline — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Bootstrap batchBootstrap is a mobile-first CSS and JavaScript framework: a responsive grid, a normalised base stylesheet, a component library covering the interface patterns most applications need, a large set of utility classes, and a small group of JavaScript plugins for modals, dropdowns, carousels, tooltips and collapse behaviour. You write markup with its class names, and the framework supplies the layout and appearance.
The grid is the core of it. Containers, rows and columns sit on a flexbox layout with breakpoint-specific class names, auto-layout and equal-width columns, ordering and offsets, and gutters that stay consistent across every page. Around it the content layer standardises typography, images, tables and figures; the components cover navigation, cards, forms, alerts, badges, modals and the rest; and the utility classes handle spacing, display, flex, colour and text so most pages need very little bespoke CSS.
What separates a good Bootstrap codebase from a bad one is how it is built. Loading the compiled stylesheet from a CDN and overriding it with a second stylesheet produces specificity fights and a bundle full of unused rules. Compiling from the Sass or Less source with your own variable overrides, importing only the components you use, and letting a pipeline purge, minify and fingerprint the result produces a themed framework that looks like your product rather than a template. Bootstrap 4 depended on jQuery; Bootstrap 5 removed that dependency, dropped Internet Explorer support and introduced CSS custom properties — which is why the version you are on determines a great deal about how your application is written.
Bootstrap remains one of the most widely deployed frontend frameworks in the world. It is the default in countless admin templates, internal tools, CMS themes, vendor products and corporate design systems, which means most engineers will maintain a Bootstrap codebase whether or not they chose it. It also means a very large number of applications are still on version 3 or 4, carrying jQuery and an unsupported release with them.
The practical value is speed with consistency. A team that knows the grid and utilities can build a usable, responsive, accessible interface in hours rather than days, and every page in the estate behaves the same way. That matters most for the interfaces engineering teams build for themselves — dashboards, status pages, admin panels, internal portals — where design capacity is scarce but usability still counts.
The problems worth training for are the ones that show up later: a 250 kilobyte stylesheet where thirty is used, a theme implemented as overrides rather than variables, a version upgrade nobody can risk, jQuery retained solely for the framework's plugins, and accessibility findings in components that were assumed to be accessible by default. Those are build, architecture and upgrade problems, and they are the ones this course spends its second half on.
What Bootstrap is, what problem it solves and what it costs. Where to get it and the four installation routes with their trade-offs, the file structure and what Reboot changes about the browser defaults, containers and the breakpoint system — then an honest comparison of versions 4 and 5 and what your choice commits you to.
Topics: What Bootstrap is and why teams use it · Where to get Bootstrap — download, CDN, npm and source · Using Bootstrap online versus bundling it, and subresource integrity · The distribution file structure — CSS, JavaScript bundle and source · Reboot, normalisation and the base styles you inherit · Containers, fluid containers and the breakpoint scale · Bootstrap 4 versus 5 — jQuery removal, Popper, dropped browser support, custom properties · When Bootstrap is the wrong choice
The framework's core. How the grid works on flexbox, the grid options across breakpoints, auto-layout and equal-width columns, variable-width content, responsive classes, then ordering, offsets, nesting and gutters — with the failure patterns that produce horizontal overflow on small screens.
Topics: How the grid works — containers, rows and columns · Grid options across the breakpoint scale · Auto-layout columns and equal-width columns · Variable width content and content-sized columns · Responsive classes and breakpoint-specific behaviour · Column ordering, offsets and nesting · Gutters, spacing and alignment within the grid · Diagnosing horizontal overflow
The content layer that makes every page in an estate look consistent. Headings and display headings, inline text elements, blockquotes, alignment, responsive typography, code and variables, image treatments, the table variants, and figures — plus where customising a heading is correct and where it means fighting the framework.
Topics: Headings, customising headings and display headings · Inline text elements, blockquotes and alignment · Responsive typography · Code, inline code and variables · Images — rounded corners, circle, thumbnail and responsive images · Tables — basic, striped, bordered, hover and condensed · Responsive tables and overflow behaviour · Figures and the figure component
The components that carry a user through the application. Alerts including links, dismissal and animation, badges and their variations, breadcrumbs and pagination, the nav family through tabs and pills, the navbar with its responsive behaviour, and dropdowns in every direction with menu alignment.
Topics: Alerts — contextual variations, alert links, closing and animated alerts · Badges — contextual variations, pill badges and links · Breadcrumb and pagination, sizing and alignment · Nav — base nav, horizontal alignment, vertical, fill and justify · Tabs, pills and tabs with dropdowns · Navbar — brand, supported content, inputs, colour schemes and responsive behaviour · Dropdowns — single and split buttons, dropup, dropright, dropleft · Menu items and menu alignment · Keyboard behaviour and focus handling in navigation components
The building blocks of a page body. Button styles, sizes and states, button groups and toolbars, the collapse family through to accordions, cards with all their content types, and list groups — assembled into the panel and dashboard patterns most internal tools are made of.
Topics: Button styles, sizing and block-level buttons · Active and disabled button states · Button groups, toolbars, nesting and vertical variation · Collapse — basic collapsible, panels, list groups and multiple targets · Accordion behaviour and its accessibility requirements · Cards — content types, titles, text and links · Images in cards, headers and footers · List groups and their variants · Composing cards and collapse into dashboard panels
The part of the framework that gets the most use and the least attention. Inputs, textareas, checkboxes, radios and selects, input sizing and input groups, form layout on the grid, validation states, and the labelling and error-messaging rules that decide whether the form passes an accessibility review.
Topics: Inputs, textareas and input sizing · Checkboxes, radio buttons and switches · Select lists and multiple selects · Input groups with prefixes, suffixes and buttons · Form layout on the grid, inline and horizontal forms · Validation states and feedback messages · Native constraint validation alongside framework styling · Labels, help text and accessible error announcement · Disabled and readonly states
The interactive layer. Modals in all their variants, tooltips and popovers with positioning, carousels, scrollspy, and the collapse and dropdown APIs — initialised through data attributes or programmatically, with their event lifecycle, plus what changed when version 5 dropped jQuery in favour of vanilla JavaScript and Popper.
Topics: Modals — small, medium and large, scrolling long content, vertically centred · Modal content that varies, grids inside modals and optional sizes · Tooltips and popovers — creating them, the plugin and four-direction positioning · Carousel — slides only, controls, indicators and captions · Scrollspy and vertical menu highlighting · Data attribute initialisation versus the programmatic API · Plugin events and lifecycle hooks · Popper positioning and its dependency · jQuery in version 4 and its removal in version 5
Making the framework look like your product. The icon options and their weight, the utility class system for spacing, display, flex, colour and text, then real theming — Sass variables and maps, overriding the scale, custom properties in version 5, dark mode, and the difference between customising and fighting.
Topics: Icon options — Bootstrap Icons, Font Awesome, Google Material, Ionicons, Feather, Dripicons, Bytesize · Icon weight, sprite sheets and inline SVG · Utility classes — spacing, display, flex, colour, text and borders · The utility API and generating your own utilities · Sass variables, maps and the theme colour system · Overriding the type scale, spacing scale and breakpoints · CSS custom properties in version 5 and runtime theming · Dark mode and colour-mode support · Theming versus override stylesheets, and specificity consequences
The engineering half. Compiling Sass from source with a bundler, importing only the components you use, purging unused classes, autoprefixing, minifying, fingerprinting and caching, then version upgrades, accessibility auditing and the CI gates that keep the bundle from growing back.
Topics: npm installation and a bundler-based build · Compiling Sass from source and importing selectively · Removing unused CSS safely, and the risks of purging dynamic class names · Autoprefixer, browser targets and supported browsers · Minification, source maps, fingerprinting and cache headers · Self-hosting versus CDN in regulated environments, and subresource integrity · Upgrading version 3 to 4 to 5 — breaking changes and sequencing · Removing jQuery once the framework no longer needs it · Accessibility auditing of framework components · CSS size budgets and visual regression tests in CI
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild a multi-panel dashboard using only grid and utility classes, then verify at 360, 768 and 1440 pixels that nothing overflows and nothing needs custom CSS.
Assemble a navbar, dropdown, tabs and a validated form, then test them with the keyboard and a screen reader and fix every finding.
Convert version 4 plugin initialisation to the version 5 vanilla JavaScript API, wire up modal and tooltip events, and remove the jQuery dependency entirely.
Re-theme the framework through Sass variables and maps, delete the override stylesheet it replaces, and show the specificity problems that disappear with it.
Compile from source, import only the components in use, purge what remains, minify and fingerprint the output, and record the size at each step.
Plan and execute an upgrade from version 4, resolving breaking changes, replacing jQuery-dependent plugin code, and proving the interface with visual regression tests.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
I was looking to improve my understanding of AIOps, and this training helped me achieve that goal. Rajesh Kumar explained the subject in a structured and practical manner. The sessions on different AIOps concepts were informative.
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.