Twenty Seventeen Meeting Notes: Sept. 30 2016

Here’s the meeting summary for this week. If I missed anything, let me know in the comments.

Housekeeping

Summary

The group:

  • gave an update on the theme’s progress. Lots of PRs merged this week, plus the design implementation should be done early next week. From @laurelfulford: “I’m aiming for Monday at the latest to have the design PR ready to merge. There will still be minor issues, but it’s at the point where it’ll benefit from everyone else’s eyes.”
  • labeled a handful of issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ that hadn’t been triaged yet.
  • discussed issue on fonts and non-latin fallbacks. It now has a list of alphabets the theme aims to support. Next steps include coming up with font stacks for each choice and figuring out implementation strategies.

#4-7, #bundled-theme, #twenty-seventeen

Twenty Seventeen: Agenda for Sept 30, 2016 Meeting

Here’s the agenda for today’s weekly meeting on Twenty Seventeen. It will last 30 minutes, and I’ll be around in the #core-themes channel for at least 30 minutes afterward to answer any questions.

  • General theme update.
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. as many issues and pull requests that haven’t been labeled yet.
  • Better support for non-latin font fallbacks.
  • Open floor.

Reminder: Meetings are every Friday at 18:00 UTC. Twenty Seventeen Features meeting every Tuesday at 17:00 UTC.

#4-7, #bundled-theme, #twenty-seventeen

Twenty Seventeen Features Meeting Notes: Sept. 27 2016

Here’s the meeting summary for this week. If I missed anything, let me know in the comments.

Housekeeping

Summary

The group:

  • Discussed #37974 and what the options were for possible implementation. Those include: theme options, nav menus and child pages.
  • Mostly agreed that nav menus had a lot of positive things that could be inherited for this feature. Beside a familiar UIUI User interface, the internal data structure is solid and flexible for future changes and growth, and there are several ways to improve the experience to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it more discoverable, such as with menu fallbacks in the customize preview.
  • Talked about “fragments” and how this feature might work when a full page is assembled via those fragments. The fragments wouldn’t be viewable on their own.
  • Talked about how child pages are grouped together on the edit screen but don’t have good UI for page structure management.
  • Mentioned theme options and how many themes do this kind of thing now, but it lacks portability and themes can do it in many different ways.
  • Talked a bit about how themes might output the assembled content. Maybe it uses a version of the_content().
  • Noticed that drag and drop ordering came up a lot – especially in relation to concepts users get in menus and widgets.
  • Brought up the idea of adding other pages’ content inside a page. Pages in a page. But that could be getting too far into content blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. territory.
  • Shared ideas about where this might live: in the edit screen, the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. or a combination.
  • Decided to have @karmatosed sketch out some of these ideas. Others are welcome too!
  • Brought up video headers, #38172, to get more eyes on it.
  • Discussed dummy content, #38114, after the official meeting. Chat archive starts here.
  • Talked about a potential direction for dummy content that’s showing it when live previewing, using JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. as a potential format and having a set of dummy content in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. that themes could utilize.
  • Decided to research what type of content themes might need. It may be smart to divide content by theme types.

#4-7, #bundled-theme, #twenty-seventeen

Twenty Seventeen Meeting Notes: Sept. 23 2016

Here’s the meeting summary for this week. If I missed anything, let me know in the comments.

Housekeeping

Summary

The group:

  • labeled a handful of issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ that hadn’t been triaged yet.
  • discussed ideas for handling the home page layout. #37974 will become the “master” ticketticket Created for both bug reports and feature development on the bug tracker. for this. All discussion related to improving this part of themes should happen there – in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and not on GitHub. Many ideas were mentioned, but the first step agreed on was mapping out user flows. See A shorthand for designing UI flows for context.
  • decided to have a second meeting for the features around Twenty Seventeen, like the one discussed in #37974. That meeting will be every Tuesday, at 17:00 UTC in #core-themes.

#4-7, #bundled-theme, #twenty-seventeen

Twenty Seventeen: Agenda for Sept 23, 2016 Meeting

Here’s the agenda for today’s weekly meeting on Twenty Seventeen. It will last 30 minutes, and I’ll be around in the #core-themes channel for at least 30 minutes afterward to answer any questions.

  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. as many issues and PRs that haven’t been labeled yet.
  • Handling the home page layout. See: Pull #62, #19627, #16379, #38013.
  • Open floor.

Reminder: Meetings are every Friday at 18:00 UTC.

#4-7, #bundled-theme, #twenty-seventeen

Twenty Seventeen Kickoff Meeting Notes

Today, we had a kickoff meeting for Twenty Seventeen! See the introductory post for some details.

A few housekeeping notes:

  • Slack archive of meeting.
  • This meeting was short notice, but I plan on posting an agenda each week prior to the meeting.
  • No meeting next week, but watch out for posts here about tasks related to Twenty Seventeen.
  • Next meeting is Sept. 23rd.
  • Meetings are every Friday at 18:00 UTC in #core-themes in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Our agenda was:

Introduction to Twenty Seventeen

  • This meeting really has two main focuses: Gather help, and a design review.
  • Twenty Seventeen aims to show that the one-page look and feel is possible in a WordPress theme.
  • And the bullet points in the announcement post get directly to that:

A better flow for using a static page as your front page.
Visible edit icons in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., replacing the current hidden shift+click method.
Expanding custom headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. images to include video (think: atmospheric video headers!).
Dummy content for live previews.

Ways to help

We discussed a few of the above bullet points in more details but tried to stay out of talk of implementation. We focused on how to best break the work up and what the first steps would be. There’s many ways to help with Twenty Seventeen this year that don’t involve the theme itself or code.

Specifically:

  • #19627 Themes should be able to opt-in to a static front pageStatic Front Page A WordPress website can have a dynamic blog-like front page, or a “static front page” which is used to show customized content. Typically this is the first page you see when you visit a site url, like wordpress.org for example.: Document what other services, platforms and themes do to help inform a bunch of things, including page-on-front changes. @melchoyce will take a look at the WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ flow for front page setup and related things to get this started.
  • Dummy content for live previews: @helen described this as: “So, dummy content would be something like a text widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. with business hours appearing in live preview (currently known in the form of the customizer) if there are no widgets in that area yet. That shows users a) there’s a widget area there (otherwise it’s just empty right now, or maybe has like, a search box and a login link at best), and b) what content might work really well there and what it’s going to look like.”
  • #37974 Add multi-panel feature to pages through add_theme_support: @karmatosed created this ticketticket Created for both bug reports and feature development on the bug tracker. and has ideas on how to move forward with it.

Who wants to help?

  • Front page flow: @mor10, @aaroncampbell offered to help here.
  • Video headers: Myself, and @celloexpressions have interest here.
  • Dummy content: @helen will help get this moving.
  • Visible edit icons in the Customizer: We need help here, but should have details soon on this. See: #27403.

If you want to help on any of these, and missed the meeting, no problem! Comment here and I’ll do my best to get you pointed in the right direction.

Design review/feedback

@melchoyce lead the design review:

Here are the current mockups, for reference: https://cloudup.com/cR_df4xfeeG

Mel’s to-dos she’ll be working on in the next week: https://cloudup.com/cRPc_k7MnIb

Points discussed:

  • Extremely wide screens + what happens to images that are not wide enough to be full-bleed.
  • Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure color contrast requirements are met.
  • Mel wants to explore pull-quote styles and color schemes.
  • Really rock-solid support for non-latin alphabets should be explored.

Questions, Next Steps, Etc.

  • The schedule is listed above.
  • What about browser support? See this issue from Twenty Sixteen, which Twenty Seventeen will follow.

The theme is now on GitHub. A few things to keep in mind:

  • The theme is a fork of Lodestar, a theme designed by Mel and built by @laurelfulford. It’s an excellent base to start with and what you’ll see on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
  • The design isn’t implemented.
  • A lot of other work remains too, and issues will be created in the coming week to help guide the process.

Again, if you want to help, comment here. If you have questions, just ask. It’s time to get to work! 🙂

#4-7, #bundled-theme, #twenty-seventeen

Say Hello to Twenty Seventeen 👋🏽

It’s that time again: time to build a new default theme for WordPress!

WordPress 4.7 will launch with a brand new theme – Twenty Seventeen. Designed by Mel Choyce (@melchoyce), Twenty Seventeen sports a modern look and will makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). a good base for any business website or product showcase.

twenty-seventeen-promo-png

Check out the gallery below to preview our next default theme at full-size:

(Higher resolution mockups)

In addition to having a wide appeal, Twenty Seventeen will focus on providing a seamless initial theme setup so anyone can set up a website for themselves or their business with minimal hassle.

Twenty Seventeen aims to show off some new coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. features and enhancements, such as:

  • A better flow for using a static page as your front page.
  • Visible edit icons in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., replacing the current hidden shift+click method.
  • Expanding custom headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. images to include video (think: atmospheric video headers!).
  • Dummy content for live previews.

Mel will keep an eye on all things design during the creation of Twenty Seventeen. Laurel Fulford (@laurelfulford) and David Kennedy (@davidakennedy) will assist her, leading the theme’s development. Lots of opportunities exist this year for getting involved with Twenty Seventeen – we need your help, and lots of it! 🙏🏽

Backing up the Twenty Seventeen team will be a team focusing on the core Themes 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.. This team is looking for new and experienced core developers with theme experience to help lead and contribute to specific features.

Similar to feature projects, the initial development of the theme will be on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. Once it’s usable and stable, the theme will be merged into core and the GitHub repo will be deprecated. After it’s merged, all issues should be reported to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

Twenty Seventeen will also use plain CSSCSS Cascading Style Sheets. — it won’t use preprocessors in the development of the theme. This will keep it simple, making the theme easier for everyone to understand, quicker for anyone to modify and better to maintain in the long run.

Throughout the process of building Twenty Seventeen, the team will be collaborating with the Theme Review Team and the core development team to make sure it is up to core standards.

How can you get involved?

There will be weekly meetings every Friday at 18:00 UTC in #core-themes starting today. During that time, the focus will be on the theme itself. If you are interested in contributing, keep an eye out here for updates or join us in #core-themes in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If you have some early thoughts on what would make this a great WordPress experience, or if you’re generally interested in participating, sound off in the comments. Please hold any design feedback for Friday’s meeting. where we can have a conversation about it in greater depth.

Want to know more about default themes?

Here are some links where you can find out more about past default themes:

#4-7, #bundled-theme, #twenty-seventeen

The story so far with Twenty Sixteen.

Things have been moving along fast with Twenty Sixteen. There have have been two, short, half-hour meetings so far, where we scrub through the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues. Everyone is welcome and they are held at 16:00 UTC on Monday and Friday.

Currently there are 10 issues and 7 pull requests in GitHub.

The deadline to get Twenty Sixteen ready to go into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is the 30th September, as per the release schedule. That isn’t too far away. Now is a crucial time to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure everyone puts this theme through its paces. You can get it right here. Testing is important to make sure all the bugs and issues are fixed before merge. Everyone is invited to help with this.

There are other ways you can get involved by helping with the existing issues on GitHub. For example, these ones all need a pull request.

Twenty Sixteen is a great opportunity for people to contribute. So far, there have been a lot of new contributors and it would be great to have more. Help make Twenty Sixteen the best default theme it can be and get involved!

#bundled-theme, #twenty-sixteen

Twenty Sixteen in the theme directory

There is some great news today, to go along with Twenty Sixteen being released on GitHub this weekend: Twenty Sixteen is now available in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ theme directory!

Twenty Sixteen has been added to the theme directory to allow anyone to test it from their WordPress.org install. While under development in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, there will be regular syncs from GitHub to the theme directory.

You can grab it right here.

Twenty Sixteen weekly meetings will begin this September 4 2015 16:00 UTC.

#4-4, #bundled-theme, #twenty-sixteen

Twenty Sixteen is now on Github!

To try things a bit differently this year, Twenty Sixteen is going to be developed on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, just like a featured 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, before it makes its way to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. and TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. You can find it right here.

Want to get involved? It’s as easy as creating an issue or PR on Github. There is a handy guide on how to contribute.

Weekly meetings will be on Fridays and Mondays at 16:00 UTC in #core-themes. These will start on Friday 4th September.

Everyone is invited to come and join in bringing Twenty Sixteen to life. Default themes are a great opportunity to get involved in contributing to WordPress!

#4-4, #bundled-theme, #twenty-sixteen