I wrote a blog post that reflects my own thoughts on how I personally view Backdrop CMS as part of the larger community and a service to those being left behind by Drupal 9+.
I like Drupal 9 in some situations and for some client and still consider myself part of the Drupal community. I wish there were some way for the Drupal community to acknowledge that Backdrop CMS might meet the needs of some Drupal 7 users and that adopting Backdrop CMS is not abandoning Drupal, it's just a small fork in the road.
Backdrop CMS - Providing a Soft Landing for Drupal 7 Sites
I'd love feedback.
Recent comments
Thanks for explaining @herb I was actually thinking along the same lines and have created a simple module that gives the 'view any content_type content' permission and restricts just by checking the...
Disable hidden path message on particular content type
We now have a working version of Organic Groups. https://backdropcms.org/project/og
organic groups or "group module"?
@argiepiano I was referring to the main goal of restricting access to a content type. I was thinking that if the solution is to write a custom module there's a more direct way to implement access...
Disable hidden path message on particular content type
To add to @argiepiano's point; I've been following the discussion in #5634 on possible/probable performance impacts of content access modules : https://github.com/backdrop/backdrop-issues/issues/...
Disable hidden path message on particular content type
Seems to be an awkward ways to avoid using a content access module :). I don't follow. This doesn't in any way restrict or grant access. It simply removes an info message.
Disable hidden path message on particular content type