Google trademarked Knol back in the day (2007). A USPTO search shows it is still live:
http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4809:9wz...
Electronic publishing services, namely, publication of text and graphic works of others in the field of general encyclopedic knowledge; providing education, entertainment and information services, namely, providing information via the Internet in the field of general encyclopedic knowledge.
It also must be stressed that it is not sufficient to have a disclaimer: the user even getting to your website to even see the disclaimer is effectively already under false pretenses, and not everyone reads those messages anyway. If anything, that you feel the need to have such a disclaimer is good evidence that people are, in fact, being confused by your naming. I, for a concrete example, am only on this comment thread because "oh, I remember Knol... I am surprised they are trying to reboot/revitalize that project", and would have read a ton of these comments under that vague premise had it not been for this top one making it clear "no, this is not Knol". This is just such an egregious example of what you can't do with identity :(.
http://www.ipo.gov.uk/tmcase/Results/4/EU006911796
and the OHIM website, which as I understand it covers Europe-wide trademarks:
https://oami.europa.eu/eSearch/#details/trademarks/006911796
But like I said, I am not a lawyer, do your own research, consult an expert etc etc...
One deal-breaker for me is that it has to feel like it's on my website. This means templates are not enough: I need full CSS customizability (statuspage.io does a good job with this) or iframe ability. The lack of a great, fully customizable product in this space is why I am currently fucking around with Markdown pages.
It's certainly fair to charge a lot more than you're apparently charging in order to get this customizability -- needing it probably predicts a real business that cares about its brand. (If knol.io becomes a big business I bet you'll end up charging a lot more in general.)
Anyway, awesome job with this! Looks like a great product solving a real problem.
Theme customisation is definitely something on our future features list. But maybe we should move it up on the priority list. ;-)
Let me know if you have any questions. I'll be glad to answer them!
"Import your existing documentation, create new ones or choose from our exsiting library!"
Edit: tone
I like the idea of what you are doing I'll be sure to keep an eye on it :), Good Luck.
I hope the examples explain better what we are trying to achieve here.
Personally, I've never liked seeing this in ToS and the like - it usually means "unlimited until you hit the limit we didn't tell you about"
