Tag Archives: 4.1

Kira Schroder 12:27 pm on October 8, 2014
Tags: 4.1,   

Last Week in WordPress Core

Hi Everyone!

It’s time for Last Week in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.! This update covers through Sunday, October 5th, and contains many commits from WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe. Yay! Things are rolling along well, including first passes on pinning the adminadmin (and super admin) menu, and many fixes to media and image handling. A complete summary is below.

Name Change?
It’s been suggested that we change the name of this post to “Core Weekly,” because apparently there has been confusion about this being the last week of WordPress Core, which would just be sad. I like the name idea. Any comments or suggestions?

Admin

  • First pass at pinning the admin menu on scrolling similarly to how the side metaboxes are pinned on the Edit Post screen. [29835] #29806
  • Add classes to form containers on Edit User and taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. screens. [29803] [29804] #29348 #28196
  • Add default z-index to the admin menu, see [29841] #29806
  • Use correct context for “Name” and “Parent” strings on taxonomy screens. Remove unnecessary context for “Slug” and “Description” strings. [29821] #29824
  • When switching to the Text editor, make the textarea visible to screen readers. [29815] #29815
  • Add a default filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to title_save_pre to avoid extra whitespace. [29801] #19904

Media

  • Account for MEDIA_TRASH in both the Media Grid and Media List Table. [29810] [29811] [29812] #29742
  • Add the date filter from media grid to the media modal. [29813] #28990
  • Add a namespace to the click handler registration for .insert-media in media-editor.js: click.add-media-button to allow devs to override the default behavior. [29802] #23096
  • In wp_delete_attachment(): account for orphan sizes by looping over the sizes stored in metadata, instead of relying on the current sizes stored in $_wp_additional_image_sizes. [29816] #24518
  • For attachment-compat fields, show a spinner while wp.media.model.Attachment.saveCompat() is firing. #27028 [29831]
  • In the admin, give media list table icons auto for width and height. In the post thumbnail metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way., apply width: auto. If someone turns on support SVG files, this will allow them to show up. [29832] #26256
  • Allow PSDs (Photoshop documents) to be uploaded. [29833] #28805
  • Fix setting default quality in WP_Image_Editor. [29834] #29856
  • Pass the requested size to wp_get_attachment_image_attributes filter. [29836] #29869

Networknetwork (versus site, blog) Admin

  • Don’t display update count for Themes when the user doesn’t have the update_themes cap. [29817] #29651
  • Don’t display update count for Plugins when there aren’t any/count is 0 [29817] #29651
  • Properly check if the theme is active on the main site to avoid deleting it via bulk actions. [29839] #29861

Plugins

  • In activate_plugin(), do not re-run the activation routine for already-active network-wide plugins. [29818] #28651
  • Avoid a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher notice in list_plugin_updates() if plugins_api() returned a WP_Error object. [29825] #29583
  • Use correct links for filtering pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party reviews. #29826 [29754]
  • Plugin search: Wrap results in a form to fix pagination’s paged input field. #18724 [29829]
  • Pass the requested size to wp_get_attachment_image_attributes filter. [29836] #29869

Users

  • In the wp_new_blog_notification() email template, include the login url. [29806] #21089
  • Always sanitize user_nicename in wp_insert_user() to avoid broken author archive permalinks. [29819] #29696

Comments

  • WP_Comment_Query: comment__in, comment__not_in, post__in, post__not_in. [29808] #25386
  • Add a class attribute for submit button in comment form. [29809] #20446
  • Add an aria-label attribute with commenter’s name to get_comment_reply_link(). [29822] #16433

Thanks to @afercia, @andg, @andrewryno, @arippberger, @avryl, @azaozz, @bainternet, @boonebgorges, @ccprice, @desrosj, @ericlewis, @georgestephanis, @janhenckens, @jarednova, @jb510, @jbrinley, @jeremyfelt, @jesin, @joedolson, @joemcgill, @JoshuaAbenazer, @karpstrucking, @markoheijnen, @mattheu, @merty, @michalzuber, @mordauk, @nikolov.tmw, @nofearinc, @obenland, @ocean90, @OriginalEXE, @paulwilde, @peterchester, @SergeyBiryukov, and @wonderboymusic for their contributions this week, and to @swissspidy for help in compiling this post.

This post covers revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. [29800] to [29841]. For the complete list of commits to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision., check out the log on trac. Interested in joining in? Write or test a patch for 4.1. Also, don’t miss the weekly meeting today at 20:00 UTC.

#4-1, #week-in-core

Helen Hou-Sandi 2:53 am on October 8, 2014
Tags: 4.1, ,   

Scalable Dropdowns and More, chat on 2014/10/8

In 3.9, I started taking a look at solving some long-standing scaling issues with dropdowns, notably those for users (#19867) and pages (#9864). I arrived at a conclusion about our mixed usage of autocomplete and autosuggest far too late to make it for 3.9, and did not add it to my plate for 4.0, but would like to tackle it again for 4.1.

We can solve these issues smartly by using a combination of Ajax-powered autocomplete/suggest and smart defaults, e.g. users with the most content pre-loaded for quick access without having to run a search. As a brief overview of where I see us going with this – a roadmap, if you will: user dropdown, page dropdown, current instances of jQuery UIUI User interface autocomplete (multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site users and new site), tags/nonhierarchical taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. UI, more built-in taxonomy UIs (#14877), and possibly more as we discover appropriate places. Not all of this will happen in 4.1 – think of this as not only a solution to long-standing, painful problems, but also a step in a series of many.

To that end, we will be holding an initial chat at 19:00 UTC on 2014/10/8 to get things moving. @ericlewis and I have begun early development as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party – for more, see this particular branch, which experiments with using Select 2 as a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. helper library for the UI.

#4-1, #dropdowns, #plugins

John Blackbourn 3:40 pm on October 3, 2014
Tags: 4.1   

4.1 development is under way

WordPress 4.1 development is under way. See the release schedule for the key dates.

Here’s an overview of the headline features for this release. If you’d like to get involved with mockups, design, development, documentation, testing – anything really – see the users and tickets listed below each item.

Other areas which will receive attention during this release:

  • Early stages of our taxonomy roadmap, mainly related with @boonmgorges‘s work on query improvements.
  • Accessiblity improvements in conjunction with the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team.

#4-1

Boone Gorges 12:38 am on October 2, 2014
Tags: 4.1   

Meta, Date, and Tax Query improvements in WP 4.1

For WP 4.1, I’ll be working on improvements to WP_Meta_Query, WP_Tax_Query, and WP_Date_Query, the Three Tenors Three Stooges Three Amigos of WordPress. Here’s a summary of the proposed changes, with some notes about where help is needed.

Unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. coverage

Test coverage for these three classes has historically been pretty spotty, but is absolutely critical for any meaningful refactoring to take place. I’ve meticulously picked over them and created a set of comprehensive tests for each one (#29560, #29718, #29781). Coverage is now quite good, but more eyes are always welcome.

Multi-relational and nested queries

All three classes currently accept a ‘relation’ parameter, which allows multiple query clauses to be joined with AND or OR. So, for instance, you can query for: posts that are in the ‘Boone’ categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. AND have the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) ‘Awesome’ AND do not have the term ‘Raphael’ in the favorite_turtle taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.. But this syntax only allows for so much expressiveness: you can’t mix AND and OR, and you can’t group clauses. These limitations make it difficult to use these queries in support of complex content filtering – like you might need, say, if you’re using WordPress to power the inventory system for an online store.

For 4.1, I’ll be working on allowing the necessary syntax for multi-relation queries that can be grouped and nested to an arbitrary depth. See the following tickets for patches and discussion:

  • #29642 MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • #29738 Tax
  • #29822 Date

Much of the infrastructure that will support the new syntax will be shared between the classes. If you’re familiar with current WP_*_Query internals, you may want to check out the patches and join the discussion at the WP_Meta_Query ticket, which is the furthest along of the three classes in this refactoring process.

Miscellania

Once the changes discussed above are in place, there are a number of smaller but equally lovely improvements I’d like to begin addressing:

  • #29181 ‘EXISTS’ and ‘NOT EXISTS’ operators for WP_Tax_Query
  • #29823 WP_Date_Query across tables
  • #24093 Improve WP_Meta_Query performance by switching to subqueries rather than table joins. This is one where we could use lots of testing; if you know how to set up a VM with an old version of MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/., then your help would be appreciated.

Do you have other ideas for how these three classes could be improved in 4.1 and beyond?

#4-1

Scott Taylor 9:45 pm on October 1, 2014
Tags: 4.1   

4.1: Call for Tickets

What tickets would you like us to look at in 4.1? (Extra points if it already has a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..)

Since the release is officially underway, now is a great time for us to prioritize work and make sure our pet projects/tickets get some airtime. The priorities of the community matter. Let us know below what you would like to see in WordPress 4.1.

#4-1

John Blackbourn 5:48 pm on October 1, 2014
Tags: 4.1,   

Agenda for October 1st dev chat

We’ll be discussing 4.1 in today’s dev chat (October 1 2014 20:00 UTC). The release schedule can be found here.

Here’s the agenda:

  • Decision time for features being developed as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. See Ryan’s overview of what was discussed on Monday. Also need to discuss the menu customiser work by @celloexpressions.
  • Very brief update on Twenty Fifteen theme from @obenland.
  • Improved UIs for installing and updating plugins, themes, and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Who wants to help with design mockups, UXUX User experience, dev? Needs a ticketticket Created for both bug reports and feature development on the bug tracker. for each.
  • @Helen and @MarkJaquith both have focuses for 4.1. Do we have tickets for all of the various components? Who’s helping out?
  • Accessibility ticket priorities.
  • @rboren has been documenting various mobile media management issues. Who’d like to help address these? Probably needs a bunch of individual tickets.
  • Language switcher on the General Settings screen: #29395. Per-user setting has been proposed again: #29783. Who’s interested? cc: @SergeyBiryukov @ocean90
  • Query enhancements coming in from @boonebgorges. Unit testing and general dev help needed?
  • Keeping the 4.1 milestone under control. @wonderboymusic.

We won’t be touching on 4.0.1 this meeting unless something specific comes up (nacin will be on a flight). An RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). for 4.0.1 is expected by the end of the week.

Anything else you’d like to discuss? Leave a comment.

#4-1, #agenda

Ryan Boren 5:12 pm on September 30, 2014
Tags: 4.1, ,   

4.1 Kick-off Meeting, 2014/09/29

These are my rough highlights from yesterday’s kick-off meeting. They emphasize who is working on what.

https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2014-09-29&sort=asc#m929822

johnbillion:

Preliminary session management interface: https://i.imgur.com/sHz2oeV.png
There’s a repo: https://github.com/johnbillion/wp-session-manager/

Various tasteful and sensible people:
“We might end up calling this the Keep Ryan Happy release”
“the rboren happy release, for those who don’t know, is fixing and improving mobile stuff”
“ryan deserves happiness. Not just because I want mobile and media too :)”

johnbillion:
Also on the list is improvements to the UIUI User interface when installing and updating plugins, themes, and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. I want to get rid of the ancient UI which has been in core since we first started doing updates inside core

markjaquith:
So, one of the things I originally wanted to do (and avryl had in early versions of the Focus pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party) was to do some fading of the rest of the UI when you are actively typing into a post. I think this would get us the rest of the way to DFW’s feature set.
So my goal for 4.1 would be to remove DFW completely.
We also could/should do the fancy scroll behavior for the menu like we do for post side metaboxes.

nacin:
1) the theme will be ready by October 25
2) if the theme is not on track for that, the default themes are matt’s pet project, and he will allocate appropriate design and development resources to make sure it will be ready by October 25

johnbillion:
One last feature that I forgot, I’d love to get the language chooser on the General Settings screen to be able to download and install new languages like we planned for 4.0 but had to get punted

helen:
mentioned this a couple weeks ago i believe, ericandrewlewis and i are experimenting with tackling some tickets as a plugin to start so we can move faster: https://github.com/helenhousandi/wp-19867-9864
currently working on a branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". that uses select2 to help with scaling issues with the users dropdown – would look to bring this to pages, tags/nonhierachical taxonomies, and the multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site add user and add site forms.

DH-Shredder:
I’d like to do some work with markoheijnen on getting a few of the image manip APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. improvements in before image-flow

netweb and helen:
#22435 Export API <- Would be great to get this in, has-patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., needs-testing, adds export unit tests to core and that will help other export related tickets.
https://github.com/hlashbrooke/Export-Plus

boonebgorges:
I’ll be working on syntax and internal improvements for WP_Tax_Query, WP_Date_Query, WP_Meta_Query. Berzerk test coverage, support for multi-relational/nested queries, some other goodies. See eg #29738

jeremyfelt:
I want to get a bunch done around multisite unit testing and rewriting some old junk to clean things up a bit. This should help us start moving steadier with other improvements.

boonebgorges:
Also want to investigate moving WP_Meta_Query to subqueries rather than JOINs because of the massive crappiness of JOINing the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tables. May not have time for 4.1, but will start doing some benchmarks. #24093
https://core.trac.wordpress.org/ticket/24093 Future Release, sc0ttkclark->(no owner), new, WP_Meta_Query is inefficient when referencing the same keys in “OR” query

boren:
I’ll be evangelizing flow and visual records. http://simp.ly/publish/rBkqyq

#4-1, #kickoff, #meeting

Andrew Nacin 11:25 am on September 27, 2014
Tags: 4.1, ,   

John Blackbourn is leading WordPress 4.1 (and announcing new committers!)

I’m pleased to share John Blackbourn (@johnbillion) is the release leadRelease Lead The community member ultimately responsible for the Release. for WordPress 4.1. But please hold your applause until the end, I have a few announcements to get through!

WordPress 4.1 will be kicking off at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe this weekend. As noted yesterday, the first meeting will be at 1400 UTC on Monday, September 29.

You’ve probably seen John in action over the years (his first contribution was more than seven years ago). I’ll also add it’s pretty awesome that @simonwheatley and @s1m0nd of Code for the People (a six-person shop) jumped at the chance to donate a large chunk of John’s time through the end of the year back to the WordPress project. (See also this post for more on the release lead role.)

New committers for WordPress 4.1

As many of you know, the lead developers review and appoint new committers to serve each release cycle, often to work on a particular component or feature. This guest commit access comes up for review after each release and can be renewed. I in particular work closely with every guest committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., providing feedback.

I’m pleased to announce our largest guest committer class ever: Gary Pendergast (@pento), Boone B. Gorges (@boonebgorges), Konstantin Kovshenin (@kovshenin), Aaron Jorbin (@jorbin), and Jeremy Felt (@jeremyfelt).

Konstantin and Gary both enjoy diving into internals and getting their hands dirty with tough bugs and regressions. Jeremy will be continuing to push multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site forward. Jorbin will be focusing on testing and tooling. Boone has been working on a set of great improvements to tax, date, and metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. queries, with test coverage to come with it.

These five should be strangers to no one — they’ve all been around the community for years, and not only are they top-notch contributors who embody the project, but they’re generally just really good people.

This will also be John Blackbourn’s third release as a guest committer. I’d also like to welcome back Ian Stewart (@iandstewart), who previously was a committer during the development of Twenty Eleven, and will be back to take the commit reins for the next default theme, Twenty Fifteen.

Scott Taylor (@wonderboymusic) was on fire during 4.0, especially if this terrific post is any testament, continuing a great run. Scott’s WP origin story is pretty great — right as he was getting ready to leave the WordCamp San Francisco 2011 after-party, @koop convinced him to stick around a little longer. We were introduced, and not long after (from the party) his first patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. got committed. A thousand contributions later that have made an indelible impact, Scott is now a permanent WordPress committer. We hope to have him around for a long time.

About a year ago Drew Jaynes (@DrewAPicture) was given commit access to lead the hook documentation effort. This was hugely successful. After the effort was complete, Drew’s role evolved into maintaining all inline docsinline docs (phpdoc, docblock, xref), which has just been wonderful. We appreciate his attention to detail and his dedication to this never-ending effort. Drew is now a permanent committer.

Congratulations to John, Drew, Scott, Gary, Konstantin, Jeremy, Jorbin, Ian, and Boone!

#4-1, #commit, #release-lead

Andrew Nacin 7:56 pm on September 26, 2014
Tags: 4.1, ,   

Announcement 4.1 kickoff meeting this Monday September 29…

Announcement: 4.1 kickoff meeting this Monday, September 29, at 1400 UTC. This is an unusual time for us that we’d like to try out. The Wednesday meeting (October 1) is still on for 2000 UTC as well.

Around the world:

  • 10am U.S. Eastern (GMT-4), 7am U.S. Pacific (GMT-7).
  • This is midnight Tuesday for east coast of Australia (GMT+10).
  • If you’re at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe’s contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. (GMT+3), this will be 5pm.

More to come with regards to 4.1 over the weekend, but I wanted to make sure everyone saw this (as it was decided at this week’s dev meeting). But please think about what you’d like to work on or what you’d like to see. This comment thread is also open.

This initial post said Monday, September 28. Monday is September 29, and that’s the day of the meeting.

#4-1, #agenda, #meeting

Konstantin Obenland 11:57 pm on September 9, 2014
Tags: 4.1, , ,   

Twenty Fifteen

It’s that time of the year again, time to work on a new default theme!
This year we’re back to creating a brand new design. Like Twenty Fourteen, this is being targeted for December and thus WordPress 4.1.

@matt asked Takashi Irie to design Twenty Fifteen, and they are both closely collaborating with @iandstewart, who also worked on Twenty Ten and Twenty Eleven. The design is far from finished, but the following screenshots might give you an idea of what direction it is headed this year:

Twenty Fifteen is a clean, blogblog (versus network, site)-focused theme designed through simplicity. With careful attention to typography, the theme treats text as a major part of the user interface. It features Google’s Noto Serif and Sans – a font family designed to be visually harmonious across many of the world’s languages, and a perfect fit for the internationalization strides being made in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

The theme is also designed to maximize the impact of core’s customization tools – Custom Headers and Custom Backgrounds. These tools will allow any Twenty Fifteen blog to be easily personalized.

Last but definitely not least, Twenty Fifteen uses a mobile first approach in its design, remaining attractive and focusing on an optimal browsing experience across a wide array of devices from mobile to widescreen desktops.

All of these things come together to present content cleanly for any of Twenty Fifteen’s users – a simple default theme.

—Takashi Irie

Next steps will be to finish the design, create a working theme, commit that to core, and then break it and make sure it adheres to the high standards and expectations we all have for default themes.

If you are interested in contributing, please subscribe to this blog (if you haven’t already), and leave your name in the comments. As soon as it’s ready for public breaking, testing, and patching, I’ll make sure you get a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.”!

Further reading:

#4-1, #bundled-theme, #themes, #twentyfifteen