![Picture of someone moving blocks from one pile to another](/sites/default/files/styles/ca/public/2023-04/img-g75eyvuxo3nm0el6g6l3a4wt.png?itok=G3IY-sZf)
Deploying blocks and content to other site environments
If you have a current Drupal site (built in Drupal 8 or later) you no longer need to entirely rebuild your site -- ever again. That doesn't mean it couldn't use a freshening up now and then.
If you have a current Drupal site (built in Drupal 8 or later) you no longer need to entirely rebuild your site -- ever again. That doesn't mean it couldn't use a freshening up now and then.
When you build a new website, going live is relatively easy. You get ahold of a domain name, point it at a webhost, put the website code there, and you're up and running!
After a site is live, it gets a lot more complicated.
More and more I keep running into assertions that Git is a version control tool, and that if you use it for deployment, you're doing it wrong.
Why?
At Freelock we find it to be a very effective deployment tool, and I'm not seeing a solution that meets our needs any better.
Two presentations in particular caught my attention recently mentioned this:
Lately at Freelock, we've been improving our Drupal site assessment.
If there's one thing that's constant in the web world, it's change.