@b1ueh4wk
I'm working on a fork though it might not be ready soon but I think Drupal community need more solutions alongside Opigno. as I stated before I don't like some features of Opigno and think it is bloated in some ways and is not completely modular unless you go very deep inside its configurations. for example you can not easily remove or disable some modules you don't need.
I wanted to build a simple e-learning website (like udemy) in Drupal and came across to Opigno. It seems Drupal does not have a simple solution for such websites. course module is limited in functionality and if you want a very simple website to sell online courses you have to go for a DIY approach with group module and integrate it with commerce license module.
So, now I am doing my best to create a very modular solution. The negative part is that it may not be fully compatible with Opigno for migration.
I am also completely support a fork and am ready to help
the problem I have with Opigno is not just about timely releases. It comes with a lot of bloat.
UPDATE:
it seems I made a mistake in updating both modules. I tried composer require 'drupal/splide:^1.0@RC' but strangely it did not update. I used exact version number and I did updated.
Now there is no problem and everything works very well. Thank you @gausarts!
@gausarts
Yes, I checked both stable versions and latest RCs
this error is what I get with latest RC Splide and Blazy 2.17-rc4:
Warning: Undefined array key "settings" in Drupal\splide\Plugin\Field\FieldFormatter\SplideEntityReferenceFormatterBase->buildElement() (line 21 of modules/contrib/splide/src/Plugin/Field/FieldFormatter/SplideVanillaWithNavTrait.php).
And this is what I get from latest stable Slick and Blazy 2.17-rc4:
Fatal error: Cannot make non static method Drupal\blazy\Plugin\Filter\TextFilterBase::getValidNode() static in class Drupal\slick\Plugin\Filter\SlickFilter in /app/web/modules/contrib/slick/src/Plugin/Filter/SlickFilter.php on line 498
I've attached complete splide error log
@gausarts
Thank you. Yes the problem fixed and the latest rc version is much better. BUT when I updated Blazy to latest rc version I get two errors regarding Slick and Splide. I don't know whrere to report those bugs because I don't know this is causes by Blazy or those modules.
I am also very interested. the problem I have with Layout Builder is that it is not stored as configuration and pages you make have arbitrary real paths. you can set an alias path but drupal will pick up the real node path which is very problematic in transferring configuration from development environment to production.
@andypost
I don't think so. the problem with layout builder is that it is saved in the form of content an also the pages you create with layour builder are most likely NODES and they don't have fixed and absolute paths.
this is mostly problematic when you want to transfer configuration from your development environment to production. I did not used page manager module so much but I think that is the real solution but it is very complex