If you build a plugin that require template modification, it might be a good idea to bundle an example theme in your plugin. And here’s how to do it.
My first plugin at WordPress.org ! f(x) Share.
Wow. that feels great.
WordPress Dashboard Widget API is my favorite API in WordPress and sometimes dashboard is my preferred admin page to add simple settings in client site. It’s the screen they will see when they logged in. Why not use it more?
In this post I want to share a little about how to properly save the dashboard meta box “Configuration” with the build in nonce validation.
I read a lot of tutorial but no mention about this, I don’t even find any reference in Codex page.
So, I did some test for WordPress 4.4 beta3 new feature: Responsive Images. And it will make your content retina ready automatically! Awesome.
Not only that, it will also serve smaller image to low res device and it will make your site load faster to the less capable mobile device.
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:
Download f(x) Share @GitHub
This is a useful control, we can use it for various settings for example:
- Reorder element, such as header, navigation menu, thumbnail, excerpt, etc.
- Sharing buttons.
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).
The only way to disable theme update check to wp.org repository is using this code (well, it’s pretty much a hack):
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.
One of my theme “Press Start” is featured at WordPress org featured section. WOW !
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.
A beautiful WordPress theme inspired by file explorer. I create this theme in 48 hours (well, actually 12.5 hours).
So, a few days ago Sami Keijonen create a challenge to build a WordPress Theme in 48 hours. He mention that he need several months to build a WordPress Theme.
Well, for myself, the challenge is not really hard. I usually build a theme in 2-4 days for simple custom theme. As long as the client already have a design (PSD/design inspiration/example) I can build it in less than a week.
I only charge $300 – $500 for a very simple theme. So, I need to work fast 🙂
WordPress is a Global CMS, with very minimum requirement to install:
PHP: version 5.2.4
MySQL: version 5.0
I’m sure most of us have better server configuration than the minimum. I think most hosting have at least PHP 5.4 installed. but as a freelancer, sometimes we get a client with older version of PHP in their server. And for whatever reason they cannot/do not want to upgrade to better hosting.
If you don’t have multiple PHP version in your server, you can always install multiple PHP version in your server and pollute your server with outdated script.
Or you can spent $10 and have a separate server where you can test your code for whole year.
$10 / year, that’s only $ 0.83 / month