• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Feast Design Co.

WordPress Themes for Food & Lifestyle Bloggers

  • Themes
  • Feast Plugin
  • Blog
  • Support
  • Tutorials
  • Nav Social Menu

    • Email
    • Facebook
    • Instagram
    • Twitter
menu icon
go to homepage
  • Feast Plugin
  • Support
  • Tutorials
  • Account
    • Facebook
    • Instagram
    • Twitter
  • search icon
    Homepage link
    • Feast Plugin
    • Support
    • Tutorials
    • Account
    • Facebook
    • Instagram
    • Twitter
  • ×

    Home » News & Updates

    Why you shouldn't make customizations

    Published: Feb 7, 2021 · Modified: Feb 23, 2021 by Skylar · Leave a Comment

    We frequently get asked about how to make certain customizations, and we recommend against it.

    Jump to:
    • Price
    • Maintenance
    • Complexity
    • Justification
    • Project scoping
    • Implementation
    • Conclusion

    Price

    We don't build customization support into our themes: https://feastdesignco.com/themes-vs-customizations/

    Who is paying for this change? Any change, no matter how small, requires someone's time. People often request changes without factoring the cost this is putting on someone else.

    If this change cost you $100, instead of the person you're asking for support from, would you still fix it?

    We don't build customization support into our prices, and therefore can't offer free customization services.

    Maintenance

    As a general rule, every customization you make takes the equivalent time EACH year to maintain it.

    • 3 hours of customizations = 3 hours per year of maintenance
    • 30 hours of customizations = 30 hours per year of maintenance

    The reason this happens is because WordPress, SEO, pagespeed and accessibility best practices and standards change constantly. Anything you do this year will be not a best practice in 1-2 years, and become an active problem in 3-4 years.

    There's simply no way to predict what direction these things are heading and no way to fully "future proof".

    Complexity

    Every feature we've designed and optimized over the years has had feedback from experts, and is designed to comply as best as possible with:

    • search engine optimization
    • pagespeed
    • cumulative layout shift
    • accessibility

    The cost to hire an expert that's on top of all these issues to guide you through your charges is a minimum $5000 project. The amount of back-and-forth emails and hand holding and negotiating seemingly insignificant details is such a burden that every small tweak becomes a massive project management burden.

    Justification

    Always ask yourself: why am I making this change?

    Project scoping

    Project scoping is accurately defining the work that you expect to be done. Poor definitions leads to poor estimates and projects outcomes that don't match

    Poor: "My heading looks weird"

    Good: "I think the current 26px font size for my custom font for h3s on post pages is too small on mobile and needs to be bumped to 34px in order to be legible, but I'm concerned about CLS issues being caused by this"

    You need to be specific and explicit with what you're looking to have done:

    • quantify the change (eg. change spacing to 25px instead of the current 15px)
      • this avoids "oh it's bigger/smaller than I thought"
    • identify the key pages (homepage, category pages, posts, an individual post)
      • this avoids "I didn't meant for it to apply over there"
    • identify the device (desktop, mobile, tablet, any combination) - often, each device requires an equal amount of work so developing for desktop + mobile + tablet can be 3x the work
      • you should primarily be developing for mobile, but most people only look at the desktop layout
    • use the proper terminology - a header and a heading are two very different things

    Implementation

    How the customization is being implemented has massive ramifications on the amount of effort required to maintain and update the site down the road.

    See: https://feastdesignco.com/types-of-customizations/

    This is so significant that we're seeing people with $5,000 - $10,000 custom themes from just 3 years ago simply walk from them and start from scratch.

    We also see people on theme versions from 4 years who are afraid to update (or have never updated) because they're afraid of losing a customization, and often these customizations were outdated 2+ years ago.

    Conclusion

    The themes were designed and optimized in a certain way for very specific reason. Making customizations to this without deep expertise will result in problems for SEO, pagespeed, accessibility and maintenance in 90% of cases.

    These customizations then require tons of work to maintain over the years, often fall far behind best practices, and cause a lot of anxiety when it comes to updating a site down the road.

    That's not to say that you can't and shouldn't customize a theme, but we recommend hiring an expert to perform these for you, and the cost of this is almost always $5000 minimum. If you can't justify this expense, then wait until your site is earning enough to pay for it.

    More

    • GA4
    • Modern 404
    • Focus
    • Process Shots

    Reader Interactions

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Primary Sidebar

    Themes

    • Feast Plugin grants access to all 5 themes
    • Not sure where to start? See the getting started guide

    Feast Plugin

    • Feast Plugin
    • Modern Homepage
    • Modern Sidebar
    • Modern Footer
    • Modern Mobile Menu
    • Modern Menu
    • Modern Recipe Index
    • Modern Categories
    • Modern 404
    • Recipe Update Checklist
    • Recipe Post Template

    Resources

    • Image optimization
    • Recipe Guidelines for Foodie Bloggers
    • How to write a recipe post
    • Page headings
    • SEO for Food Bloggers
    • Tutorials
    • Pagespeed Audit
    • Comments
    • Internal links

    more resources →

    Categories

    • Modern Recipe Index
    • Modern Categories
    • Posts per Page
    • How to use categories
    • Category pages need content
    • How to configure the category pages
    • Food blog site structure
    • Food blog page structure

    Classic themes

    The classic themes are only for hobby sites and any food blog interested in monetizing or SEO needs the Feast Plugin.

    • Foodie Pro Classic
    • Brunch Pro Classic
    • Cook'd Pro Classic
    • Cravings Pro Classic
    • Seasoned Pro Classic

    Footer

    ↑ back to top

    Topics

    • Food Blog Design and Appearance
    • Productivity
    • Tech and Plugins
    • Food Blogging and Promotion
    • Minimalist WordPress Themes
    • Simple WordPress Themes
    • Travel blogs
    • Knitting + DIY blogs

    Help

    • Documentation & Tutorials
    • Food Blogging Resources
    • Open A Support Ticket
    • Login
    • Your Account
    • Subscriptions
    • Downloads
    • Discounts and Coupons
    • Compatibility

    Company

    • Subscribe to newsletter
    • Privacy Policy
    • Refund policy
    • Terms & Conditions
    • Principles and Best Practices
    • Affiliates
    • Contact

    Copyright © 2023 · Feast Design Co.

    Results not typical or guaranteed. Our themes and plugins are just a small part of the overall effort involved in running a food blog. Nothing on this website shall constitute legal or financial advice, always consult a local lawyer and accountant. Accessing this website and all transactions herein are under the laws and jurisdiction of Toronto, Ontario, Canada.