It seems potentially useful to allow install profiles to be run, not only at site creation, but also at any point afterwards. That would make them useful for publishing "recipes" which would mostly involve the creation of site building items such as content types, views, and fields. However, they could also be used to install contrib modules, themes, and layouts where necessary.
This would allow users to use a install profile even after they have installed backdrop and otherwise started building their sites. And it would allow them to run more than one install profile, each of which would provide a different set of functionality.
Recent comments
Hello. I'm stuck at the Drupal > Backdrop update step at /core/updatte.php with an error: The configuration directory in settings.php is specified as './files/config/active', but this...
Configuration directory "empty or missing crucial files" after site copy
Tried and successfully applied DrAlbany's method with the form https://www.drupal.org/sandbox/grobot/2105379stickman hook. I also encountered the same situation. Thanks DrAlbany
Ubercart - Auto increment SKU
Since before migration you need to prepare the Drupal site - disabling and removing all modules, disabling themes, as part of the preparation you can clear the cache and logs, delete the search...
Trimming the size of my database for D2B_migrate not to error out (Request Entity Too Large / 504 Gateway Time-out)