Topic

Tailwind CSS

1 post about Tailwind CSS. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Okta
Unlock the Secrets of a Custom Sign-In Page with Tailwind and JavaScript
This tutorial shows how to customize an Okta-hosted sign-in page for a fictional to-do application while retaining the Okta Identity Engine and Sign-In Widget (SIW). It starts with a custom domain and brand configuration, then uses the page code editor, SIW design tokens, custom text, Tailwind CSS via CDN, and external JavaScript behavior to create a responsive layout, branded footer, and terms-and-conditions modal. The modal uses Alpine.js transitions and a MutationObserver watching the authentication container so it appears after SIW elements render; Google Fonts also require CSP allowlist entries for googleapis.com and gstatic.com. The post notes that browser manipulation can bypass the modal, recommends accessibility testing after customization, and describes connecting the brand to an Okta React sample through an OIDC custom issuer URL.

The best engineering reads, once a week.

Topic

1 post about Tailwind CSS. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Okta
Unlock the Secrets of a Custom Sign-In Page with Tailwind and JavaScript
This tutorial shows how to customize an Okta-hosted sign-in page for a fictional to-do application while retaining the Okta Identity Engine and Sign-In Widget (SIW). It starts with a custom domain and brand configuration, then uses the page code editor, SIW design tokens, custom text, Tailwind CSS via CDN, and external JavaScript behavior to create a responsive layout, branded footer, and terms-and-conditions modal. The modal uses Alpine.js transitions and a MutationObserver watching the authentication container so it appears after SIW elements render; Google Fonts also require CSP allowlist entries for googleapis.com and gstatic.com. The post notes that browser manipulation can bypass the modal, recommends accessibility testing after customization, and describes connecting the brand to an Okta React sample through an OIDC custom issuer URL.

The best engineering reads, once a week.