Hey 0xFF,I revisited this thread just now and thought it may be interesting to expand upon what you said regarding the staff side:>On designers side, the reason why is quite clear : it's far more of work and difficulties to provide both sidesActually, you are more correct than you may realize! It's not that creating a theme for both sides is twice as much work or even 3x as much work... osTicket's code base is very difficult to work with, and I would estimate that themeing the staff side is at least 10x as much work as the client side. I assume that is why (to my knowledge) no one has attempted it before.>I'm wondering if the staff side is really useful; it's not an answer but a reflexionIt is interesting for me to encounter this perspective. When I started using osTicket 1.7, it quickly became the center of my business. It improved my workflow in more ways than I could have predicted, but I found it painful to look at. I started tweaking the layout for my own internal use... I never had any intention of developing a commercial product. And, actually, my entire focus was the on the Staff side. I found myself having multiple editing sessions, sometimes for hours at a time. I was so invested in my own tweaks that I didn't upgrade my osTicket until 1.9, and at that point I would often spend an entire day editing to try and make everything "just right".At some point I thought to myself, "I have put hundreds of hours into this. It's too bad that no one (outside of my small business) is ever going to use it". At that moment I heard the echo of something a Unix guru / friend had said to me years earlier, "You can take an open source project and turn it into a commercial product". I think he used Apple's OS X as an example. I wasn't even aware at that point that other osTicket themes existed. But when I saw their price point and —comparatively — how little effort had gone into them, I decided to go down that path.Obviously, there is a huge difference between designing something for one's own use vs. designing the same thing for the masses. The first step was to comb through my own code and divorce myself from it. And I also decided to begin to working on responsiveness.And it was at at this juncture that I began to work on the Client side. Truthfully, I have yet to use the Client side for my own business. I have always intended to, and I still do. But clearly my relationship with osTicket evolved into much more of a distraction than I ever expected. So that's my story. Not only is osTicket Awesome the only theme (at this point) that addresses the Staff side, its initial focus was entirely on the Staff side. If the argument were made that the Client side is the public-facing part of osTicket that represents one's organization and thus the most important to improve, I could counter by saying, "Good point. But in most scenarios the Client side gets little use compared to the Staff side. Your clients log in, open or review a ticket and then they're gone. Whereas the Staff side is monitored and used all day, every day."But now you have made me curious. Perhaps I'll start a survey on www.osticketawesome.com and ask people which side is more important to them.