It's actually intended to be about moving in the opposite direction. I want people to be comfortable experimenting with Backdrop without having to be worried about being locked in, so I want to make sure they know there's a way out if they need it.
I'd like to have the same thing for Wordpress! But it's easier to figure out the conversion to Drupal, since we can piggyback on the extensive work done on D7-D8 migrations.
Irina has the right vision; I'll update the project description now. The session is intended to explore the options for migrating a complete Backdrop site TO Drupal 8/9. The goal is to give newcomers to Backdrop confidence that they have an exit path if they decide they want to leave, so that they feel more comfortable trying Backdrop in the first place.
I thought that this session is about an option to move from Backdrop to Drupal 9/10 in the future using same tools that are used for D7 to Drupal 9/10. That is something that we offered to our customer. If they know that they can go back to brand name (Drupal) from the new system (Backdrop) if things do not work for them for any reason made decision to try new system less stressful.
I tested standard Drupal 9 upgrade flow from page /upgrade/credentials with backdrop db credentials and got the following response. It would be great if this db would be recognized by D9.
Is this session about migrations (moving data from one D7 site to a second B site) or upgrades (taking a D7 site and converting it to a Backdrop site)?
If it's both, can we change the session title to something like "Switching from Drupal to Backdrop"?
Excellent. I look forward to learning more about the Tour module.
I think I'll plan on demonstrating the User Time Zone Tokens module. We are using it here on the Backdrop LIVE site.
https://backdropcms.org/project/utz_tokens
I'd like to demo the Tour module concept, which is newly developed by me and still unreleased.
It's actually intended to be about moving in the opposite direction. I want people to be comfortable experimenting with Backdrop without having to be worried about being locked in, so I want to make sure they know there's a way out if they need it.
I'd like to have the same thing for Wordpress! But it's easier to figure out the conversion to Drupal, since we can piggyback on the extensive work done on D7-D8 migrations.
Irina has the right vision; I'll update the project description now. The session is intended to explore the options for migrating a complete Backdrop site TO Drupal 8/9. The goal is to give newcomers to Backdrop confidence that they have an exit path if they decide they want to leave, so that they feel more comfortable trying Backdrop in the first place.
I thought that this session is about an option to move from Backdrop to Drupal 9/10 in the future using same tools that are used for D7 to Drupal 9/10. That is something that we offered to our customer. If they know that they can go back to brand name (Drupal) from the new system (Backdrop) if things do not work for them for any reason made decision to try new system less stressful.
I tested standard Drupal 9 upgrade flow from page /upgrade/credentials with backdrop db credentials and got the following response. It would be great if this db would be recognized by D9.
Here is a forum topic on this subject, which might be helpful to get the discussion started.
https://forum.backdropcms.org/forum/e-commerce-solutions-backdropcms
I would love to see boostrap5 lite in core - will make sites much easier to customize for many potential users.
Is this session about migrations (moving data from one D7 site to a second B site) or upgrades (taking a D7 site and converting it to a Backdrop site)?
If it's both, can we change the session title to something like "Switching from Drupal to Backdrop"?