Josh Betz
Made with 🧀 in Madison
Made with 🧀 in Madison
We launched the dsgn365 podcast this week. Check out the introductory episode and make sure to subscribe in iTunes.
Let’s say you have a new web project you’re working on. Sure, you could setup a web server on your local machine and develop locally. For some reason you don’t want to do that though. Anyway, with this setup we’re going to assume you have some kind of landing page at the URL – why not? And you have a development directory `dev`. Now, as things get more complicated with this project, it would be nice if you could just point your browser at the root of the domain instead of a development directory. After all, eventually that’s where it’s going to live. Luckily, the solutions lies in `.htaccess`.
(more…)
I actually doubt Dan Benjamin1 uses WordPress or cares about custom fields. The point is, your average client shouldn’t have to know or care about custom fields. I’d be happy if they were disabled by default — as long as I have an option to enable them by defining a constant in the wp-config file.
With a bit more work on your end as a developer, you can create a custom meta box that points directly at a custom field. If you’re really crazy about it like I am, you could even use a hidden key for you custom field by starting the name of the key with and underscore.
I think the ideal situation is if you happen to be working with a custom post type. It’s easy enough to turn custom fields on or off for any post type you create. So you can do all your testing with the custom fields turned on and turn them off when you get everything set and ship the theme off to the client. In the scenario, I don’t even bother using hidden keys, since there’s no way to access them directly through the custom field boxes anyway.
(more…)
It’s interesting watching the web and its technologies develop. A project that I’m currently finishing up is for a website that I’ve seen through a few iterations now. I did the first design for them a little over four years ago as a sophomore in high school.
At the time, I had already been using WordPress for awhile. It didn’t really even seem like an option for this site then though. As crazy as it seems now, Dreamweaver templates were what we decided on and that kept everything fairly sane — at least by the standards at the time. Managing it today would be considered a nightmare.
(more…)