Skip to content

Development Workflow

Gannt of our Development workflow Timeline

Project Workflow

1. Planning

  • [ ] Determine Features
  • [ ] Determine Blocks Needed
  • [ ] Determine Usage
  • [ ] Update Github Issues for Branching Later

2. Basic Setup and Configuration

3. Global Elements and Style Guide

4. Page Layouts

  • [ ] Base Layout For All Pages
  • [ ] Custom Layouts For Content Pages

5. Custom Blocks

6. Custom Features

  • [ ] Custom Post Types
  • [ ] Custom Functionality

7. Developer Testing and Review

  • [ ] Code Cleanup
  • [ ] Code Review
  • [ ] Bug Fixes
  • [ ] Accessibility Testing
  • [ ] Performance Testing
  • [ ] Browser Testing
  • [ ] Responsive Testing
  • [ ] SEO Testing
  • [ ] Final Review
  • [ ] Final Bug Fixes
  • [ ] Documentation Updates

10. Marketing Testing and Review

11. Revisions and Updates

12. Launch

Basic Setup and Configuration Checklist

  • [ ] Confirm that Users and Plugins were imported properly when setting up the site via RunCloud.
  • [ ] Plugins
    • Check if any of the following plugins are necessary for the build and import the proper settings and license keys where necessary (delete from this checklist any plugins that are not needed for the specific build):
      • [ ] Advanced Custom Fields (License key for updates)
      • [ ] Calendarista
      • [ ] FluentSMTP (API key and set from email as info@lpdsendmail.com, send a test email to confirm it works.)
      • [ ] GiveWP
      • [ ] Gravity Forms (Lisence key)
      • [ ] Perfmatters (License key and upload settings json file)
      • [ ] The Events Calendar
      • [ ] WP Review Slider Pro
      • [ ] WP Sheet Editor (License key)
      • [ ] Any other needed plugins specific to the site
  • [ ] Pages / Menus
    • Register any additional needed menu locations in the code.
    • Use Project Workbook or Visual Sitemap Document for guidance.
    • Make sure external links are not set up as pages on the site and are directed as external links to the right website with target="_blank" properly.
  • [ ] Favicon and Block Icon
  • [ ] List out elements needed in Site Settings for the site and set up Site Settings/fill out the needed fields so that the elements and information are available once we start coding the site and building twig templates.

Global CSS and Global Elements Checklist

Normal Global Styles Considerations

  • [ ] Fonts
  • [ ] Typography
    • [ ] Prose
      • [ ] Heading Levels and paragraphs
      • [ ] Anchors
      • [ ] List items
      • Etc.
    • [ ] Theme.json Typography Options (Sizes and Heading Level Styles)
    • [ ] Custom Utility CSS Classes
  • [ ] Colors and Gradients
  • [ ] Global Padding
  • [ ] Content Widths
  • [ ] Button Styles
  • [ ] Password Protected Pages (Input should match default form input style and submit should match default button style)
  • [ ] All gravity form elements.
    • Upload God Form (or God Form with Stripe Fields if needed) from development folder to ensure all fields match the theme style.
  • [ ] Default Focus Ring Color
  • [ ] Default Highlighted (::selection) Text Color
  • [ ] Start the Style Guide with all Typography, Colors, and Gradients

Style Considerations Specific to Build

  • [ ] On the Github subissue, list any considerations that are specific to this particular site.