Pepsi bought Mountain Dew, and that turned out better than fine.
I’m not exactly a GoDaddy fan, but nothing has changed. Media Temple is still run by Media Temple’s people.
Agree on these points:
- Ratings should be public
- Authors should be able to reply to ratings
- Malicious ratings should be flaggable and removable
- Authors must be able to see who rated the item
- Every marketplace user should have a ratings profile. If they are repeatedly shaming authors it should be traceable and knowable by all authors/buyers.
It’s imperative that the long-term goal of ratings is to establish accountability. Anonymity does not create honest systems. If a user does not want his rating public, then he cannot rate an item (like: Amazon).
These safeguards need to come to protect against competitors / angry buyers who use ratings to hurt an author.
TommusRhodus saidNo, we are two now;)
Am I the only one that uses MacRabbit Espresso?
I (woefully) abandoned Espresso. Their team (in my mind) wasted an entire release cycle making Espresso absorb their visual CSS editor app (CSSEdit). Meanwhile responsive design and pre-processors happened. The community was too small to pick up the slack, and the app still stumbles over a lot of things that Sublime just does.
Sublime Text is probably the most extensible and widely used today.
To counter-act the heft of negative feedback on this:
@ Envato — Do what you think you need to do to improve the marketplace as efficiently as possible. I am a fan of the frontend changes happening on other Envato sites, and if dropping old visuals makes the marketplaces more extensible/maintainable then that means faster feature rollouts. Go for it.
@ Authors — You shot yourself in the foot assuming the background color would never change, and loading up item descriptions with images. Deal with it, and don’t make the same mistake again. But before you convert everything to 32-bit PNGs spend some time learning about image compression and start hosting on a solid CDN, or stop using images. You’re making the marketplaces feel slower for buyers and hurting everyone.
You don’t need GitHub to use git (git is the underlying VCS tool). You also don’t need any remote repo (GitHub), but if you want a private one to push into Bitbucket has free private repos (team collab is paid).
ToivoMedia said+1 All I use when slicing a PSD template – Would love to hear some advice from you
GravityDept saidWhy not give an alternative to this “terrible” advice? No time to write something constructive?
UniikMedia saidPhotoshop has some of the worst optimization for screen display. This is terrible advice if you stop there.
Photoshop > Save for Web & Devices. Voila.
Thought it was obvious, but you have to read the article: http://notes.envato.com/general/image-performance-tips-for-authors/
That’s why @UniikMedia’s suggestion completely missed the point and is bad advice.
Subtext to this thread:
Dear authors, the unoptimized images you’re cramming into item pages from cheap, slow servers is making Envato look bad. Fix that. Kisses, Envato
They’re the reason I haven’t started any new projects in WordPress in three years. So much simpler and easier for clients. http://statamic.com is my go-to CMS for content-driven sites.
What makes them good as a CMS (content-driven administration) makes them bad for generic themes since there really isn’t a prescribed content architecture like WordPress (which is still noticeably bound to its blogging roots).
I could definitely see people writing themes for specific archetypes (blog, portfolio, small business, etc), but I doubt they’ll be as popular as WordPress because many of the newer CMS are paid (and worth it).