@Massimo is there a page somewhere listing the projects derived from web2py? I think maybe one reason is the lack of awareness and visibility of such web2py derivative projects
On Tuesday, July 31, 2012 11:51:56 PM UTC+8, Massimo Di Pierro wrote: > > I agree web2py needs a good CMS. The problem is that different people > expect different things from a CMS. Some time ago I posted code for web2cms > but nobody has contributed to it. :-( > Now I am trying put some of that logic into auth.wiki() > > > > > On Tuesday, 31 July 2012 10:21:24 UTC-5, Luther Goh Lu Feng wrote: >> >> I wish to share that imho one of the strengths of web2py is its >> dedication towards backwards compatibility. This is something not >> frequently found in other frameworks, eg in Django or in Drupal. >> >> Therefore, I believe that if a web2py project, be it CMS or otherwise >> gains a sufficient following, it could possibly be very successful. >> >> Just my 5c >> >> On Tuesday, July 31, 2012 9:40:15 PM UTC+8, Mariano Reingart wrote: >>> >>> On Tue, Jul 31, 2012 at 10:08 AM, Mariano Reingart <reing...@gmail.com> >>> wrote: >>> > On Mon, Jul 30, 2012 at 6:13 PM, Tim Michelsen >>> > <timmichel...@gmx-topmail.de> wrote: >>> >>> Instant Press is built by @Martin and I dont know if he gets >>> contribution >>> >>> Movu.ca is built by @rochacbruno (me) and I did not get too much >>> >>> contribution (two or 3 people helped with ideas and translations) >>> >> >>> >> Do you think muvuca could be staffed with the features shown in >>> Mezzanine (I >>> >> haven't know it before nor used it): >>> >> >>> >> Hierarchical page navigation >>> >> Save as draft and preview on site >>> >> Scheduled publishing >>> >> Drag-and-drop page ordering >>> >> WYSIWYG editing >>> >> In-line page editing >>> >> Drag-and-drop HTML5 forms builder with CSV export >>> >> SEO friendly URLs and meta data >>> >> Shopping cart module (Cartridge) >>> >> Configurable dashboard widgets >>> >> Blog engine >>> >> Tagging >>> >> User accounts and profiles with email verification >>> >> Translated to over 20 languages >>> >> Sharing via Facebook or Twitter >>> > >>> > Please, take a look at web2conf: >>> > >>> > https://code.google.com/p/web2conf/ >>> > >>> > It has many of your requested features (wyswyg online editor, >>> > navigation bar, user profiles, twitter and blog/rss integration, >>> > schedule/ratings, translations). We are adding something similar to a >>> > shopping cart for the registration system. >>> > Some features are made with plugins and/or are reusable outside the >>> > conference management system. >>> > >>> > If there is enough interest, we could improve and make it a general >>> CMS. >>> > Also, there are many companies and professionals that can be hired to >>> > develop such a project, or contributing to existing ones. >>> > A fundraising would be a good option to start this. >>> > >>> >>> BTW, measuring "community" is difficult. >>> >>> For example, django has a larger community here in Argentina, but >>> earlier web-conference projects like PyCon-Tech failed to gain such >>> traction anyway, and current alternatives are too complex IMHO and >>> needs highly experienced developers. >>> >>> I would also take into consideration maintainability (backward >>> compatibility, all-inclusive real full-stack features, compact code, >>> etc.) >>> Maybe you have to program a little more, but believe me, you will have >>> a better control of the situation, specially when you need to extend >>> or scale the app. >>> As someone told before, most of the features of a CMS are simple to >>> implement in web2py, maybe that's why there aren't many big and >>> complex projects. >>> >>> >>> I've made a blog post about this, telling the history of web2conf in >>> Argentina (in Spanish, sorry): >>> >>> >>> http://pyconar.blogspot.com.ar/2012/07/sitio-web-de-pycon-argentina-un-poco-de.html >>> >>> >>> In brief, I've made a mistake selecting PyCon-Tech in 2009 for our >>> first conference. >>> As it was built in django (and used by PyConUS), I thought it have >>> enough community to at least fix bugs and survive. >>> I was wrong. >>> The project literally died and we even lost the web sites (django >>> 0.96, unmaitained, eat up all of our server memory) >>> Hopefully, with web2py, we could resurrect our old websites and go >>> ahead the last two years. >>> >>> You can see it running here: >>> >>> http://ar.pycon.org/2012 >>> >>> Best regards, >>> >>> Mariano Reingart >>> http://www.sistemasagiles.com.ar >>> http://reingart.blogspot.com >>> >> --
