Our focus right now is on post formats integration, both structured (formats with post meta 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.) and “normal” output for the other formats.
- Work with Post Formats team to get
the_image() functions into core Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so we can avoid a ton of extra logic in Twenty Thirteen’s functions.php file to grab the first asset for a format. Making it easier for *any* theme to get the same data back and keep their template files simpler. Themes should not have to parse shortcodes or try to make something run through oEmded before display.
- Work with Post Formats team on
post_formats_compat() functionality, improving Quote markup and filling in the gaps for other formats. Obenland is going to work on a patch 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. for this.
- Image: we need clarification from 3.6 leads and Post Formats team on whether it is going to be structured or not (post meta) and it needs more work for the post-media functions (see 1 and 2 priorities above)
- Finalize each post format in Twenty Thirteen: what template HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. or PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher it needs, what it needs from core functionality to work correctly
By post format
Here’s a breakdown per format, per today’s discussion (IRC log).
- Standard: good to go
- Aside: we remove the title from the PHP template, added styling; non-structured
- Chat: IHNIWIGOWTPF (see IRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. log, hehe); non-structured
- Gallery: we use a bit of PHP to remove default gallery styles, and we use a filter 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 change the image size to large on index view, then add a bit of CSS Cascading Style Sheets. fanciness to change the first image to “bigger” size, 300×300 (single view is not changed other than to align the columns); non-structured
- Link: structured, we use
get_the_url() wrapped in our own fallback to output permalink if no URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is found
- Image: right now it works OK without any changes, but the design calls for the image to be above the title, which means we need a way to pull out the first image, and have
the_content() be output without that image; also filter
content_width to 724 for this format (small issue with that reported in #23863). Seems like the best approach here is to use a custom image size to grab an exact 724 px wide image (unless it’s smaller that 724, in which case we grab the largest available). Ideal: a user uploads an image, adds it to the post content at exactly 724 from the Media editor, then
the_image() outputs the exact HTML img tag 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.) + attributes.
- Quote: structured; currently we rely on people using
blockquote correctly in the editor, and style it with CSS; after Obenland’s patch to Quote markup (noted above in priority 2) we’ll add CSS support for the structured HTML markup, and leave in the basic styles in case someone uses post content anyway
- Status: similar to Aside
- Video: structured; we filter
content_width to 724 to allow the video to be wider than the rest of the content area; needs
the_video() to return the HTML output of first video and remove the same from the post content
- Audio: structured, we’re leaning towards using the post format compat output instead of a custom structure in the theme; needs more testing but seems to be working OK as-is right now