librelist archives

« back to archive

Questions on CMS

Questions on CMS

From:
Jonathan Chen
Date:
2013-09-06 @ 08:08
Hey all,

My company and a few of us have been working on a CMS-like application
using flask and an assorted python tech. We've also been using a lot of
angularjs with our app that we've done some interesting stuff to make it
work with Flask. I am thinking of open-sourcing the application after we
remove some assets. But we have some issues if others would even use it.

There are a lot of CMS's out there that have different flavors or whatever,
but if nobody would think of using it then it would be pointless for us to
try to open source it. So I'm just reaching out to the community on what
kind of features would you like to have in a CMS that would make you want
to use it and deploy it for your own website. While brain storming with
some others I was thinking of trying to make the CMS as designer friendly
as possible. Where people don't need to spend a lot of effort to build a
model, but concentrate more on design and doing the look and feel of the
app.

What kind of features or paradigm would you guys/gals would like to see in
a CMS to make it something that you would want to use.

Worse case scenario is that we might split the different apps of the app
we've been using into separate flask-extensions.

~Jonathan C.

Re: [flask] Questions on CMS

From:
gioi
Date:
2013-09-06 @ 08:27
Ok Jonathan, thanks for your offer.
These are my requests:
- Extensibility: the whole point of rewriting a CMS is customization.
Your CMS should be designed to integrate well with non-CMS part of an app.
- Access Control: guess an integration with flask-principal will work.
- Innovative editing: I'd really like to see a CMS with inline editing
and cool effects like AJAX editing... Maybe integrating with
non-AngularJS applications.
Thank you!

Re: [flask] Questions on CMS

From:
Stefane Fermigier
Date:
2013-09-06 @ 08:41
Hi,

We're also working on CMS-like features for applications based on Flask. I
can't say if we would end up using your project wholesale, or some 
components of it, or just some bits, or just look at it for inspiration, 
but we would definitively welcome the move.

We're also specially interested in your ideas about integrating Flask with
AngularJS, since this is also on our roadmap and seems at this point still
an uncharted territory.

Regards,

  S.

On Sep 6, 2013, at 10:08 AM, Jonathan Chen wrote:

> Hey all,
> 
> My company and a few of us have been working on a CMS-like application 
using flask and an assorted python tech. We've also been using a lot of 
angularjs with our app that we've done some interesting stuff to make it 
work with Flask. I am thinking of open-sourcing the application after we 
remove some assets. But we have some issues if others would even use it.
> 
> There are a lot of CMS's out there that have different flavors or 
whatever, but if nobody would think of using it then it would be pointless
for us to try to open source it. So I'm just reaching out to the community
on what kind of features would you like to have in a CMS that would make 
you want to use it and deploy it for your own website. While brain 
storming with some others I was thinking of trying to make the CMS as 
designer friendly as possible. Where people don't need to spend a lot of 
effort to build a model, but concentrate more on design and doing the look
and feel of the app. 
> 
> What kind of features or paradigm would you guys/gals would like to see 
in a CMS to make it something that you would want to use.
> 
> Worse case scenario is that we might split the different apps of the app
we've been using into separate flask-extensions. 
> 
> ~Jonathan C.

-- 
Stefane Fermigier - http://fermigier.com/ - http://twitter.com/sfermigier 
- http://linkedin.com/in/sfermigier
Founder & CEO, Abilian - Enterprise Social Software - http://www.abilian.com/
Founder & Board Member, Nuxeo - Open Source ECM - http://www.nuxeo.com/
Co-Founder and Chairman, Free&OSS Cluster - http://www.gt-logiciel-libre.org/
Co-Founder & Vice-President, National Council for Free&OSS - http://cnll.fr/
Vice President, Open World Forum 2013 - http://openworldforum.org/
"Well done is better than well said." - Benjamin Franklin
"There's no such thing as can't. You always have a choice." - Ken Gor
"Le vrai courage, c'est de faire ce qui est juste." - Dr Benjamin Justice

Re: [flask] Questions on CMS

From:
Christopher Meng
Date:
2013-09-06 @ 08:19
Wow...That would be great as we will have another choice~

Hope it can support multiple databases.

Before more suggestions coming, I hope you can show us a demo.

Just my 2 cent. ;)

Re: [flask] Questions on CMS

From:
Jonathan Chen
Date:
2013-09-06 @ 08:24
Unfortunately, at this moment we won't be able to show a demo of it. It is
highly customized for our needs. Like LDAP authentication, etc. web
services, etc. But I would like to start to separate our customization to
help build some sort of standard around it.


~Jonathan C.


On Fri, Sep 6, 2013 at 1:19 AM, Christopher Meng <cickumqt@gmail.com> wrote:

> Wow...That would be great as we will have another choice~
>
> Hope it can support multiple databases.
>
> Before more suggestions coming, I hope you can show us a demo.
>
> Just my 2 cent. ;)
>

Re: [flask] Questions on CMS

From:
Jonathan Chen
Date:
2013-09-06 @ 08:25
Also, we use a lot of flask extensions like flask sqlalchemy and stuff like
that so it can support multiple databases.


~Jonathan C.


On Fri, Sep 6, 2013 at 1:19 AM, Christopher Meng <cickumqt@gmail.com> wrote:

> Wow...That would be great as we will have another choice~
>
> Hope it can support multiple databases.
>
> Before more suggestions coming, I hope you can show us a demo.
>
> Just my 2 cent. ;)
>

Re: [flask] Questions on CMS

From:
Bruno Rocha
Date:
2013-09-06 @ 10:05
I am working in a CMS using Flask and MongoDB

http://www.quokkaproject.org / http://github.com/pythonhub/quokka

It is in very beginning but it is already working for simple posts.

The main goal is to have a simple and flexible CMS based in channels ->
content structure, also take advantage of blueprints to create modules.

Any suggestion or contribution is very appreciated.

Bruno Rocha
http://github.com/rochacbruno
http://rochacbruno.com.br


On Fri, Sep 6, 2013 at 5:08 AM, Jonathan Chen <tamasiaina@gmail.com> wrote:

> Hey all,
>
> My company and a few of us have been working on a CMS-like application
> using flask and an assorted python tech. We've also been using a lot of
> angularjs with our app that we've done some interesting stuff to make it
> work with Flask. I am thinking of open-sourcing the application after we
> remove some assets. But we have some issues if others would even use it.
>
> There are a lot of CMS's out there that have different flavors or
> whatever, but if nobody would think of using it then it would be pointless
> for us to try to open source it. So I'm just reaching out to the community
> on what kind of features would you like to have in a CMS that would make
> you want to use it and deploy it for your own website. While brain storming
> with some others I was thinking of trying to make the CMS as designer
> friendly as possible. Where people don't need to spend a lot of effort to
> build a model, but concentrate more on design and doing the look and feel
> of the app.
>
> What kind of features or paradigm would you guys/gals would like to see in
> a CMS to make it something that you would want to use.
>
> Worse case scenario is that we might split the different apps of the app
> we've been using into separate flask-extensions.
>
> ~Jonathan C.
>

Re: [flask] Questions on CMS

From:
gioi
Date:
2013-09-06 @ 12:18
Il 06/09/2013 12:05, Bruno Rocha ha scritto:
> I am working in a CMS using Flask and MongoDB
Is there a reason why you chose MongoDB over a RDBMS or another
Document-oriented Database?

Re: [flask] Questions on CMS

From:
Bruno Rocha
Date:
2013-09-06 @ 13:16
On Fri, Sep 6, 2013 at 9:18 AM, gioi <g@gioi.tk> wrote:

> Is there a reason why you chose MongoDB over a RDBMS or another
> Document-oriented Database?
>

Hi,

I contributed to development of another CMS's with different frameworks,
the most relevant is Opps CMS[1] writen in Django + Relational Database,
this is a large project already on production for high traffic websites and
during the development of this CMS I learned a lot of things about content
management for content portals and magazines. Often I was really upset
because clients wanted to customize too many things on the CMS and it is
very difficult to maintain a set of different database schemas in a single
code base.

So I realized that the biggest "pain", what makes me feel really "sad" is
primarily "database migrations" and "database schemes" and "database
de-normalization for performance", a lot of database issues raised. (now it
is better because we switched to Postgres)

So because of that I decided to start a flexible project where the goal is
to minimize that issues, obviously I have now another issues like
map-reduce to deal, but it is different because with schema less document
based CMS you can customize the CMS for every instance without the need to
keep different code bases and also without the pain of migrations. i.e:
adding a new field is just adding a new form input if you use
DynamicDocument, no need to touch database schema.

That is the reason I choose Flask, because it plays well with Mongo, and
choose MongoDB because it is well established and the one I know how to
work with. (another reason is because of blueprints, it makes module
development very elegant)

Other people asked me why Quokka CMS[2] will not support relational
databases and the answer is that "Quokka goal is to be the happiest CMS in
the world. like a quokka" and no CMS is happy with database joins, schemes
and migrations. (the success of Plone in this area is because of the ZopeDB)

I like to work with relational databases for many kinds of applications,
like commerce, warehouse and some others where I need reports and
integration with legacy apps, but I realized that the document oriented
fits perfectly to store documents like Posts, Albums, Flat-pages, Comments,
Polls etc.

[1] http://github.com/opps
[2] http://www.quokkaproject.org

Re: [flask] Questions on CMS

From:
no thank you
Date:
2013-09-06 @ 14:52
Put me down for a second vote for inline editing.  That sounds great, and I
think that would make it easier for clients that are totally new to CMS to
adapt.  For CMS,  I've found that a focus on a "plugin" or "module" system
built into a really simple core application does wonders for clarity of
communication with a client.  If you start off with a system that just
handles pages and nav and are provided the ability to glom more
functionality on to that,   it cuts down on the amount of crap you have to
explain to a client about how you've solved their problem and how they can
interact with the system, occam's razor style.


On Fri, Sep 6, 2013 at 8:16 AM, Bruno Rocha <rochacbruno@gmail.com> wrote:

>
> On Fri, Sep 6, 2013 at 9:18 AM, gioi <g@gioi.tk> wrote:
>
>> Is there a reason why you chose MongoDB over a RDBMS or another
>> Document-oriented Database?
>>
>
> Hi,
>
> I contributed to development of another CMS's with different frameworks,
> the most relevant is Opps CMS[1] writen in Django + Relational Database,
> this is a large project already on production for high traffic websites and
> during the development of this CMS I learned a lot of things about content
> management for content portals and magazines. Often I was really upset
> because clients wanted to customize too many things on the CMS and it is
> very difficult to maintain a set of different database schemas in a single
> code base.
>
> So I realized that the biggest "pain", what makes me feel really "sad" is
> primarily "database migrations" and "database schemes" and "database
> de-normalization for performance", a lot of database issues raised. (now it
> is better because we switched to Postgres)
>
> So because of that I decided to start a flexible project where the goal is
> to minimize that issues, obviously I have now another issues like
> map-reduce to deal, but it is different because with schema less document
> based CMS you can customize the CMS for every instance without the need to
> keep different code bases and also without the pain of migrations. i.e:
> adding a new field is just adding a new form input if you use
> DynamicDocument, no need to touch database schema.
>
> That is the reason I choose Flask, because it plays well with Mongo, and
> choose MongoDB because it is well established and the one I know how to
> work with. (another reason is because of blueprints, it makes module
> development very elegant)
>
> Other people asked me why Quokka CMS[2] will not support relational
> databases and the answer is that "Quokka goal is to be the happiest CMS in
> the world. like a quokka" and no CMS is happy with database joins, schemes
> and migrations. (the success of Plone in this area is because of the ZopeDB)
>
> I like to work with relational databases for many kinds of applications,
> like commerce, warehouse and some others where I need reports and
> integration with legacy apps, but I realized that the document oriented
> fits perfectly to store documents like Posts, Albums, Flat-pages, Comments,
> Polls etc.
>
> [1] http://github.com/opps
> [2] http://www.quokkaproject.org
>
>
>
>
>

Re: [flask] Questions on CMS

From:
Jonathan Chen
Date:
2013-09-06 @ 14:56
Thanks for the input. It will probably be some time before we publish the
stuff, but I'll make note of it. I think what I'll plan on doing though is
to release some stuff around what we have been using. I am thinking of
spinning off a flask-ldap extension and maybe a flask-sso??? Though, I
would need help with this one.

One goal I was thinking though is to be able to make custom objects. For
instance, I can through the web UI make a custom class, and when I design
the UI I can make calls to that custom class to retrieve content or
whatever. I will think about inline editing. I'm not a fan of inline
editing because you can lose some functionality, but I'll think about how
to do it well.


~Jonathan C.


On Fri, Sep 6, 2013 at 7:52 AM, no thank you <oneofy@gmail.com> wrote:

> Put me down for a second vote for inline editing.  That sounds great, and
> I think that would make it easier for clients that are totally new to CMS
> to adapt.  For CMS,  I've found that a focus on a "plugin" or "module"
> system built into a really simple core application does wonders for clarity
> of communication with a client.  If you start off with a system that just
> handles pages and nav and are provided the ability to glom more
> functionality on to that,   it cuts down on the amount of crap you have to
> explain to a client about how you've solved their problem and how they can
> interact with the system, occam's razor style.
>
>
> On Fri, Sep 6, 2013 at 8:16 AM, Bruno Rocha <rochacbruno@gmail.com> wrote:
>
>>
>> On Fri, Sep 6, 2013 at 9:18 AM, gioi <g@gioi.tk> wrote:
>>
>>> Is there a reason why you chose MongoDB over a RDBMS or another
>>> Document-oriented Database?
>>>
>>
>> Hi,
>>
>> I contributed to development of another CMS's with different frameworks,
>> the most relevant is Opps CMS[1] writen in Django + Relational Database,
>> this is a large project already on production for high traffic websites and
>> during the development of this CMS I learned a lot of things about content
>> management for content portals and magazines. Often I was really upset
>> because clients wanted to customize too many things on the CMS and it is
>> very difficult to maintain a set of different database schemas in a single
>> code base.
>>
>> So I realized that the biggest "pain", what makes me feel really "sad" is
>> primarily "database migrations" and "database schemes" and "database
>> de-normalization for performance", a lot of database issues raised. (now it
>> is better because we switched to Postgres)
>>
>> So because of that I decided to start a flexible project where the goal
>> is to minimize that issues, obviously I have now another issues like
>> map-reduce to deal, but it is different because with schema less document
>> based CMS you can customize the CMS for every instance without the need to
>> keep different code bases and also without the pain of migrations. i.e:
>> adding a new field is just adding a new form input if you use
>> DynamicDocument, no need to touch database schema.
>>
>> That is the reason I choose Flask, because it plays well with Mongo, and
>> choose MongoDB because it is well established and the one I know how to
>> work with. (another reason is because of blueprints, it makes module
>> development very elegant)
>>
>> Other people asked me why Quokka CMS[2] will not support relational
>> databases and the answer is that "Quokka goal is to be the happiest CMS in
>> the world. like a quokka" and no CMS is happy with database joins, schemes
>> and migrations. (the success of Plone in this area is because of the ZopeDB)
>>
>> I like to work with relational databases for many kinds of applications,
>> like commerce, warehouse and some others where I need reports and
>> integration with legacy apps, but I realized that the document oriented
>> fits perfectly to store documents like Posts, Albums, Flat-pages, Comments,
>> Polls etc.
>>
>> [1] http://github.com/opps
>> [2] http://www.quokkaproject.org
>>
>>
>>
>>
>>
>

Re: [flask] Questions on CMS

From:
bibek chitrakar
Date:
2013-09-06 @ 12:41
I am also developing a Application which requires certain administration
section and user interface much like Joomla interface but very customizable
and generic features. It would be great if we could create a Flask CMS.
Much appreciation !!



On Fri, Sep 6, 2013 at 6:03 PM, gioi <g@gioi.tk> wrote:

> Il 06/09/2013 12:05, Bruno Rocha ha scritto:
> > I am working in a CMS using Flask and MongoDB
> Is there a reason why you chose MongoDB over a RDBMS or another
> Document-oriented Database?
>
>


-- 
Regards,
Bibek Chitrakar