for several months we are working on our first WordPress theme, but as a newbie I have some questions which bother me, and I’m looking for answers.
I noticed that themeforest society is very friendly so I decided to ask my questions on the forum, maybe you will share with me your experience:
How looks your workflow for bugs reporting? From the bug report by the user, through fixing the error to update the fixed version of the theme?
What tools do you use? – git, grunt / gulp, unit testing?
Do you automatize interface tests? – if not, then how do you react when the new version brings new bugs? (Of course automation does not exclude new bugs but it reduces the risk of complications)
Do you have come to the point where you decided to re-build your framework from beggining? – if yes, would you do it again?
How looks your workflow for testing new version of your theme ? (when you bring new important features)
How often do you add new functionalities and features to you theme?
How do you organize team? Is it a rigid structure, where specific tasks and responsibilities (like bug fixing, code optimizing, designing new features and solutions etc.) are strictly assigned to particular members? or is it rather a fluid structure and assignment of tasks depends on changing factors?
I realize this is a lot of questions but I hope that someone will respond at least some of them.
If you replace the word “theme” with “plugin”, I can reply to some of your questions. Effectively both are applications of some sort, so the fundamental rules will be the same. Find replies to those which apply:
A user creates a ticket, which I investigate. Based on the diagnosis I decide if it’s users fault or our script’s. If our script’s, I determine if it’s a major flaw or a minor thing that can be appended to our to-do list. If it’s a major issue, I push the fix live asap and notify everyone about the patch. If it’s a small thing, it just waits until the next plugin update along with other features.
It will depend on the script complexity, but I am fine with just a GIT repository, where I create branches, tags etc to stay on top with the organisation.
I have a development instance of a WordPress installation where the latest version of the plugin is installed. I try to come up with a few use cases, which I test. I also try to do various extreme tests and unusual things to our code to see how it behaves (the devil is always in details).
Depends on the time I have, the amount of requested or invented features. I guess it’s different with a theme, because there much more things involved, however with a plugin I tend to release new versions whenever I come up with an idea and finish coding it. No reason to wait. Also, it’s less error prone when you have to test one thing, rather than ten.
First make a moodboard with webdesign images (Images from dribbble, behance, others themes, my personal inspiration stock … )
I do some sketches and lists with features about what I want to continue.
I have already my own framework. On it began to create what we have on paper. To work ordered using Task function from Notes - Mac OS ( it is simple and free ) Plus it synchronizes with my iphone, imac, ipad, macbook.
After that I started to create demos and presentation page. Now is easy. With thousands of pictures saved and thousands of inspiration images printscreen websites. But at first it was hard.
Once the theme is ready to start a test. Usually a test with all browsers on Windows, Linux, Mac, Android, iOS …
After I do the documentation, presentation … blah blah and upload this .
How looks your workflow for bugs reporting? From the bug report by the user, through fixing the error to update the fixed version of the theme?
Customer contact me via email or support pages. First I make sure if the client did all the steps correctly. If I notice that the error was from me put this on task list and a fix it in the first update. And advising the client date will receive a udpate (Maximum one week) . If the error is fatal getting down and solve in the same day.
What tools do you use? – git, grunt / gulp, unit testing?
For write code I use Sublime Text. And I have active different features (autocorrect, detect code errors, others … ) . Staying organized with Notes (Mac OS) connected / sync in iCloud .
How looks your workflow for testing new version of your theme ? (when you bring new important features)
I have a development instance of a WordPress installation in my server, install my theme again ( as a customer ) . After checking with the W3C, WP_DEBUG, Theme Check, try to do various and unusual test things . As I said above check theme on all browsers.
How often do you add new functionalities and features to you theme?
When are requested by the customers or I have time. Usually for new features on support page I create a poll with proposals from my clients and my ideas .
How do you organize team?
My team only deals is with support or test and report. If they have any questions or suggestions, her contact me on an internal chat from support page or email . Development and design I do alone. For some projects … I have project collaborations. Here is more complicated, usually during project using tech hubs or office rent…or Starbucks .
Maybe someone else would like to share his experience in theme development ?
and solve in the same day.
(Mac OS) connected / sync in iCloud .
.