Twenty Seventeen: Agenda for Oct 21, 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.

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

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

Twenty Seventeen: Merge Proposal for 4.7

A note from @helen: Before we get into the proposal itself, I’d like to officially introduce its author, @davidakennedy, as a 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. for bundled themes. We really should have done this ages ago, but now he’ll get to make a big splash with Twenty Seventeen. Congrats, David! 🎉


twenty-seventeen

The team behind Twenty Seventeen has reached that point that we’re ready to propose Twenty Seventeen as the new default theme for WordPress in 4.7. It’s an ambitious theme that focuses on a creative home page and an easy site setup experience for users.

Like last year, with Twenty Sixteen, the development process happened on GitHub. The theme will be merged into WordPress from the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. period on, and development will move to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. Some remaining tickets will move over to Trac at that time.

Features of Twenty Seventeen

Created with the feedback on previous default themes in mind, and the desire to reach a new audience, Twenty Seventeen was designed for business websites. It offers:

  • multiple sections on the front page, selected 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..
  • a striking asymmetrical grid.
  • custom color schemes, built on top of a monochromatic foundation, and adjustable via a hue picker.
  • different headline placement for pages, changeable in the Customizer, via theme options.
  • a great experience in many languages, thanks to language-specific font stacks.
  • SVG icons (a first for a default theme).
  • support for custom logo, 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. image and many post formats.
  • the use of new functions in Core for making child theming easier.

Contributions

As usual, a default theme couldn’t happen without the community. This year, Twenty Seventeen has benefited from 57 amazing contributors so far (up from 38 at this point last year). They have helped with:

  • triaging issues.
  • providing code reviews.
  • testing and recommending language specific font stacks.
  • improving the theme’s 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).
  • browser and device testing.
  • numerous bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, code tidying and countless improvements.

Testing, Feedback and Next Steps

While contributors have tested Twenty Seventeen on various devices and browsers throughout the development process, edge cases still exist. Please test Twenty Seventeen in as many different environments as you can.

Until the merge deadline, contributors to Twenty Seventeen will work on the Core Merge milestone in GitHub, knocking out as many issues as possible.

A big thank you to everyone that has helped make Twenty Seventeen come to life.

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

Twenty Seventeen: Agenda for Oct 14, 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.
  • Flexbox.
  • 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 Meeting Notes: Oct. 7 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. The theme’s initial design implementation is merged and everyone should focus on testing.
  • discussed issue on SVGs instead of icon fonts. @melchoyce has decided on Font Awesome for SVGs, so implementation was discussed. A few fallback methods were discussed, like a simple text fall back or CSSCSS Cascading Style Sheets. image fallback, but some testing will be needed. A pull request should be worked on next week.
  • highlighted other issues that the community is encouraged to comment on and test (both have pull requests):

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

Twenty Seventeen: Agenda for Oct 7, 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.
  • There isn’t much that hasn’t been already triaged, so that will be skipped.
  • SVGs instead of icon fonts.
  • 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: Oct. 4 2016

Here’s the summary for this week. The meeting was busy, so feel free to add anything missed in the comments.

Housekeeping

Summary

The group:

  • discussed #37974 (Add multi-panel feature to pages through add_theme_support) for the majority of the meeting. The goal was to find a minimum viable productMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia that could be developed in the time left.
  • decided to shoot for this feature to be 1. limited to the front page only. 2. exist 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. 3. provide basic markup, created by CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • decided this story board stood out as the strongest to be iterated on and mocked up as a design.
  • decided live preview in the Customizer wasn’t critical at the current time.
  • @helen and I will work on marshaling people to help with the project.
  • @karmatosed will work on the initial mock-up of the feature.
  • briefly discussed #38172 (Enable video headers in custom headers) It also needs to have a minimum viable product defined and those interested were encouraged to comment on the ticketticket Created for both bug reports and feature development on the bug tracker. with that in mind.
  • brought up #19627, and that could be worked on but it’s not a priority over the other major features for Twenty Seventeen.

Next steps

  • For Add multi-panel feature to pages through add_theme_support, the mock up will be created and developers are needed to work on it.
  • For Enable video headers in custom headers, a clearer scope needs defining and more developers are needed to work on it. A basic 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. exists for this ticket. 

Call for help

Twenty Seventeen needs you. Home pages should be fun to create and a heck of a lot easier. Headers can be even more captivating. If you’re interested in working on either of these projects, please let me or @helen know.

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

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 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 make 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 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