This repository tracks the output of the _tw WordPress starter theme generator with all options left blank.

Right now there isn't a public repository for the generator itself. Please post issues regarding the generator to this repository.

If you're starting a new project, the generator is the best way to do that. You can also read the documentation for more details.

Note
The default contents of README.md in a generated theme are as follows:

A custom theme based on _tw

1. Move this folder to wp-content/themes in your local development environment
2. Run npm install && npm run dev in this folder
3. Activate this theme in WordPress

4. Run npm run watch
5. Add Tailwind utility classes with abandon

6. Run npm run bundle
7. Upload the resulting zip file to your site using the “Upload Theme” button on the “Add Themes” administration page

Or deploy with the tool of your choice!

• Installation
  Generate your custom theme, install it in WordPress and run your first Tailwind builds
• Development
  Watch for changes, build for production and learn more about how _tw, WordPress and Tailwind work together
• Deployment
  Share your new WordPress theme with the world
• Troubleshooting
  Find solutions to potential issues and answers to frequently asked questions

• Using Tailwind Typography
  Customize front-end and back-end typographic styles
• JavaScript Bundling with esbuild
  Install and bundle JavaScript libraries (very quickly)
• Linting and Code Formatting
  Catch bugs and stop thinking about formatting

• On Tailwind and WordPress
  Understand how WordPress and Tailwind work together
• Managing Styles for Custom Blocks
  Learn strategies for using Tailwind in theme-specific custom blocks
• Setting Up Browsersync
  Add live reloads and synchronized cross-device testing to your workflow

Note
The default contents of README.md end here.

All notable changes to this project will be documented here.

The format is based on Keep a Changelog.

• Ensure changes to theme.json update tailwind.config.js during watch process (#79)
• Support Yarn (#77)

• Support for block editor styles in WordPress 6.3 (#60)

• Automatic versioning in the zip file generated by npm run bundle
• More detailed documentation in README.md

• Update to Tailwind 3.3
• Revisit approach to Tailwind Typography
• Improve comments throughout

• @tailwindcss/line-clamp and postcss-simple-vars

• @wordpress/prettier-config and eslint-config-prettier

• Use Prettier to format JavaScript files
• Install ESLint directly and use the eslint:recommended configuration
• Set ecmaVersion to latest throughout

• @wordpress/eslint-plugin

• Update to Tailwind 3.2
• Revisit approach to Tailwind Typography

• Tailwind Typography support for comments
• @tailwindcss/container-queries

• Finish restructuring theme files with improvements from Varia
• Update Tailwind Typography selector
• Clean up package.json scripts

• composer.lock and package-lock.json files

• Default theme support for core custom background and custom logo functionality
• Default setting for content_width

• Update to Tailwind 3.1

• The postcss-import module, as its functionality is included with Tailwind 3.1

• Include a style.css file containing only the WordPress file header
• Add quickstart instructions to README.md

• Update documentation to focus on installation without symlinking
• Update file header

• JavaScript build process using esbuild
• Tailwind plugin for Prettier (for use in CSS files)
• Tailwind plugin for eslint (for use in PHP files)
• A components folder, automatically including CSS files within
• Support for nested declarations by default
• Tailwind Typography support for TinyMCE and the classic editor

• Restructure theme files with improvements from Varia
• Base phpcs.xml.dist upon WordPress Coding Standards sample file
• Improve Tailwind Typography block editor support

• Customizer and Custom Header support

• Schema to theme.json file
• postcss-simple-vars to change CSS selectors based on build target

• Update tailwind.config.js for Tailwind 3
• Move Tailwind Typography modifier classes into tailwind/custom/components.css
• Simplify Tailwind Typography configuration file
• Switch from @_tw/typography to @tailwindcss/typography
• Improve comments throughout

• Alpine.js
• Stylelint
• Separate configuration files for front-end and editor builds

• Use .prose as our Typography selector

• Support for Tailwind Typography in the block editor
• Support for theme.json in Tailwind
• Styles for the block editor's content, wide and full widths
• A basic theme.json file
• Classes for entry-title and entry-content

• There are now multiple .eslintrc files to handle the differences between node and browser linting

• Build process migrated from Laravel Mix to Tailwind's own CLI via npm-run-all

• Repository made public with initial functionality

• Record screencasts covering installation, development and deployment
• Create a WP-CLI package