search

WedgeServer / website

Website for Wedge
GNU Affero General Public License v3.0
2 stars 0 forks source link

Website copywriting #1

Open mr-tcan opened 6 years ago

mr-tcan commented 6 years ago

I didn't run the website locally because I don't know Scala but I read the index.scala.html.

There is a lot of references of Caddy and considering that this fork was misunderstood and provoked some overreacting from Caddy devs (the trademark infringement issue), I was thinking if it is not better to focus on Wedge itself instead making comparisons.

For example, instead of A fork of Caddy without the license fees or a restrictive EULA. Free to use however you like. we can use Wedge is a modern and secure webserver with no ads, no license fees and no restrictive EULA attached. or instead of Wedge does not have a commercial support offering / Caddy has a paid, email-only support offering we can use Wedge support is provided by our awesome community. And many people in the dev community are scared by the word "fork" so instead One of the core aims of the fork is to maintain API compatibility with Caddy ; so all of the great plugins you may already know should work out of the box. we can use "Wedge is based on Caddy source code and maintain API compatibility .. `.

Just some thoughts. :D

lol768 commented 6 years ago

Hey, thanks for your thoughts!

As you've no doubt noticed, marketing and writing isn't really one of my strong points so thanks a bunch for these suggestions. I guess part of my reluctance to drift too far from "Wedge is a fork of Caddy" is a) a reluctance to present Caddy's work as my own when it's not and b) a desire to make it clear we are prioritising API compat. with this. I think you're right in that Wedge needs to stand on its own two feet though.

I'll go through these and swap these out in a little bit.

mr-tcan commented 6 years ago

I understand your points but think about CentOS. CentOS is derived from Redhat source code minus the trademark stuff and they make it clear in their About page. There is OpenResty to which is based on Nginx source code plus LuaJIT and they make it clear that it is not a fork in the sense that it is not compatible with Nginx. So I think it is pretty easy to tell people that nobody is "stealing " nothing from anyone and the project is API compat.

My marketing and writing skills are better than my code skills, so I can help you with that.

lol768 commented 6 years ago

https://github.com/WedgeServer/website/commit/afb523b7e686e541f16865323956666e02a03221 incorporates most of your changes, I think.

I think the "Automatic TLS" wording could probably do with being revised at some point. I suspect there's too much technical jargon in it. It might be worth using "HTTPS" throughout, too.