• Analyzing the code from WordPress themes, both free and paid for, and realized that there is no standard for the development of themes. Some themes use CPT for all other widgets, other Visual Composer (and dirty code) and so on.

    I know WordPress, studying hard and already making my themes and I am honestly confused as to which way I should build my themes. What is the best or “worst” method.

    Some may say that “the best method is what solves your problem,” but I believe it is not because it solves my problem, which is the best method. Not because it is running that is good!

    My question is, is there some way “more appropriate / better / less worse” to develop a theme? CPT, Widgets, VisualComposer and so on…?

Viewing 3 replies - 1 through 3 (of 3 total)
  • realized that there is no standard for the development of themes

    Oh – but there are standards for theme development! See https://make.wordpress.org/themes/

    Thread Starter gtw7375

    (@gtw7375)

    “realized that there is no standard for the development of themes”, in the sense of different ways to mount/create site elements. Custom Post Types, Widgtes, like Visual Composer plugins.

    Generally speaking, themes should not be incorporating or relying on any plugins. That said, it’s fine to add optional enhancements for plugins but these should always be wrapped in a conditional that tests for a core function within the plugin so that the site site will not fall over if the plugin is unavailable.

    In the sense of implementing standard site elements (eg menus, widgets etc), there are no real limits on your creativity as long as you’re hooking into the relevant WP core functions.

    Reviewing https://make.wordpress.org/themes/handbook/review/required/ should give you a good idea of what’s needed/recommended.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Best practices for development wordpress themes’ is closed to new replies.