DEV Community: Pavel Štěrba

TailwindCSS Typography

Pavel Štěrba — Sat, 12 Nov 2022 16:20:01 +0000

During preflight, TailwindCSS removes default styles set by browser. Even tho it's useful for consistency between browsers, you are also losing default formatting for text elements like headinga, paragraphs or lists.

For custom designs, you will most likely define typography styles from scratch, but if you just want to display text data (like for example in a blog rendered from Markdown), it can be useful to have proper typography without any additional work. Let's take a look to TailwindCSS Typography first party plugin.

Installation

Just add it as another dependency to your project and download it from npm:

npm install -D @tailwindcss/typography

And add it to configuration file inside plugin section:

module.exports = {
  // ...
  plugins: [
    require('@tailwindcss/typography'),
    // ...
  ],
}

Usage

Most important class provided by this plugin is prose. Just wrap you text content wit it and you are ready to go:

<article class="prose">
  <h1>Article Title</h1>

  <p>...</p>
  <p>...</p>
  <p>...</p>
</article>

To modify text size, you can use various classes provided as well. Make sure that you are using them with prose class, not just on their own.

<article className="prose prose-lg">
  <h1>prose-lg</h1>
  <p>...</p>
</article>

Full list of supported size modifiers is:

Class	Font size
prose-sm	0.875rem (14px)
prose-base	1rem (16px)
prose-lg	1.125rem (18px)
prose-xl	1.25rem (20px)
prose-2xl	1.5rem (24px)

Aside from font size, prose also set maximum width of element for better readability. If you want to use more space or remove this behaviour completely, add class max-w-none:

<article class="prose max-w-none">
  ...
</article>

Dark mode

TailwindCSS can handle dark mode with ease with variant dark:*. In Typography plugin, you have by default various shades of gray text available, but all of them are better in light mode. To use it in dark themed page, just use prose-invert class beside your prose:

<article className="prose prose-invert">
  <h1>prose</h1>
  <p>...</p>
</article>

Modify single element

If you need more control over generated styles, you can target single element with prose-*:*. For example, if you want to underline all h1 tags, you can do it with:

<article className="prose prose-h1:underline">
  <h1>prose</h1>
  <p>...</p>
</article>

Block without formatting

In some cases, you want to disable typography for a certain block. For this purpose, just add not-prose to your element and enjoy content without styling:

<article class="prose">
  <h1>prose</h1>
  <p>...</p>

  <div class="not-prose ...">
    <h2>prose</h2>
    <p>...</p>
  </div>

  <h2>prose</h2>
  <p>...</p>
</article>

What's new in Tailwind v3.2

Pavel Štěrba — Fri, 11 Nov 2022 10:02:31 +0000

TailwindCSS v3.2 is out for a few weeks and even tho full list of changes is available on GitHub or TailwindCSS Blog, let's take a closer look at some features.

Multiple config files

If you are using multiple styles in your project (for example one for web and one for admin section), you can specify, which config file should be used for generating CSS file with new @config directive:

/* web.css */
@config "../tailwind.web.config.js"

@tailwind base;
@tailwind components;
@tailwind utilities;

/* admin.css */
@config "../tailwind.admin.config.js"

@tailwind base;
@tailwind components;
@tailwind utilities;

Styling based on browser support

Now you can conditionally style elements based on browser support of certain feature with supports-[...] variant:

<div class="bg-red-600 supports-[display:grid]:bg-green-600 ...">
  Grid support in browser
</div>

Styling based on ARIA attribute

You can also style conditionally based on ARIA attributes with new aria-* variants:

<div class="bg-green-600 aria-hidden:bg-red-600 ..." aria-hidden="true">
  Hidden for screen readers.
</div>

By default, you can use eight most used boolean ARIA values, but can of course add new ones to config file:

aria-checked
aria-disabled
aria-expanded
aria-hidden
aria-pressed
aria-readonly
aria-required
aria-selected

Styling based on data attribute

Last conditional styling is based on data attribute with data-[...] variant. There are no default variants generated by TailwindCSS, but you can use easy format data-[key=value]:

<div class="bg-red-600 data-[size=small]:bg-green-600 ..." data-size="small">
  data-size="small"
</div>

<div class="bg-red-600 data-[size=small]:bg-green-600 ..." data-size="large">
  data-size="large"
</div>

Breakpoint for max width

New max-* variant allows us to apply style until certain breakpoint is reached:

<div class="bg-red-600 max-lg:bg-green-600 ..." aria-hidden="true">
  Green background for small display.
</div>

Nested groups

Groups are useful when you need to style elements based on hover on parent element. For that, you can use group and group-hover variant. Since v3.2 you can also nest them with group/name and group-hover/name syntax:

<div class="group/outer ...">
  <div class="group/inner ...">
    <div class="bg-red-600 group-hover/outer:bg-orange-600 group-hover/inner:bg-green-600 ..."></div>
  </div>
</div>

First party plugin for container queries

Container queries are big thing in CSS world and even tho it's not implemented in TailwindCSS core yet, you can use their first party plugin with new @ syntax:

<div class="@container">
  <div class="block @lg:flex">
    <!-- ... -->
  </div>
</div>

HTTP Status Codes as PHP Exception

Pavel Štěrba — Sat, 05 Nov 2022 09:57:28 +0000

HTTP status codes are not just 404 Not Found a 500 Server Internal Error, there's plenty more. During your API development, you will sooner or later face a situation, where you will have use wider variety of HTTP statuses.

You can implement them one by one for your project, or you can use library HTTP Exceptions, which recently released major version 2.0 with all HTTP status codes.

Installation

Just add it as dependency to your project:

composer require pavelsterba/http-exceptions

Usage

All exceptions can be thrown without any additional information - message and code are predefined and you just have to send them to endpoint.

try {
    throw new HttpException\ServerError\InternalServerErrorException();
} catch (HttpException\HttpException $e) {
    echo $e->getMessage(); // 500 Internal Server Error
    echo $e->getCode(); // 500
}

If you want to customize error message or attach previous exception, you can of course pass them as parameters to constructor (but you have to pass status code as well), or you can use static get method to customize it:

use HttpException\ServerError\InternalServerErrorException;

try {
    // ...
} catch (Exception $ex) {
    throw InternalServerErrorException::get("Server down, sorry.", $ex);
}

Exceptions hierarchy

Since version 2.0, you are able to have your API fully exception driven, because exceptions for Informational, Successfull and Redirection codes are implemented. Full hierarchy or exceptions is:

Exception
└─ HttpException\HttpException
   ├─ HttpException\InformationalException
   │  ├─ HttpException\Informational\ContinueException
   │  ├─ HttpException\Informational\SwitchingProtocolsException
   │  ├─ HttpException\Informational\ProcessingException
   │  └─ HttpException\Informational\EarlyHintsException
   ├─ HttpException\SuccessfulException
   │  ├─ HttpException\Successful\OKException
   │  ├─ HttpException\Successful\CreatedException
   │  ├─ HttpException\Successful\AcceptedException
   │  ├─ HttpException\Successful\NonAuthoritativeInformationException
   │  ├─ HttpException\Successful\NoContentException
   │  ├─ HttpException\Successful\ResetContentException
   │  ├─ HttpException\Successful\PartialContentException
   │  ├─ HttpException\Successful\MultiStatusException
   │  ├─ HttpException\Successful\AlreadyReportedException
   │  └─ HttpException\Successful\IMUsedException
   ├─ HttpException\RedirectionException
   │  ├─ HttpException\Redirection\MultipleChoicesException
   │  ├─ HttpException\Redirection\MovedPermanentlyException
   │  ├─ HttpException\Redirection\FoundException
   │  ├─ HttpException\Redirection\SeeOtherException
   │  ├─ HttpException\Redirection\NotModifiedException
   │  ├─ HttpException\Redirection\UseProxyException
   │  ├─ HttpException\Redirection\TemporaryRedirectException
   │  └─ HttpException\Redirection\PermanentRedirectException
   ├─ HttpException\ClientErrorException
   │  ├─ HttpException\ClientError\BadRequestException
   │  ├─ HttpException\ClientError\UnauthorizedException
   │  ├─ HttpException\ClientError\PaymentRequiredException
   │  ├─ HttpException\ClientError\ForbiddenException
   │  ├─ HttpException\ClientError\NotFoundException
   │  ├─ HttpException\ClientError\MethodNotAllowedException
   │  ├─ HttpException\ClientError\NotAcceptableException
   │  ├─ HttpException\ClientError\ProxyAuthenticationRequiredException
   │  ├─ HttpException\ClientError\RequestTimeoutException
   │  ├─ HttpException\ClientError\ConflictException
   │  ├─ HttpException\ClientError\GoneException
   │  ├─ HttpException\ClientError\LengthRequiredException
   │  ├─ HttpException\ClientError\PreconditionFailedException
   │  ├─ HttpException\ClientError\PayloadTooLargeException
   │  ├─ HttpException\ClientError\URITooLongException
   │  ├─ HttpException\ClientError\UnsupportedMediaTypeException
   │  ├─ HttpException\ClientError\RangeNotSatisfiableException
   │  ├─ HttpException\ClientError\ExpectationFailedException
   │  ├─ HttpException\ClientError\IMaTeapotException
   │  ├─ HttpException\ClientError\MisdirectedRequestException
   │  ├─ HttpException\ClientError\UnprocessableEntityException
   │  ├─ HttpException\ClientError\LockedException
   │  ├─ HttpException\ClientError\FailedDependencyException
   │  ├─ HttpException\ClientError\TooEarlyException
   │  ├─ HttpException\ClientError\UpgradeRequiredException
   │  ├─ HttpException\ClientError\PreconditionRequiredException
   │  ├─ HttpException\ClientError\TooManyRequestsException
   │  ├─ HttpException\ClientError\RequestHeaderFieldsTooLargeException
   │  └─ HttpException\ClientError\UnavailableForLegalReasonsException
   └─ HttpException\ServerErrorException
      ├─ HttpException\ServerError\InternalServerErrorException
      ├─ HttpException\ServerError\NotImplementedException
      ├─ HttpException\ServerError\BadGatewayException
      ├─ HttpException\ServerError\ServiceUnavailableException
      ├─ HttpException\ServerError\GatewayTimeoutException
      ├─ HttpException\ServerError\HTTPVersionNotSupportedException
      ├─ HttpException\ServerError\VariantAlsoNegotiatesException
      ├─ HttpException\ServerError\InsufficientStorageException
      ├─ HttpException\ServerError\LoopDetectedException
      ├─ HttpException\ServerError\NotExtendedException
      └─ HttpException\ServerError\NetworkAuthenticationRequiredException

With this in mind, you can catch them as you like:

try {
    // ...
} catch (HttpException\ClientError\NotFoundException $e) {
    // Only NotFoundException catched
} catch (HttpException\ClientErrorException $e) {
    // All ClientError exceptions
} catch (HttpException\HttpException $e) {
    // All HTTP exceptions from library
} catch (Exception $e) {
    // Everything else...
}