Framework names ideas

While planning centers mostly around how we're going to implement things from a technical level, we also need to come up with a name for the framework project itself. We screwed this up with MWF, and thus we got MWF, the "Mobile Web Framework". This mistake was not made in the case of a more recent polling tool we produced that we named "OPT" and then came up with what it would mean: "Online Polling Tool". However, there's a lot more to a name than just an abbreviation. We may just want to pick something that's short, sweet and rememberable, without having any actual relation to what we're doing. Examples range from Zend to jQuery - they're not call the "PHP Modular Framework" (PMF) or the "Javascript Making Things Easier Framework" (JMTEF). Instead, they've got things that are memorable. In jQuery's case, the Query kind of makes sense because you query the DOM through it, but that's as far as the relation goes - and Zend is even more abstract, just an idea. Same goes for Twitter Bootstrap (though arguably they should have foregone the whole "Twitter" part).

The reason that this is important is, as we start developing, we need an overarching namespace (at least for the Javascript and maybe for the CSS too -- see Conventions).

As such, let's start brainstorming name ideas below...

from albert -

• WebBlocks (homage to Lego building blocks)
• WebBricks (ditto)
• WebParts
• Web Foundations Framework – WFF
• Web Templating Framework -ahem...

Eric is +1 on WebBlocks