Skip to content

Instantly share code, notes, and snippets.

@arshaw
Last active March 28, 2025 16:01
Show Gist options
  • Save arshaw/04178a661f600a67bcceae3ae7437502 to your computer and use it in GitHub Desktop.
Save arshaw/04178a661f600a67bcceae3ae7437502 to your computer and use it in GitHub Desktop.

Overview

The goal is make a powerful theme system that BOTH established components libraries can leverage, as well as developers wanting one-off advanced customizations. With an eye towards Tailwind usage. Most changes will be additive, exposing additional hooks for themes to leverage, and there will be very few breaking changes.

Issues to Address

  • Tailwind support: #5868
  • Exposed theme system: #4332
  • Custom elements in toolbar: #496
  • Emphasized lines on day/week boundaries: #4864
  • Buttons
    • ClassNames on custom buttons: #6094
    • Custom HTML within buttons: #3316
  • Icons
    • Use SVG icons (for standard theme): #5685
    • Optional loading of icons (via forked/custom theme): #7698
  • Dark-mode first-class support
    • Bootstrap theme: #7465
    • Standard theme, and other themes
  • Packaging
    • Separate theme CSS from non-theme CSS: #3564
    • For CSP, don't inject CSS via JS: #7353

A number of other theme-focused features will be implemented as well.

Planning Calendar Settings

The new theme system has to align with our many future plans, which we had to contemplate in much more detail. We've spec'd out where we want to go and how v7 fits into the larger plan. We've come up with a concrete list of settings we need to introduce for v7:

FullCalendar v7 Revised Settings »

Time Estimate

Development will begin April 1st. The goal is to have a release candidate with docs ready 8 weeks later, on May 27th. This is just an estimate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment