Theme Developer Handbook @ Contribute Day

oK; let’s take some bits of the handbook – each bit should be reviewed for usefulness and accuracy. Keep in mind that we’re aiming for a resource that people can use to check as they develop a theme.

Here’s the list of topics – each should get a pass from a volunteer and then pass it to Se for a style review. Tick off the topic when you take it and add any notes by editing the post. When Se says “it’s done,” she’ll add another note and we’ll then consider it to be checked in. 🙂

Introduction

Part One: Theme Basics

  • Including CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. stylesheets and scripts (@iandstewart)
  • Template Tags (@clauzon)
  • The LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. (@iandstewart)
  • Theme Files and Organization (@digisavvy)
  • Page Templates (@enricchi)
  • Template Hierarchy (@ozzyr)
  • Theme Functions (@iandstewart)

Part Two: Theme Functionality

  • 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) (@ozzyr)
  • Comments (@davidjlaietta)
  • Media
  • Navigation Menus (@jboydston)
  • Pagination (@thepixelista)
  • Post Thumbnails (@Brainfestation)
  • Sidebars (@thepixelista)
  • Translation (@Brainfestation)
  • widgets https://codex.wordpress.org/Widgetizing_Themes (@ancawonka)
  • Next and Previous Links https://codex.wordpress.org/Next_and_Previous_Links
  • Linking Theme Files and Directories https://codex.wordpress.org/Determining_Plugin_and_Content_Directories
  • Custom Headers https://codex.wordpress.org/Custom_Headers
  • Adding Admin Menus https://codex.wordpress.org/Adding_Administration_Menus

Part Three: Advanced Theme Topics

  • Child Themes
  • Theme Customizer [This still needs to be properly incorporated: https://codex.wordpress.org/Theme_Customization_API ]
  • Theme Security
  • UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. Best Practices
  • Theme Unit Tests https://codex.wordpress.org/Theme_Unit_Test
  • Validating Your Website https://codex.wordpress.org/Validating_a_Website)

Part Four: Theme Release

  • Required Template Files
  • Submission Process
  • Testing
  • Theme Review Guidelines
  • Writing Documentation (@sewmyheadon) ref: https://codex.wordpress.org/Theme_Review#Theme_Documentation

#contribute-day-2013, #handbooks

WordCamp San Francisco Contributor Day

Hi everyone!

Handbook Style and Formatting Guide

Welcome to the WCSF 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/.. Here are some things that need to be worked on:

  • Video transcriptions need to be worked on @drewapicture
  • design for the new support portal and developer resources
  • @ipstenu will be leading the support side of things for people who want to do support tickets

If you have access to IRC, please log in to irc.freenode.net #wordpress-sfd

We’re also open to other things that people want to work on and write. For example, we could write some user docs on make/docs for the new support portal.

#contribute-day-2013