What's best practice for theme/plugin settings API for new dev? (5 posts)

  1. sem101
    Posted 2 years ago #

    Hi, I'm new to theme & plugin dev, go easy on me :)

    There are 3 specific areas I'm trying to wrap my head around and understand what WP is trying to do with future releases, and how should I begin coding to these standards.

    (I will soon start following the blog, irc, news, trac, etc. thanks.)

    Theme settings/options:

    A) Theme Customization API (Customize)
    B) Settings API (Settings)
    C) Plugin API (Appearance)

    See why I'm confused? There are 3 areas I can implement settings/options. My first stab was to go after Customize. So I began coding and put ALL of my settings/options in there. Looks/works great! However, when I started to dev a few plugins, I had a look at B & C above and realized that these are great places to put ALL my settings as well.

    So I have a ton of completed settings in Customize, but do you think I should put my settings in Settings or Appearance?

    At first thought, I was thinking Customize would be solely for Front-End styling: Background Image, Logo, Fonts?

    Then use Settings API for things like: if checked() locate_template(ACTIVATE_CUSTOM_PLUGIN)?

    What do you guys think and what does WP want me to do for future standards?

    Thanks WP peeps!

  2. esmi
    Forum Moderator
    Posted 2 years ago #

  3. sem101
    Posted 2 years ago #

    Thanks. I've read that great post :) I should've included in my post that I've read a TON of these articles. But where I'm struggling is I have 3 areas to implement any/all settings.

    I'm trying to find best practice moving forward, where do I put these settings? I have A, B, C above ALL working and ready to go. But from a UX standpoint, I feel having split settings in 3 areas is not good practice.

    Further thoughts?

    Thanks again!

  4. esmi
    Forum Moderator
    Posted 2 years ago #

    I'd suggest using the Settings API. The Theme API is not meant for plugins and is nowhere near as well developed as the Settings API.

  5. sem101
    Posted 2 years ago #


Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.