Technical Specifications

These tech standards are the basis for all websites we build. These are the principles you can expect to come across when we take on your project.

Teach Me
Smooth Sailing

Your time and peace of mind are at the core of what we do. We will ensure that you’re at ease by creating a stress—and risk free—process.

E-commerce Delight

Quality means distilling all of your unique selling points into one coherent visual message.

Easy User Experience

Don’t turn visitors away. Designers work with your content so that it’s clear and directs people to what you want them to do.

 ” I have helped many entrepreneurs, pro athletes and executives build
outstanding websites. They go on to contribute greatly to their industry and their community. This is my greatest thrill. For if I can continue this achievement with satisfying you, I’ll cherish our partnership always. “

Joe Momoh President & CEO

Learn More

Basic principles

We Will:

  • initially build the site on Codessa dev server
  • use the most currently available version of WordPress at time project is started
  • create CSS files that are well-commented, clearly broken into sections and organized in a logical order following the page display order (body, header, navigation, content, row, sidebar, footer, etc.)
  • set all external links to target=”_blank”
  • disable comments unless otherwise specified
  • discourage search engines from indexing the site on our staging server
  • use the fonts that are in the PSD files we receive from designers
Will Not:

  • create a child theme for Foundation or Bootstrap sites as each site build is a custom theme built off a framework and is not impacted by parent theme updates like other commercially available themes (standard WP core updates and plug-in updates can still be run as normal)
  • style comments form or comments thread views unless directed by client
  • allow Google to crawl WordPress sites on our development server
  • write/modify plug-in source code (functionality) unless specifically discussed and agreed to
  • make significant changes to the functionality of a premium theme (see premium themes section below)
  • won’t perform SEO optimization of the website unless specifically requested in the original specifications during the quoting stage

Header & Footer

We Will:

  • use Dashboard » Appearance » Header so header logo file can be added as an image
  • link logo to home page
  • use Dashboard » Appearance » Background to set background color and/or background image plus scrolling.
  • use Advanced Custom Fields Pro » Options Page to create global options for header content, footer content, etc. resulting in a Dashboard menu item called “Theme Settings”
  • will set up Dashboard » Theme Settings » Contact Info as a set of custom fields where user can set site phone number, site email address, physical or mailing addresses, etc.
  • will set up Dashboard » Theme Settings » Footer » Copyright Statement and Social Media custom fields where user can add/edit the site’s copyright statement and various social media pages
  • will use built in favicon functionality released since WP 4.3 (Appearance -> Customize -> Site Identity)


We Will:

  • create all menus using Dashboard » Appearance » Menus editing tool
  • clearly identify Menu Locations using obvious naming such as “Top Nav”, “Primary Nav” and “Footer Nav”
  • build the responsive navigation using the defaults for Bootstrap or Foundation unless otherwise specified
Will Not:

  • add breadcrumbs unless specified


We Will:

  • make images in the responsive versions of the slider proportional
  • put all text that overlays the slider in the full screen view underneath the slider image in the responsive views
  • work with premium slider plugins if requested prior to development beginning

Pages & Posts

We Will:

  • manually set the Page Sort Order on each page we add to the site so that the listing of sites on Dashboard » Pages closely follows the same order as the navigation menus
  • only use one <h1> tag per page or post, unless otherwise stated in the Client’s project requirements
  • wrap the Page Title or Post Title in the lone <h1> tag, unless otherwise stated in the Client’s project requirements
  • setup any custom fields used on a Page Editor of Post Editor in a logical order using an obvious naming syntax so that non-technical users can add/edit information.
  • use Dashboard » Settings » Permalinks to set the default permalinks to /%postname%/ (requires MOD REWRITE in PHP on host)


We Will:

  • name the theme and theme’s template folder based on the project name. The name can be changed if requested
  • add site logo or first letter of the site as favicon
  • replace the default screenshot to one of the homepage
  • create a templates folder under the themes directory and create the requested template files there (example: templates/template-home.php)
  • provide CSS for template files and:
    • Single.php
    • Page.php
    • 404.php
  • use the default responsiveness provided by Bootstrap or Foundation if specific files are not provided for the responsive views

Woo Commerce (plugin)

We Will:

  • quote client for checkout, cart, and single-product pages. If templates are not provided – Codessa will use the standard WooCommerce templates for these pages
  • set the default payment gateway to PayPal and Pay with check
  • set default shippings standards of
    • Free Shipping
    • Flat Rate
    • Local Delivery
    • Local Pickup
  • Any customizations and additional functionality add-ons must be requested by the client during the quoting stage in order for Codessa to provide an accurate quote

Premium Themes

We Will:

  • work with a premium theme if requested by the client and use the theme’s default functionality to quote and build the project.
  • only provide a rough estimate for any additional functionality (not provided by themes default settings) and charge the standard hourly rate for all hours spent. Estimate accuracy will be based on completeness of functionality descriptions by the client during the quoting stage
Will Not:

  • make significant changes to the existing functionality of a premium theme (see above) without full understanding and acceptance from the Client of the future risks that come with making such changes (i.e. updates released from Premium theme breaking components of site upon update)
Recent Projects

View Work

Already In Love

Request Quote