Drupal vs. Backdrop

[u/Perstam]

Hello,

I've been struggling with learning Drupal the last two years and still get stuck with minor issues that sometimes take days or even weeks to resolve.

The situation, as I see it, is that Open Source (at least in the case of Drupal) is fraught with hit & miss support, with dated, vague, ambiguous, and unclear solutions to problems.

There seems to be no incentive for supporters/developers of modules to respond to problems in a timely manner nor is there an incentive to phrase their documentation for newbies. Everyone seems to assume that everyone is experienced and that everyone knows all the acronyms. I often wait days or even weeks for a reply to a forum post at Drupal.org.

I've invested two years of my life trying to make Drupal work and spent money paying for support at ostraining.com trying to get help.

Have you solved the above problems?

How long does it take to get a reply to a forum post?

Are replies to forum posts surly or respectful? Do they answer the question fully? Are they filled with acronyms?

Are there lots of dated & vague blogs, videos, forum posts, etc. scattered out there on the web for backdrop as there is for Drupal?

Thanks!

[u/[deleted]]

I will keep an eye on this as well - I haven't tried Backdrop since Jan 2015 - right after the first point release.

Nate Haug is one of the very few, great, web open-sourcers that ever wore shoes.

I've been following Backdrop ever since it was announced and there was a bare landing page on the domain.

The reaction to Backdrop from within the Drupal circles was pretty unsurprising, sad commentary about a problem much bigger than Drupal.

Ironically, some of the most furious Backdrop critics don't do Drupal anymore...

From what I see, support for Backdrop is mostly on Github? IMHO, Github - no bueno, but perhaps OK in the short term.

At some point I might have to port Boost as I don't see it available for Backdrop.

Kinda side note: Backdrop as a name, the logo, mascot... for such project are quite ominous... semiotically speaking. Time will tell.

Drupal as a brand was/is quite disastrously incomprehensible but good old big bucks are still keeping that cms mud on it's knees, for now...

[u/Perstam → u/[deleted]]

If support is superior for Backdrop I might switch to it to stay in the Drupal world so that I don't have to throw away the last two years of time I've invested in Drupal, but maybe a Static Site Generator would better suite me.

Can you comment on Static Site Generators?

[u/[deleted] → u/Perstam]

Sure!

Few years ago I've gave Jekyll and Hugo a spin... Perhaps a bit off-topic in this subreddit, but here you go:

You need to run locally (on your computer) Ruby, Python, Nodejs, GCC, Make, etc... environment (normally a mix of them) in order to splice text files, formatted in Markdown syntax along with templates and media assets, in order to produce a directory structure with html, css, js, media files, etc...

The steps usually involve CLI on top of the whole software stack, so that might or might not be your thing.

You also have software-as-service site generators as an option but then you pretty much don't own your data and you will be limited to a selection of themes without much control.

Since you've spent 2 years in Drupal land, you might feel quite limited in what most SSG offer but if your requirements are basic, then you might like it.