Category: Articles (Page 178 of 259)

Recently, Stephen shared an interesting site with me – User Onboarding – in which, as the site states, seeks to do the following:

User Onboarding is the process of increasing the likelihood that new users become successful when adopting your product.

Learn some lessons from how popular web apps do it!

It’s a really simple, straightforward site that highlights how various applications sign up, sign in, and continue using a product. Not only that, it also looks at what’s bad about the process, too.

In short, it’s a great site to peruse (or to throw in your RSS reader) if for no other reason to check out some of the ways in which other companies attempt to garner customers.

But principles, by nature, tend to be transferrable (not always, but many times). This means that some of the lessons explored throughout the various teardowns the site does are applicable to onboarding users with WordPress.

Continue reading

Last week, I shared a few thoughts on how I think that major updates to an existing WordPress theme are actually more analogous to a new product rather than an update of the existing product.

That is, if a theme is identified by the way it presents the content of the blog, then it stands to reason updating the look and feel of the theme is changing the very thing that gives the theme its identity.

So, from there, it’s reasonable to ask the question: Once a theme’s design is locked in, should it ever change?

Continue reading

Designers and developers, by their nature I think, are attracted to new things if for no other reason than to see how it’s designed, how it’s put together, how it functions, and so on. I don’t consider that a positive or a negative – it’s just a trait that some people have (and certain types of people exhibit it more than others).

That curiosity matched with the desire to constantly be improving at one does do for a living (or for a hobby) is what separates those who see the gig as “just a job” and those who see it as what they’re dedicating their lives to doing.

Yes – it can be expensive: Some like to purchase new devices as soon as they are released or new products as soon as they are released in order to familiarize themselves with them, and then to try to bring back what they’ve seen, learned, and experienced and build it into whatever they’re focused on creating.

But when you bring this approach into something like WordPress theme design and/or theme development, it has the obvious potential to improve future work but it can also negatively impact existing work.

Continue reading

I think that one of the best ways to stay current with whatever tools, languages, etc. that you’re working with is to take a look and see what other communities are doing with their tools.

For what it’s worth, I also think that bringing experience from previous projects and/or jobs to new projects and/or jobs is important – you get a chance to continue doing all of the things that worked well, a chance to avoid the things that didn’t work, and a chance to discover a new set of things that work and things that don’t.

One of the more popular tools to come out as of late is Docker. There are a lot of really cool things about it, and there are a lot of articles already being written about it. I recently read one that struck a chord with me and with WordPress-related development.

Especially this quote:

Logging is a critical part of running an application. It’s often undercooked because it’s been here for so long no one think about it anymore. But trust me, when things stop logging, admins start crying.

Yes, it’s a good read for anyone who likes to see how other developers are doing their thing in another area of the industry and there’s a number of points made that I think many people who have been working in software for a number of years can identify with, but I couldn’t help but ask myself if I’m doing (or we’re doing) enough logging in the WordPress projects I’m (or we’re) deploying.

Continue reading