Just a heads up, Pietro pushed his designs and a first html / css demo to https://github.com/mootools/website The html / css might have to be redone, since this was simply a quick prototype.
So now we're at the implementation stage: https://github.com/mootools/website/wiki/Implementation The website will run on node.js. I think using Express would make sense. Personally I like Jade and Stylus, but anything else would work too. It would be cool if someone could set something up. If that's too much I can do it next weekend so it gets easier to iterate from that. On Tue, Mar 26, 2013 at 2:54 PM, Eric Patrick <[email protected]> wrote: > My 2 cents: > > I believe the MooTools site should showcase demos of multiple UI > frameworks. Bootstrap is a must because it is indeed full of goodness, > actively supported, and wildly popular. VM UI looks awesome, and is a > great showcase of how one can leverage MooTools. > > As a parallel, my company offers a document imaging module integrated in > our product suite. It's interfaced based. We include our own imaging > (based on Amazon S3), and have plugins for several of the major vendors. I > love when our clients choose our own version, but if they have *money and > talent invested in something else popular* (e.g. FileNET), I want to*make it > easy > * for them to pick our products (without worrying about building FileNET > integration). Having that interface out of the box is a huge selling point > for us. > > My thoughts on 'interfaces' (wrappers, whatever we want to call such > plug-and-play offerings) we might want to feature on the Mootools site to > encourage others to choose Mootools: > > - Bootstrap (with Aaron's behaviors, or with exact jQuery > replacements?) > - VM UI (native Mootools!) > - Mapping providers (Google, Bing, MapQuest, Yahoo) ? > - Facebook / Google+ / Twitter / LinkedIn ? > - Google Visualizations ? > > Other thoughts? > > Eric > > On Monday, March 25, 2013 11:33:59 AM UTC-4, Nutron wrote: > >> I've been pretty quiet so far on this thread (except up at the top where >> it got kicked off) so I'll share a few thoughts: >> >> 1. I love that the main drivers of this thread are not core MooTools >> devs. It goes to the point about you guys (and girls?) taking MooTools to >> the next level and making things happen. And here you are! >> 2. I'm content to stay out of any of the decision making but I'd like >> to throw in my 2 cents for Bootstrap. Here's why: >> 1. I use Bootstrap all the time (http://www.thanx.com and the >> mobile implementation of our app at http://app.thanx.com both use >> it). Your stuff doesn't need to look anything like Bootstrap to make >> use of >> it's goodness. >> 2. It's a robust and mature CSS framework and everyone else is >> using it. I think it might actually be a GOOD thing to show that >> MooTools >> can work just fine w/ Bootstrap. >> 3. The default styles, though a bit boring, are well designed. I >> can't stress this enough. You have to try and make ugly things with >> Bootstrap. I can't say that about most other CSS frameworks. >> 4. I have an implementation of most of the Bootstrap features ( >> >> http://github.com/anutron/**mootools-bootstrap<http://github.com/anutron/mootools-bootstrap>). >> It may need a little bit of updating for the latest version (I don't >> think >> so). It does not use the same JS signature; it's not a 1:1 port of how >> you >> invoke it (it's more of a MooTools style). Use it or don't, but my >> point is >> only that implementing it wasn't that hard. >> 5. Avoiding Bootstrap because they implemented a version of it w/ >> jQuery is a silly reason. >> 3. I'm so happy and proud of this community. Keep it up! >> >> >> On Mon, Mar 25, 2013 at 6:01 AM, Tony Brown <[email protected]> wrote: >> >>> Excellent! >>> >>> On Mon, Mar 25, 2013 at 8:28 AM, Tim Wienk <[email protected]> wrote: >>> >>>> Please do not go too much in-depth with all this yet, at the current >>>> stage I'm confident there won't be a finalised website in two weeks. >>>> We are still just exploring and looking for the right direction and >>>> gathering ideas. Actual implementations (let alone platform or "CMS" >>>> decisions) are not even point of discussion yet. >>>> >>>> Meanwhile a small word of concern regarding the design, as Valerio has >>>> mentioned (see https://github.com/mootools/**website/wiki/MooTools.net- >>>> **redesign<https://github.com/mootools/website/wiki/MooTools.net-redesign> >>>> ), what we're looking for is a rather light design, a lot of >>>> whitespace and clarity. While I think your designs are rather nice in >>>> general, they don't seem to follow that principle as much as the other >>>> mockups in the Wiki do. >>>> >>>> There is some discussion and collaboration regarding the layout >>>> aspects taking place in IRC (#mootools on Freeenode, or >>>> irc://chat.freenode.net:6667/**mootools<http://chat.freenode.net:6667/mootools>). >>>> You can use your favourite >>>> IRC client, or https://webchat.freenode.net/ if you'd like to join. >>>> Feel free to ping Timmeh or arian (or just ask in general) in that >>>> channel if you'd like a quick update, when someone is around they'll >>>> poke you back, I'm sure. (This goes for everyone, but it'd be >>>> especially nice to see Benjamin there. :-) ) >>>> >>>> Furthermore, there hasn't be a lot of activity on the mailing list >>>> regarding the redesign, since we try to collect the different ideas >>>> and remarks in the Github wiki, feel free to add your own ideas as >>>> well: >>>> https://github.com/mootools/**website/wiki/_pages<https://github.com/mootools/website/wiki/_pages>. >>>> I'm really >>>> impressed with the level of the designs and designers we're seeing, >>>> the final outcome will surely be a combination of multiple people's >>>> designs (in fact, most of the current mockups in the Wiki are already >>>> results of combined ideas). >>>> >>>> -- >>>> Tim Wienk, Software Developer, MooTools Developer >>>> E. [email protected] | W. http://tim.wienk.name >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "MooTools Users" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/** >>>> topic/mootools-users/fz2dbZE-**iOk/unsubscribe?hl=en<https://groups.google.com/d/topic/mootools-users/fz2dbZE-iOk/unsubscribe?hl=en> >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> mootools-user...@**googlegroups.com. >>>> >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> >>> >>> -- >>> *Sincerely,* >>> >>> Tony Brown >>> >>> twitter: >>> https://twitter.com/**pixelBender67<https://twitter.com/pixelBender67> >>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "MooTools Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to mootools-user...@**googlegroups.com. >>> >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "MooTools Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "MooTools Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
