Hey everyone, Chris here from Skeleton. We hope everyone is enjoying the new the recently launch of Skeleton v3. The reception has been wonderful, and we appreciate all the kind words and well wishes you've sent our way for this massive update.

In today's post, we'll focus on a few topics:

• Cover our new sponsor incentives, including updates to our website templates
• Gather community feedback regarding new features and updates coming soon
• Discuss some notable issues we've discovered in Skeleton v3 and Tailwind v4

So let's get started.

New Incentives for GitHub Sponsors

As you may be aware, Skeleton exists in large part due to the support of our generous community through sponsorship. This ensures Skeleton remains self sufficient and helps cover the day-to-day operational costs, such as hosting, domains, services, etc.

• GitHub: https://github.com/sponsors/skeletonlabs
• Ko-Fi: https://ko-fi.com/skeletonlabs

We've revised our sponsor incentives, especially for GitHub Sponsors (our preferred service). This includes a number of improved tier incentives, especially the Gold Tier. This provides access to a private repository containing a set of curated website templates, each built by the creator of Skeleton (that's right, me!). These serve as functional examples of how to utilize Skeleton in a real-world application. Today's updates are NOT just dependency bumps, we've actually rewrote each template from the ground up to utilize new and improved techniques, best practices, and new technologies:

• Both templates have been updated to support Skeleton v3.0 (stable)
• Both templates have been updated to support Tailwind v4
• Portfolio:
  • Updated to Svelte 5 + SvelteKit
  • Features a custom Lightswitch component
  • Features $state() store that persists via localstorage
  • Now implements Lucide icons
  • Various visual and quality improvements
• Blog:
  • Now built using Astro + Svelte 5
  • Takes advantage of Astro's content collections for posts and authors
  • Uses MDX for posts, including custom MDX components for typography
  • Shiki code blocks via Expressive Code
  • Built-in site map
  • Now implements Lucide icons
  • Various visual and quality improvements

To obtain these templates, sponsor Skeleton for the Gold Tier or higher for at least one month, then browse to this private repository. You can test drive either app using the links provided below.

Portfolio Template

Blog Template

Community Feedback

As we continue to move forward, refine, and expand Skeleton, we want to ensure we continue to keep an open line of community with the community for what comes next. Today we'll be providing a short survey that may influence not only what features we implement but also the priority in which we tackle these.

Just be aware that the results may not translate directly to our final roadmap. But all feedback you provide will be taken into account, alongside with feedback from our internal team, and well as maintainers like myself. With the goal of ensuring we're handle all initiatives in the most productive manner possible.

✅ Participate in the Survey

Note: all submissions are anonymous and does not require a login to participate

Additionally, we're opening the comment sections below as an open forum for any other ideas you would like to see implemented in the future. Bring us your crazies ideas or concepts - we're listening! We just ask that you try to keep things professional and constructive.

Known Issues with v3

Finally, we wanted to ensure you're aware of a few notable issues that have come up related to Skeleton v3 and Tailwind v4. We are taking these issues very seriously and aiming to resolve asap, including temporary workarounds for now. If you have questions about these items, please feel free to reach out in the linked issues or comments section below.

Missing Core API Classes

• A lot Skeleton utilities don't actually exist #3417

First up, we've been made aware of the fact a number of the CSS classes defined in our Core API are not functional. Specifically those used for our primitive Typography styles classes, including base/heading/anchor styles.

Immediate Workaround: use the CSS custom properties to generate your own local classes that consume these values:

.base-font-color {
  color: var(--base-font-color);
}

Long-Term Fix: We will aim to release an upcoming path that inserts these via the Skeleton CSS stylesheet. When this is occurs, please undo any local classes added per the workaround above.

Permanent Fix: We'll need to rename many of these properties to adhere to the explicit Tailwind Namespaces. Unfortunately these are more specific than we originally anticipated, so this will require some breaking changes to theme properties, as they are renamed to follow the correct convention. For example:

/* Before: */
--base-font-color: ...;
/* After */
--color-base-font: ...;

These breaking changes will affect the Theme Generator, our preset themes, and provide instructions for users to migrate and update their personal custom themes. So look for this fix in a future major release (ex: v4.0).

Safari Dark Mode - Issue with OS Preference

• tailwind: core styles only present in production builds and not development #3287 (comment)
• Media queries nested inside selector is correctly processed in build mode, but not dev mode tailwindlabs/tailwindcss#16438

It appears that if you use the default settings for Tailwind v4's dark mode (based on the user's operating system preference), specifically in Safari browsers, and specifically in a local dev server - the, Color Scheme is not being applied correctly, which may cause text and other properties to display incorrectly. This is a very specific scenario, but one that could cause you some headaches!

Note that this is Tailwind bug, and not something we can likely address directly. However, if you experience this, consider manually assigning Dark Mode (at least in your dev server) using the following instructions:

https://tailwindcss.com/docs/dark-mode#toggling-dark-mode-manually

Tailwind Module-Graph Scanner

• Vite: Remove module-graph scanner tailwindlabs/tailwindcss#16631

Again another issue on Tailwind's end - but it appears they have modified the manner in which Tailwind classes are scanned and included into your CSS bundle. We're monitoring this closely, but do have a concern we may need to re-implement a new version of the PurgeCSS plugin to ensure unwanted classes are not included in your CSS bundle. We'll continue to monitor and test internally and let you know where things land asap. No action is needed on your part at this time, but if you suddenly start seeing a large CSS bundle - this may be why.