search

rochacbruno-archive / quokka_ng

:hamster: WIP - QuokkaCMS New Generation - Refactor from scratch using TinyDB
Other
73 stars 19 forks source link

My 2 cents #2

Closed QiXuanWang closed 6 years ago

QiXuanWang commented 7 years ago

I was an early follower when I want to try some light-weight cms framework. And quokka was a perfect match since at that time I was trying to learn mongodb and flask. I tried to setup a few testing sites but honestly didn't use it at production. The major concern:

  1. When I started to use quokka, I really wanted to understand it in detail. I tried but when get deeper, I feel it's still very complex. So I liked your new motivation to keep it simple and support through plugins.
  2. The CMS admin panel is too complex when you have a simple task and too simple when you really want to do something fancy.
  3. If possible, please publish some kind of architecture structure for your new project, (something like sqlalchemy did), so others would follow you easily. And by support features through plugins could help on this so as to attract more potential contributor that doesn't know everything as you.
  4. Is it possible you could make some built-in comment system or use some fancier external one? Current discus forum feel cumbersome for me. But it's my own feeling, maybe others don't think so.
  5. I'm still confused about the "CMS" title. How do you compare it with Django or else?

Will add more if I have other comment. But, great work and keep going!

rochacbruno commented 7 years ago

@QiXuanWang thanks for sharing I will take your opinion in consideration, thanks so much!

Now my goal is to make it really simple, I learned a lot about Content Management developing two widely used CMSs (opps and quokka) and I figured out that there are some important things to focus.

1) define the target (I think quokka target is developers and/or I.T people) 2) keep it simple (my plan is to make it very lean) 3) do not depend on database (but have it optionally) in this new generation quokka will not depend on external dependency 4) generate static web site (quokka will use jinja and pelican templates to deliver a static site optionally) 5) really simple admin (now it will have few options in admin)

Thanks for sharing and following, I'll update information here soon.

QiXuanWang commented 7 years ago

Just come up with some other feature thoughts:

  1. Search according to category. This requires to upload document/pictures with feature label. I don't remember if it's already supported or not. But it would be helpful.
  2. Is it possible to add some more default themes while not blog like? I know it's lazy request but just curious. For content management. I may want to browse things in category by default.
rochacbruno commented 7 years ago

@QiXuanWang https://github.com/rochacbruno/quokka_ng#setup-a-contributor-environment

rochacbruno commented 6 years ago

This issue was moved to rochacbruno/quokka#555