{"id":1558,"date":"2016-06-15T00:08:27","date_gmt":"2016-06-14T19:08:27","guid":{"rendered":"https:\/\/ahmadawais.com\/?p=1558"},"modified":"2018-01-20T05:53:22","modified_gmt":"2018-01-20T00:53:22","slug":"wordpress-customizer-package-sublime-text","status":"publish","type":"post","link":"https:\/\/ahmadawais.com\/wordpress-customizer-package-sublime-text\/","title":{"rendered":"Introducing WordPress Customizer Package For Sublime Text!"},"content":{"rendered":"

Customize component<\/a>\u00a0has an incredible PHP and JS based API in the WordPress Core. I found it to be much better than many other elements e.g. the Settings API in WordPress is a bit messy (probably why Scott Clark from 10Up is building the Fields API).<\/p>\n

Started With Frameworks#<\/a><\/h3>\n

Anywho, when I first started making Customizer based WordPress themes<\/a>, I used frameworks like Kirki and Redux Framework, and then later I ended up using Titan Framework for a WordPress plugin called\u00a0CF7Customizer<\/a>.<\/p>\n

Problem\u00a0With Frameworks#<\/a><\/h3>\n

In the case of these frameworks, it quickly became hard to deal with the updates, backward compatibility, and then code quality especially concerning security. I found myself reading more and more source code to keep up with their development. And then came a time when I\u00a0felt I should probably go as native as I can to use WordPress APIs instead of such frameworks.<\/p>\n

Going Native With WP Customizer API#<\/a><\/h3>\n

I started to figure out what kept me away from using the official WP Customizer API.\u00a0I found out that WP Customizer is not very commonly adopted because of the lack of enough documented examples. Because after going through both Codex and Dev Reference, basic concepts of WordPress customizer were mundanely clear. It was just that the information is so scattered that I always went for simple and to the point frameworks.<\/p>\n

Customizer Is Pretty Cool#<\/a><\/h3>\n

Guess what WP Customizer is pretty much what you need to deal with and it is very easy, huge props to the customize component maintainers Weston Ruter<\/a>, voldemortensen<\/a>, Nick Halsey<\/a>, Derek Herman<\/a>\u00a0and all the contributors.<\/p>\n

WPCustomize Boilerplate#<\/a><\/h3>\n

WPCustomize Boilerplate is something that I will write about in an upcoming article but here’s a bit about it.<\/p>\n

To make things better I’ve started to build a WPCustomize Boilerplate<\/a>, which will be my sandbox for customizer related experiments. Right now, I have added all the core\u00a0and advanced controls accompanied with Panels &\u00a0Sections and customizer sanitization routines<\/a> via WPTRT.<\/p>\n<\/section>\n

\n
\n

Sublime Package for WordPress Customizer<\/a>#<\/a><\/h2>\n

Sublime snippets for WordPress Customizer.<\/p>\n

\"GPL\"<\/a>\u00a0\"Package<\/a>\u00a0\"GitHub<\/a><\/p>\n<\/div>\n<\/div>\n

\n

Stupid-simple, tab-triggered sublime snippets and completions for WordPress Customizer.<\/strong><\/em><\/p><\/blockquote>\n

I’ve been a big fan of Sublime Text; I use it every day for both frontend and backend programming. Sublime Text has a great deal of potential which helps me automate my dev workflow and build small completions and snippets based libraries.<\/p>\n

What if I told you that you can build Customizer options for your next WordPress product (theme\/plugin) under 5 minutes? Yes, it is possible! I have made a Sublime Text package for WordPress Customizer that can help you write quality code in a jiffy.<\/p>\n<\/section>\n

\n