TBB borrows the scheduling portion, but requires substantial code restructuring, and doesn't have a solution for the global variable problem analogous to Cilk's hyperobjects.
Cilk++ is a considerable upgrade to MIT Cilk: support for C++ (rather than just C), for Visual Studio (rather than just GCC), support for loops (rather than just recursion). It's considerably more transparent to the developer.
It's easy: show me the code. Links to quick examples and tutorials that show me what and how this language can do are amazingly useful. Pretty much you want the primary focus to be on using your language, not selling it. You have a navbar across the top; at first glance I know for 100% certainty only what two of those links will do for me ("home" and "company").
In short, look at http://python.org/ , http://www.perl.org/ , and http://www.ruby-lang.org/en/ . Focus on enabling the developer to do something useful as soon as possible. Focus on community, libraries, etc... If you make one change and only one change to the site, add a link titled "Getting started"... make it a wiki. See http://www.erlang.org/starting.html for more inspiration. Right now it feels like the marketing department designed the the cilk site.
2. Cilk++ guarantees space bounds. On P processors, Cilk++ uses no more than P times the stack space of a serial execution. In OpenMP, not so.
3. Cilk++ has a race detector for debugging and software release. With OpenMP, you are on your own.
4. Cilk++ has serial semantics. With OpenMP, you do not have this benefit – only a subset of OpenMP supports serial semantics.
5. Cilk++ has a solution for global variables (a construct called "hyperobjects"). OpenMP does not.