Template parts in Wordpress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a template part in WordPress?

A template part is a reusable piece of code that you can include in multiple theme files to keep your design consistent and your code organized.

beginner

How do you include a template part in a WordPress theme?

You use the function get_template_part('slug') where 'slug' is the name of the template part file without the .php extension.

beginner

Why use template parts instead of copying code in multiple theme files?

Using template parts helps avoid repeating code, makes updates easier, and keeps your theme organized like using building blocks in a house.

intermediate

What file naming convention is recommended for template parts?

Template part files are usually named with a prefix like content- followed by a descriptive name, for example content-header.php.

intermediate

Can template parts accept parameters or variables?

By default, get_template_part() does not accept variables, but you can use global variables or other methods to pass data to template parts.

Which function is used to include a template part in WordPress?

A get_template_part()

B include_template()

C load_template_part()

D require_template()

The correct function to include template parts is get_template_part().

What file extension do WordPress template parts usually have?

A .html

B .php

C .js

D .css

Template parts are PHP files, so they have the .php extension.

If you want to include a template part named 'footer', what is the correct code?

A load_template_part('footer')

B include('footer.php')

C require('footer')

D get_template_part('footer')

Use get_template_part('footer') to include the footer template part.

Why is using template parts beneficial?

A It makes the theme slower

B It increases file size unnecessarily

C It helps reuse code and keep the theme organized

D It prevents theme customization

Template parts help reuse code and keep the theme organized.

Can you pass variables directly to template parts using get_template_part()?

A No, get_template_part() does not accept variables directly

B Yes, by passing them as arguments

C Yes, by using a second parameter

D No, template parts cannot use variables at all

get_template_part() does not accept variables directly; you need other methods to pass data.

Explain what template parts are in WordPress and why they are useful.

Think about how you can reuse parts of a webpage like header or footer in many places.

Describe how to include a template part in a WordPress theme and mention any naming conventions.

Remember the function name and how you name the files.

Practice

1. What is the main purpose of using get_template_part() in WordPress themes?

easy

A. To create database tables

B. To register new custom post types

C. To include reusable template parts and keep code organized

D. To enqueue styles and scripts

Solution

1. Step 1: Understand the function role

   get_template_part() is designed to include reusable parts of a theme, like headers or footers.

2. Step 2: Compare with other options

   Registering post types, enqueuing scripts, and creating tables are unrelated to template parts.

3. Final Answer:

   To include reusable template parts and keep code organized -> Option C

4. Quick Check:

   Template parts = reusable code pieces [OK]

Hint: Remember: template parts reuse code pieces [OK]

Common Mistakes:

• Confusing template parts with post type registration
• Thinking it manages scripts or styles
• Assuming it handles database operations

2. Which of the following is the correct syntax to include a template part named 'content' with a specific variation 'single'?

easy

A. get_template_part('content', 'single');

B. get_template_part('single', 'content');

C. get_template_part('content-single');

D. get_template_part('content', single);

Solution

1. Step 1: Recall function parameters

   get_template_part() takes two string arguments: slug and optional name.

2. Step 2: Match correct order and syntax

   The correct call is get_template_part('content', 'single'); with both parameters as strings.

3. Final Answer:

   get_template_part('content', 'single'); -> Option A

4. Quick Check:

   Slug then name as strings [OK]

Hint: Use two strings: slug first, then name [OK]

Common Mistakes:

• Passing combined slug and name as one string
• Swapping slug and name order
• Forgetting quotes around name

3. Given the code snippet:

get_template_part('header');

What file will WordPress try to load first?

medium

A. header.php

B. header-header.php

C. header-single.php

D. header-template.php

Solution

1. Step 1: Understand default file naming

   When only slug is given, WordPress looks for {slug}.php file.

2. Step 2: Apply to example

   Slug is 'header', so WordPress loads header.php.

3. Final Answer:

   header.php -> Option A

4. Quick Check:

   Slug only loads slug.php [OK]

Hint: Slug alone loads slug.php file [OK]

Common Mistakes:

• Expecting a suffix like '-header' automatically
• Confusing with named template parts
• Assuming different file extensions

4. What is wrong with this code snippet?

get_template_part('footer', single);

medium

A. No issues, code works fine

B. Wrong function name, should be get_template_parts

C. Footer template parts cannot have a name

D. Missing quotes around 'single' causing a syntax error

Solution

1. Step 1: Check parameter types

   Both slug and name must be strings, so 'single' needs quotes.

2. Step 2: Identify error cause

   Without quotes, single is treated as a constant or variable, causing syntax error.

3. Final Answer:

   Missing quotes around 'single' causing a syntax error -> Option D

4. Quick Check:

   Strings need quotes [OK]

Hint: Always quote slug and name strings [OK]

Common Mistakes:

• Omitting quotes around name parameter
• Using wrong function name
• Thinking named parts are not allowed

5. You want to create a reusable sidebar template part with two variations: 'left' and 'right'. Which folder structure and code usage is correct to achieve this?

hard

A. Files: sidebar-left.php, sidebar-right.php inside /parts/ folder; Code: get_template_part('sidebar', 'left');

B. Files: sidebar-left.php, sidebar-right.php in theme root; Code: get_template_part('sidebar', 'left');

C. Files: sidebar.php only; Code: get_template_part('sidebar-left');

D. Files: sidebar-left.php, sidebar-right.php in theme root; Code: get_template_part('sidebar-left');

Solution

1. Step 1: Understand file naming for variations

   Named template parts use {slug}-{name}.php in theme root.

2. Step 2: Match code to file structure

   Calling get_template_part('sidebar', 'left'); loads sidebar-left.php.

3. Step 3: Evaluate other options

   B places files in subfolder without adjusting slug to include path; C uses only one file; D uses combined slug-name as one string incorrectly.

4. Final Answer:

   Files: sidebar-left.php, sidebar-right.php in theme root; Code: get_template_part('sidebar', 'left'); -> Option B

5. Quick Check:

   Slug-name files in root with two-string call [OK]

Hint: Use slug-name.php files in root, call with two strings [OK]

Common Mistakes:

• Placing files in subfolders without adjusting code
• Passing combined slug-name as one string
• Using only one file for multiple variations