Branding thoughts

Ok, wait a second; I will completely admit that I am a geek, but the words intersect/intersection/interstate/intrastate and my made up word, Intrasect, which does sound like it could be a word, had nothing to do with geeks or computers at all! You're telling me if you say Intrasect, they think you're geeking out on them. I've heard of technophobia, but this is a word that is based on intersect, which has been in the dictionary since the 1600's.

I still stand by Intrasect.

Well, they thought that I was going to start talking about math, so, yeah. In their words: "well, I thought it had to be something either with math or computers because it sounds like one of your scary words".

Granted, the particular person behind that quote was a decidely non-technical/non-geeky female, but...

My list, based on rthrash's, in order of preference:

Moxie
SiteStorm
Impress[/list:u]I also like:
[list]Brainstorm
KittyHawk[/list:u]

[/list]

While I really really like BrainStorm, I had a few final ideas as well:

MarkupManager - Sounds a bit dull, but it certainly gets the point across.

PIZZAZZ! - I LOVE this name.

You know I like SiteStorm.

Sisyphus - You Design. Sisyphus does all the manual labor

Co|Co - Splitting Code and Content the way they should be.

and finally, LiteSite.

These are just a few, but these are the ones that I have been able to envision the best marketing campaign for.

I also like eQuill if we plan on risking it. I just don't want to see a similar problem to what happened to Alex, nor do I think we should let anyone even attempt to push us around regarding the name.

- John

LiteSite sounds to me too 'light'... Sisyphus sounds too much like it takes a shot of penicillin to clear up. :lol:

Well, I think it was Brian who said "The name needs more pizzazz" which gave me one of the names.

Thoughts on using Brainstorm?

I like it, but I think I like SiteStorm better. It's almost there, but not quite.

PIZZAZZ! - I LOVE this name.

Haven't heard this one before, but I like it.

Sisyphus - You Design. Sisyphus does all the manual labor

Not so fond of this one, though. Until I blinked, I thought it was the name of an STD.

Co|Co - Splitting Code and Content the way they should be.

Clever, but what would the domain be?

LiteSite.

Not so fond of this one, either, because I think it sort of sells us short. At least where I'm from "lite" usually means "lacking in features".

I also like eQuill if we plan on risking it. I just don't want to see a similar problem to what happened to Alex, nor do I think we should let anyone even attempt to push us around regarding the name.

I think this one has already been killed, but I'm not less convinced than I was that there would be an issue. For instance, I've managed to find a Palm word processor with the name eQuill:
http://hice-dev.org/~dstb/palm/equilAppPage.htm

Its been around since 2001.

But I'm in complete agreement regarding not letting others push us around on the name.

I also like SiteStorm better than BrainStorm.

I also like the potential for "cute" words for elemets of the system-- droplets instead of snippets, or puddles for collections of droplets. :lol:

I also like SiteStorm better than BrainStorm.

I also like the potential for "cute" words for elemets of the system-- droplets instead of snippets, or puddles for collections of droplets. :lol:

Its like your reading my mind

There is a ton of play on words for SiteStorm:

Project Names can be after weather events...and so could add-on modules
Zephyr
Cyclone
Tornado
Tsunami
Flood
Tempest
Wind
Blizzard


You get the idea.

And yes, I was totally thinking of the name "Droplets" over snippets. I want to diverge the name as far away from Etomite as possible.

I want to diverge the name as far away from Etomite as possible.

Ditto, and I think with the ideas floating around we are actually quite a bit down that road.

I really wish we had some sort of working name prior to the first release so that we could purge things like "etomite.class.inc.php" and $etomite from the core and use whatever we are using as our identity.

Doesn't make sense to me that we'd want developers to continue coding against $etomite, but I'd also not like to have to change this between releases, so I don't think we should change it to $modx until we have one.