4 ms·

Is this still a Terrible Tree of Widgets design?

acdha 11y ago
Beyond the documentation, they have a demo if you want to find out: https://control.aldryn.com/demo/get-new/ https://control.aldryn.com/demo/get-new/
- JustSomeNobody 11y ago
  "Sorry, we've temporarily run out of demo websites. Please try again soon! " Interesting wording.
  - DanieleProcida 11y ago
    https://twitter.com/djangocms/status/674982831320379392 https://twitter.com/djangocms/status/674982831320379392
  - intellectronica 11y ago
    That's the HN effect. Demo sites are "pre-deployed" to make sure you get a fresh individual site. Usually there are hundreds of them in the waiting but looks like we've got very popular all of a sudden :) If you'd like to give it a try and don't have patience to wait for a demo site to become available, you can also register to Aldryn [ http://www.aldryn.com/ http://www.aldryn.com/ ] (for free) and deploy your own site with a few clicks.
    - austinjp 11y ago
      Slight side-track, but I'd be interested in your "pre-deployment" process. Could you enlighten me, or point me somewhere I could find out? Thanks.
      - intellectronica 11y ago
        It works just like normal site deployment (prepare containers with the site code and a database, etc, push it to cloud servers) but unlikely customer sites that are controlled by, well, customers, the demo is always the same site, so instead of making users wait for a deploy to start and finish when they request a demo, we deploy a bunch of demo sites in the background and when the user asks for a demo they just get one of the pre-deployed sites (while in the background we start deploying a new one to add to the pool).
        austinjp 11y ago
        Many thanks. What automation tools do you use, and how have you found them? If you've already written about this I'm happy to be pointed elsewhere.
        deleted 11y ago
        [deleted]
deleted 11y ago
[deleted]
WimLeers 11y ago
What a great description! It perfectly describes my impression. Awful authoring experience for non-technical users. Which doesn't mean it's not excellent for certain use cases :)
- DanieleProcida 11y ago
  I'm betting you haven't actually used django CMS 3.2 - since this release is entirely about improving the user experience for non-technical editors!

acdha 11y ago

Beyond the documentation, they have a demo if you want to find out: https://control.aldryn.com/demo/get-new/ https://control.aldryn.com/demo/get-new/

JustSomeNobody 11y ago
"Sorry, we've temporarily run out of demo websites. Please try again soon! " Interesting wording.
- DanieleProcida 11y ago
  https://twitter.com/djangocms/status/674982831320379392 https://twitter.com/djangocms/status/674982831320379392
- intellectronica 11y ago
  That's the HN effect. Demo sites are "pre-deployed" to make sure you get a fresh individual site. Usually there are hundreds of them in the waiting but looks like we've got very popular all of a sudden :) If you'd like to give it a try and don't have patience to wait for a demo site to become available, you can also register to Aldryn [ http://www.aldryn.com/ http://www.aldryn.com/ ] (for free) and deploy your own site with a few clicks.
  - austinjp 11y ago
    Slight side-track, but I'd be interested in your "pre-deployment" process. Could you enlighten me, or point me somewhere I could find out? Thanks.
    - intellectronica 11y ago
      It works just like normal site deployment (prepare containers with the site code and a database, etc, push it to cloud servers) but unlikely customer sites that are controlled by, well, customers, the demo is always the same site, so instead of making users wait for a deploy to start and finish when they request a demo, we deploy a bunch of demo sites in the background and when the user asks for a demo they just get one of the pre-deployed sites (while in the background we start deploying a new one to add to the pool).
      - austinjp 11y ago
        Many thanks. What automation tools do you use, and how have you found them? If you've already written about this I'm happy to be pointed elsewhere.
      - deleted 11y ago
        [deleted]

deleted 11y ago

[deleted]

WimLeers 11y ago

What a great description! It perfectly describes my impression. Awful authoring experience for non-technical users. Which doesn't mean it's not excellent for certain use cases :)

DanieleProcida 11y ago
I'm betting you haven't actually used django CMS 3.2 - since this release is entirely about improving the user experience for non-technical editors!