[…] working on a new theme today and you’re introducing some cool new features, using some nice HTML5, CSS3, and/or JavaScript effects, and then you sell it and support it for a few years. But then some aspects of the aforementioned languages become deprecated, or newer techniques are introduced. Then what? Keep supporting the current […]
Search: “support” (Page 7 of 67)
We found 334 results for your search.
[…] year. During that time I learned a lot about what makes or breaks a successful plugin (and what kind of things can seriously drain you from a support perspective). In fact, I eventually killed both of those projects off because I no longer had the desire to work on them, maintaining the support required […]
[…] set of ethics. I’m my experience, it’s true – though, as with anything, there are outliers. As I continue to work to introduce a premium level of support for my WordPress-related work, one of the things that I’ve found myself wrestling with is turning a profit on work to which others have contributed. But […]
When it comes to writing, releasing, and maintaining WordPress plugins is figuring out how to actually support your work once it’s released. After all, the majority of work on software is maintaining the codebase and responding from all of the feedback given by users or customers. In my latest article on Envato, I talk […]
[…] You can also do this for other things such as settings and keybindings, too. Simply replace the above code with the following commands: $ rm -d ~/Library/Application\ Support/Code\ -\ Insiders/User/settings.json $ ln -s ~/Library/Application\ Support/Code/User/settings.json ~/Library/Application\ Support/Code\ -\ Insiders/User/settings.json $ rm -d /Library/Application\ Support/Code\ -\ Insiders/User/keybindings.json $ ln -s ~/Library/Application\ Support/Code/User/keybindings.json /Library/Application\ Support/Code\ -\ […]