Visit the Website

Tech Specs:

This website uses a relatively small set of plugins that control the core functionality, and then were heavily extended via custom coding through hooks & filters.

Heavily customized WooCommerce experience, with multi-level mapping between products and custom post types
Hosting music purchases & downloads, with the option to preview music before purchase.
ACF (Advanced Custom Fields) Integration for document attachments & external links
Manipulation of Taxonomies / Custom Fields to create a Album vs. Single Song relationship
WP Bakery integration for all frontend templates. (I also have moderate experience with both Elementor and Divi)

Premise:

Christian Music Singer & Song Writer, Carrie Wrigley, wanted a redesign of her old website, which was built on Joomla. She wanted the ability to sell music and lyric sheets, as well as give the user an option to download their purchases. However, she wanted to take it quite a few steps beyond simply straight out-of-the-box WooCommerce. She had a very specific flow from Homepage to Checkout that she wanted tailored. Carrie wanted to make sure that it was built in a way that she could easily manage it herself, so everything needed to be as dynamic “automatically pull in” as possible. All of the mapping needed to be able to handle keeping about 6 different product types & custom post types & taxonomies tied together in a way that would also accommodate her concisely managing the site. All of the following is connected that way:

  • Full Album CD
    • Songs categorized by topic
    • Individual Songs
      • Music / Lyric Sheet PDFs (separate products)
      • Music Preview
      • A music video on YouTube (if available)

And everything needed to be tied together in a way that would make as much information from all 6 of those points be available at any given time. For example & clarity:

  1. If the user’s viewing a full CD Album, then they need to be able to:
    1. Purchase that entire album as a single product.
    2. View the songs that are contained in that album
    3. Have links to view either the single song product or the single lyric product of that individual song
    4. Preview that specific song.
  2. Then if the user chooses to visit an individual song, then they need to be able to:
    1. View and purchase the mp3 version of the song
    2. Pull in the single product music sheet PDF version of that song, if one is available, and list it for purchase with the mp3 version
    3. Show a youtube music video link if one is available
    4. Have links to online version of the lyrics for that song (link to custom post type)
    5. Reference which CD Album it’s a part of.
    6. Provide external links (e.g. spotify / Apple)

Things like that. Where all of this is actually being pulled into a template, and populated from many different places per product, so that all Carrie needs to do is update data in as few places as possible in the dashboard, while still retaining the product flow on the frontend.