Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#27084 closed enhancement (invalid)

Unbundle older themes

Reported by: hlashbrooke's profile hlashbrooke Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9
Component: Bundled Theme Keywords:
Focuses: Cc:


If this is not on the roadmap at all then please just close this ticket.

It seem unnecessary to have the older default themes still bundled in core. Twenty Fourteen is stable and shows off WordPress' default functionality well. I propose removing all themes prior to Twenty Fourteen (i.e. Twenty Ten, Twenty Eleven, Twenty Twelve & Twenty Thirteen), or maybe keeping only the current theme and one prior (currently Twenty Fourteen & Twenty Thirteen) as having two bundled themes would demo the theme selection page a little bit more for new users.

Removing all of the older themes would reduce WP core by about 3.6 MB, which is obviously a win, but if all the themes are still included for a good reason then feel free to ignore everything I'm saying :)

Change History (8)

#1 @TobiasBg
10 years ago

  • Component changed from Themes to Bundled Theme
  • Keywords dev-feedback added

WordPress 3.8 shipped with TwentyFourteen, TwentyThirteen, and TwentyTwelve, which is a good consensus given that the themes target different audiences (magazine-style, blogging-style, etc.), and given the time of release for TwentyFourteen (before the named year and not in the second half as happened in the previous years). So, fresh installs only get those. If a site is upgraded and had previous default themes installed, those will be kept.

Related: #22500

Unbundling TwentyTwelve and maybe TwentyThirteen should probably not be necessary until TwentyFifteen ships.

Suggesting "Future Release" to leave it as a reminder.

#3 @hlashbrooke
10 years ago

I saw that we have all the way back to Twenty Ten in trunk, so figured we were going to be including them in each release. Perhaps we should remove them from truck then? Seeing as though the are in the themes repo anyway.

Makes sense to have all three themes in the release if they each serve a specific purpose, so happy to close this ticket off.

Thanks for the IRC logs Sergey!

#4 @SergeyBiryukov
10 years ago

So, older themes (Twenty Ten and Twenty Eleven) are still in the repository, but they're not actually bundled anymore. We still accept patches for them here, so I guess we're going to keep them in the repository for now.

The discussion on which themes to bundle happens when a new default theme is ready. Older themes are excluded from zip packages during the build process, so this would be a ticket for the milestone, but we probably don't need a separate ticket for that.

#5 @hlashbrooke
10 years ago

Gotcha - thanks for clarifying all that :)

Feel free to close this ticket if necessary.

#6 @lancewillett
10 years ago

  • Keywords dev-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

#7 @ocean90
9 years ago

#31991 was marked as a duplicate.

#8 @paaljoachim
9 years ago

What about a code snippet to automatically remove the older themes....?
It would be a halfway there solution.

Note: See TracTickets for help on using tickets.