Cleanity Complete Admin / CMS Skin

OMG … awesome work man, I really like the menu effect… so beautiful

Ha ha… Now that’s an admin theme. Amazing!!!

btw what WYSIWYG editor did you use?

Thank you!

@miles-ws: It uses jquery qysiwyg =)

@onuro: Thanks for your help. I will buy ASAP .

Yes definitely a nice piece of work. Clean, simple and effective !

amazing!

very nyce…

keep em’ coming (more color variations), maybe even a v2

@Mrlami: Why not!=) I’ll see if it gets popular and gets requested much, maybe I can add more features into this in the future.

when I try to look at Live Preview, all I get is request for logon and password, what is going on?

Al

@al_m473: all you need to do is to hit/enter or login button

Any chance you could list the jQuery plugins you’ve used?

I can’t tell from the source code for obvious reasons and I’ve bought quite a few templates that have plugins that only work with 1.2.6 and I will be using 1.3.2.

Would be great if you could name them

Thanks, Chris

You can see the the details in the help document of cleanity =)

This is FANTASTIC . Thanks Although I’d have preferred to see at least some sort for example for source code, whether it’s a 10 line snippet or something, just so I know I’m not going to rip my hair out when I’m integrating the pre-existing code, or working with it.

@Cupcakes: Thank you very much for the purchase!

Well I could have opened the source code on the live preview but I just didn’t want to ruin the surprise (and of course for non-buyers, I wanted to keep the copyright for template viewing purpose only) for the buyers and I believe you are satisfied with the code and overall ease of use, am I right ?=)

Again, thank you very much and please let me know if you have any questions about the item.

Onur

That’s not what I was suggesting. I was at least suggesting a link to a txt file with some snippets of your CSS source, and your XHTML source in your main comment above that would go with the rest of the product description.

I’ve found that I prefer to know that what I’m purchasing isn’t going to be a mess to go through, or have inline styles, etc. I’ve had this with another template, and it’s a mess to try to go through.

The only complaint I have is just that we have dissimilar ways of managing the organization of our CSS source. I think using div. and div# is unnecessary and bloat, and all elements on one line to be tedious to run through… But obviously I just had to spend some time to just organize it to my preferences.

I would just rather be able to SEE some source first (not even through a peview, like I said, just literally some snippets to get an idea) prior to purchasing. That’s all.

@Cupcakes: I see what you mean. But that in case, I mostly commented many lines and for the snippets, I included the origins as links of the plugins and libraries I used(inside the help document).

And using div#foo, and span.bar like selectors are not only because they were necessary, also because I wanted to assign them only to the referring element, not anything else (in that case, the id div#foo can only be used for divs and won’t work on [let’s say] form with id of #foo).

So like in most professional development code structure, defining elements strictly helps css & programmed code to interact better.

You are also welcome to contact me if you still need any snippets, application examples that will speed up your customization =)

Thank you very much.

Onur

Excellent. Just purchased. Can you tell me where you got those icons? I like the style and I need to change them up to suit my custom app. Thanks!

The icons are from the free Vaga Icon Set

just bought this, checked over all source and v happy – great job and I’m most pleased – $12 for what’s essentially 3-5 days work for me. Projects a week ahead of time thanks! (which is great as its a week late )

love it

I’m not sure what your commented lines and/or documentation has anything to do with just a suggestion I made to include a sample of your sourcecode. I’m not buying solely because of the design (if that’s the case, I’d stick with a PSD ) but also because it’s a pre-coded template, which obviously means I want to be able to SEE what I’m purchasing and to know that I’m not going to put down money on code that’s going to give me a headache (which has occurred before here on Themeforest.)

RE: To your explanation of the css bloat, it doesn’t really make sense to use the same ID for other elements within the design itself. Do you really think it’s feasible to see span#nav, ul#nav, and div#nav all in the same document? To me that’s just poor choice of properly managing your stylesheet. But to each their own, like I said, it was a minor edit for me to go through and clean through things to how I wanted it.