Follow this image : https://cl.ly/0N0i3k0r0d2j

I wasn't sure what to make of the "Customify Panel" panel in the customizer and its single section and controls. It's not clear what this is for.

As discussed.

• It's just a note for you to remember. When you are submitting this theme in WordPress.org
• Remove development version files like .gitignore, grunt or gulp files on final production version of theme.

• The blog/archive pagination: https://cl.ly/1N1d0F30193b

• HTML align: https://cl.ly/0Y2q223V133S

• Footer background size attributes: https://cl.ly/4045472Q1v0c

• Layout => Global => site content layout: https://cl.ly/1t1c2K3e3J3Y

• Add site title & tagline color

• Header align: https://cl.ly/3a0V1l2G1r09 Both are Full Width - Contained, check in case Contained too.

• Blog Sidebar layout: https://cl.ly/200200283G0y

Also related with #16.

On line 56 of inc/template-tags.php, there's no content to translate here:

printf( '<div class="tags-links">' . __( '%1$s', 'customify' ) . '</div>', $tags_list ); // WPCS: XSS OK.

That should simply be:

printf( '<div class="tags-links">%1$s</div>', $tags_list ); // WPCS: XSS OK.

• I just assign custom menu in "Secondary" menu location. But it's not showing. So, please check it's output.

It will close all Customizer : https://cl.ly/0s150W0Q3L2V

Also this should be close when press ESC?

Throughout the theme, you've mixed PHP classes inside files with other classes and functions. It's standard practice to separate files like so:

• Each class gets its own file. One class per file only.
• Functions go within their own files. Multiple functions per file.
• Logic code that executes upon file load shouldn't be mixed with functions or class definitions.

For example, in inc/customizer/customizer.php, you have all three of these ideas mixed together in a single file.

• Multiple classes.
• Multiple functions.
• Loading files via require_once() upon file load.

In the long run, this is a maintenance nightmare.

• Header Top, Main, Bottom Layout improve: Contained; Fullwidth Contained.
• Header Top, Main, Bottom Height on all devices.
• Change Background to Styling: Background Color, Background Image, Border (Border-width, Border color, Border style)

• Video is not responsive. Check out screenshot
  
  

https://cl.ly/0907013G251C

• inc\template-tags.php line 127 get_comment_time( 'c' )

You're missing the licensing and/or copyright for the following resources:

• Font Awesome CSS (note this has a different license than the font)

• Spelling mistake on comtomify_metabox_init() in customify\inc\metabox.php line 6
• Some inconsistencies with function prefixes. Some have Customify_ and some customify_, customify_ being the proper one for function prefix according to WordPress coding standards. Change Customify_ to customify_ in following:
  • inc\posts\post-builder.php post-builder.php line: 300
  • inc\customizer-layout-builder\init.php line 452 and 1005

In your Customify_Customizer_Control class in inc/customizer/customizer-control.php, your class handles multiple types of fields. Ideally, those would be in separate classes of their own. Each class should handle its own code. If there's shared code between the classes, create a parent class and sub-class it.

• Demo content shouldn't be shown to everyone. Make sure to use the right capability [current_user_can](https://developer.wordpress.org/reference/functions/current_user_can/)() to ensure that only the right people will see those messages.
• You need to make modification in file /inc/customizer-layout-builder/config/footer/widgets.php, function customify_builder_footer_widget_item()
• Check in other sections as well.
• read more at https://make.wordpress.org/themes/2016/03/31/what-is-demo-content/

• Button
• Icon List
• Nav Icon
  ..

Button style group

• Button Styling: Text Color, Background Color, Border xx
• Button Styling on Hover: Text Color, Background Color, border xx

In template-parts/content.php and template-parts/content-page.php, you have this bit of code:

the_content( sprintf(
	wp_kses(
		/* translators: %s: Name of current post. Only visible to screen readers */
		__( 'Continue reading<span class="screen-reader-text"> "%s"</span>', 'customify' ),
		array(
			'span' => array(
			'class' => array(),
			),
		)
	),
	get_the_title()
) );

The <span> mixed into the text string is entirely unnecessary and is causing you to add a lot of unneeded code. It'd be far easier to use:

the_content(
        // Translators: %s: Name of current post. Only visible to screen readers.
        sprintf( esc_html__( 'Continue reading %s', 'customify' ), '<span class="screen-reader-text">' . the_title( '', '', false ) . '</span>' )
);

Also, note that I'm using the_title() rather than get_the_title() there so that all the right filters are applied.

• Make sure excerpt_length and excerpt_more hooks are not executed on admin side
  • customify/inc/posts/post-builder.php line 79 as :

    if ( ! is_admin() ) {
        $excerpt_length = apply_filters('excerpt_length', 55 );
    }

* Similar in line 81

WordPress.org will ask that you remove any unused code. For example, there are 100s of lines of code in inc/customizer/customizer-config.php that are commented out. Those should be removed from your final copy.

In /languages, you have a _beacon.pot file. Make sure that's updated and renamed to customify.pot.

Also, for WordPress.org, you are not required to have a POT file. It can be omitted and the WordPress.org language pack system will handle it.

• in functions.php file, you have defined content_width as 640 in function content_width(). But when I check in with of your content in site, your default content width is 841
• Then again you need to change the width as per your Content Layout.

JS variables in the global namespace should be prefixed just like PHP names.

In assets/js/customizer/auto-css.js, the AutoCSS variable should be prefixed.

• It's not so flexible to. I just added Widget in Footer Widget 1 and Footer Widget 2. But it's showing demo Footer Widget 1 and Footer Widget 2. It's not the good experience.
  
• Then I check in settings to remove Footer Widget 3 and Footer Widget 4. Finally I was able to remove it. But then, there is spacing issue. Check out this screenshot
  

I always recommend this. You should take the time to follow the WP PHP documentation standards: https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/php/

With any theme, especially a larger one like this with lots of PHP code, this will help maintain it in the future. It also helps those looking at your code understand it. This also helps us help you.

For example, I could pull a random method out like Customify_Customizer::get_config(). The code itself looks fine just looking over it. However, because there's no documentation on exactly what the method is supposed to do, I can't say that the code is 100% correct.

• inc\customizer-layout-builder\config\footer\copyright.php line 79 Customify_Init::$theme_url

• I just added more tags in post and then check out archive page. But the more tag has been ignored and it's showing normal excerpt.
• Check this screenshots
  
  

• Theme URI and Author URI should not be the same
• Theme URI is optional. If used, it must be about the theme on WordPress.org
  Author URI is optional. If used it is required to link to an author’s personal website or project/development website.

In your style.css header, you should add this line after Text Domain:

Domain Path: /languages

Details in this image: https://cl.ly/3j322f3P2n2Z

1. Remove HTML 2 builder item in free version.
2. Add "Secondary Menu" builder item

• inc\template-tags.php line 129 get_comment_date()
• inc\customizer-layout-builder\config\footer\copyright.php line 79 Customify_Init::$theme_author

Move reset icon right after Unit square box.

• Keep popup settings when click reset.
• Group background settings.
• Group box-shadow settings.

• front-page-posting is an invalid theme tag in styles.css Tags
• Further, readme.md and styles.css has different tags

• In mobile devices from media query 370px and below, table flows outside the content area.
  

When registering multiple sidebars with the same name (but numbered), such as with your footer sidebars, you should use the register_sidebars() function instead of registering them individually with register_sidebar().

For example, this will register 4 footer sidebars with the footer-1, footer-2, and so on IDs:

register_sidebars(
        4,
        array(
                'name'          => esc_html__( 'Footer Sidebar %d', 'customify' ),
                'id'            => 'footer',
                'description'       => esc_html__( 'Add widgets here.', 'customify' ),
                'before_widget' => '<section id="%1$s" class="widget %2$s">',
                'after_widget'  => '</section>',
                'before_title'  => '<h4 class="widget-title">',
                'after_title'   => '</h4>'
        )
);

A secondary benefit of that is that you have fewer text strings to translate.

Add Read only option

Able to set fixed, uneditable value for CSS Ruler : https://cl.ly/3H1P0z0x4343

• Missing style for Post Pagination. It's just in default stage. Check this screenshot
  

Throughout the theme, you have many function_exists() and class_exists() checks, which in effect make much of your code pluggable. This means it can be overwritten in a child theme.

While that may be desirable for something like template functions, I can't see the use of doing that for something like your Customify_Customizer class for example. I wouldn't be good practice to allow the entire class to be overwritten like that.

I recommend reviewing any pluggable functions/classes and making sure that there's a good use case for them being pluggable. If not, remove the conditional check.

For the most part, this looks like a solid theme in terms of code. But, it's not poetic code (referring to WordPress' motto of "code is poetry"). This is really the only thing I'd spend a lot of time trying to improve -- writing more maintainable code. It's not something you need to address today. It's something you'll work on over time.

Good inline docs is a start to making better code: #55

When I'm looking over theme code, a red flag for me is often seeing a file that's over 15 kb in size. More often than not, this means the file needs to be broken down into separate files for better organization. I touched on this in #53, but I'm creating this larger ticket because this is more about the entire theme code than just classes.

Practical example of separating files

I'm going to give you a practical example of how I'd break down one of your large files. Let's use inc/customizer/customizer.php.

First, I'd put the 3 classes into their own files. Something like:

• class-customify-wp-customize-panel.php
• class-customify-wp-customize-section.php
• class-customify-customizer.php.

Ideally, you'd use an autoloader to automatically load those (and any other classes) as needed.

Then, I'd separate all the functions into a file like:

• functions-customizer.php

Then, all the require_once() file loading calls, I'd separate out into its own file or section of another file for just loading stuff. This should be a part of a bootstrap routine for the customizer somewhere.

The direct call to the Customify_Customizer() function should be a part of your customizer bootstrap routine too.

If you're interested in a really rough bootstrap method, feel free to check out one I'm currently building. It's unfinished at the moment (need to move the app() function to a separate file too) and not specific to the customizer, but it may give you some ideas: https://github.com/justintadlock/abc/blob/master/bootstrap/app.php

Arrays upon arrays

A lot of your customizer code is arrays on top of more arrays. It can't be easy to find stuff.

When I find myself in similar situations, I usually break a lot of the code out into its own function.

• Title should not overflow the content area

• Non-breaking text in the title, content, and comments should have no adverse effects on layout or functionality.

• Check this screenshot, where title and content is overflow and also featured image is hidden now.
  

• The following CSS properties will help you support non-breaking text.

-ms-word-wrap: break-word;
word-wrap: break-word;

Currently logo height doesn't apply for Logo Retina