Fork me on GitHub

PN -> Zikula & Accessibility  Bottom

  • Here's maybe an easy question...

    I have been a PN user for both corp/clients, as well as personally for years, but have been out of Web dev/CMS world for a couple years... and guess what--my favorite open source CMS, which also happened to be the most accessible CMS tool I've ever encountered is dead.

    Of course, this was PN...

    So, as I bring a few more corporations onboard with CMS, I really must find a replacement CMS, and accessibility is a CRITICAL concern, if not THE most important one. In PN, I recall MarkWest (as well as HammerHead [Simon?]) were the accessibility champions in the PN world. Where have they gone (which CMS)?

    IS Zikula at least as accessibility-minded as PN was?

    I have used the demo extensively, and am going to implement a Zikula distro in our lab to test with JAWS and WindowEyes (as well as run through the code for compliance manually and with automated tools). But I thought I'd ask before I dive in too much farther.

    - Dan
  • For all intensive purposes, Zikula is PostNuke 0.8. So while the PostNuke name died, the code did not -- it was improved and streamlined. Unless I am not understanding something about your post, the theme is where most/all your concerns of accessibility would be addressed, so it would be highly dependent on that anyway.
  • This is what I suspected, especially after using the demo. Though I've found that many people in this community seem to be trying hard to distinguish Zikula from PN, and even seem to leave the impression that it's a complete core code-level re-write from the ground up...

    Though, as I use the demo, and look at the HTML code produced (with various standard themes) it would seem to be the same--in fact, so much is still prefixed with "PN..." that it gave me a lot of hope. I'm glad to find (and hear) this, and I'm pretty sure I won't be jumping ship. Though I understand some of the anxiety of others I'm reading from who worry about big shifts in core and community in the future--you just tend to be gun-shy when this happens.
  • Yes, I totally understand. If a person wasn't here when the transition was made -- with a little overlap before and after -- it might make one wonder what really happened. Basically, the name change gave the team a great reason to improve the code and get rid of some of the crap that made it so bloated. In the process, it seems to be more secure and much easier for module developers to develop modules. So I think you'll find that overall you'll be happy with Zikula.

    Keep in mind, however, that many older modules have been left behind, but it's mainly because they were abandoned anyway and so you can't expect them to be compatible forever. When you do legitimately need an older module, though, take a look at the Module module's settings, as you can activate legacy support that will sometimes work (depending on how old the module is and how it was coded).

    I have played around with many (if not all) CMS and nothing comes even remotely close to Zikula for power and security. Yes, some may be more user-friendly right off the bat, but there are sacrifices made for that, whereas Zikula retains the ability to be very highly customized without changing any core code. I think if you spend some time with Zikula and compare it to the last version of PN you used, you'll be pleasantly surprised.
  • I am not a PRO at all, but rather an enthusiastic learner and after reading through this post... WELL DONE Ziruka!

    It gives me the confidence to have made the right move to a CMS project, where PRPs are real PROs and take care of certain core aspects rather than trying to enhance a facade, like so many others icon_rolleyes

    Best regards to all the developers, contributors and members.
  • Z I L U L A, of course! icon_confused
  • Welcome (back)!

    We're glad you are here. Looking forward to helping you in any way I can.

This list is based on users active over the last 60 minutes.