WordPress Customizer is a very powerful. Not only because we have a live preview, but also because it got a lot of build-in input type. And we can also extend it or create our own reuse-able input type.
This is not a full tutorial but only explaining the concept, but you can check the full working code here:
WP.org is not very good (read: evil) organization. They collect data without user consent, they are not transparent in what data they collecting, and they make it hard to disable this.
For example: There’s no easy way to exclude custom theme for update check. WordPress have filters for everything, but they don’t have this filterable. Maybe they want to monopolize theme market (maybe they are trying to say: you want to create theme? you need to use wp.org theme repository).
So font name is separated using + sign. and we can add multiple font weight/style using : after font name and add available font weight/style in comma , separated string,
I remove the http: part of the URL when loading it, so it will be HTTPS compatible, and using the right protocol when loading the font.
If we use more than one font, we can simply load it in separate request, for example we use Open Sans and Ubuntu Font.
fyeah is a tumblr inspired WordPress theme, and my first theme using tamatebako framework. Check the theme page for more info about theme features. I think i’m going to use this theme for this blog 🙂
There’s tons of tutorial about how to add feature in WP Editor (tinymce) via “formats” drop downs, but none really explain how it works. Most just a recycle of other tutorials with different element and CSS and (sometimes) poorly coded.Read MoreComplete Guide to Manage Style Format Drop Down in WP Editor
I love using Hybrid Core Framework, I use it in all my themes, I don’t even know how to build a theme without it. Currently Justin is working on the Version 3 of the Framework and it’s offer a lot of improvement and features.
I want to create my own. Hybrid Core is modular and extendable so I can use only the features I need and bend it as I see fit, but I want to create my own framework so I can have full control of the features and code. For my themes I created “Tamatebako“, a Hybrid Core sidekick to build theme faster by setting the defaults. Now I want to experiment and make Tamatebako as a standalone framework.
The focus is a little different than Hybrid Core. Instead of building new awesome features, the focus is for faster theme development. I might failed and switch back to Hybrid Core, but I think it’s going to be a good opportunity to dive in and re-learn about theme development.
I haven’t even done porting main framework features (still a mess), but you can follow the development here.
Yet, a scary thought crossed my mind. I felt like I was ripping everyone off this time. I didn’t really do such a great job, but the atmosphere was really like that….
So, before others take notice, I need to quickly raise my standard. I have to work hard and change these bubbles into solid soap.