I know XHTML /CSS/JS/PHP, and am learning to scrape out some designs as well
So I’ve got the technical end covered. What I’m wondering is what you guys expect for documentation – a simple file detailing what values and such to change, what you can change safely, etcetera?
What does it need to include?
- Attended a Community Meetup
- Australia
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 1000 and 4999 items
- Contributed a Blog Post
- Contributed a Tutorial to a Tuts+ Site
- Envato Staff
- Exclusive Author
Totally up to you really, I tend to find on FlashDen that some authors develop a sort of templated documentation file and as buyers get used to them, they keep buying from that author – if that makes sense.
I’d imagine for CMS products you’d need more documentation than for HTML templates, but how far you go is up to you.
Sorry that’s a bit of a vague answer 
I’ve just submitted my first HTML template and have only included a simple readme.txt file. In it, I summarized the theme, what’s included in the ZIP file and some other minor details…
I don’t think any more is needed/expected…
But like Collis said, it’s up to you… 
Thanks
I’ll keep that in mind for when I finish these couple templates I’m working on. Hopefully, that’s very soon!
