(CSS) / (TXT) / (MKD) - Remove unusued styles and add content.

Author: davidjguru

_includes/spotifyplaylist.html

@@ -14,18 +14,23 @@ youtubeId: bYA81QfWSsw
 | :-------------------------------------------------------------------------------------------------------------------: |
 |              *Picture from Unsplash, user [Markus Winkler, @markuswinkler](https://unsplash.com/@markuswinkler)*  
 
-Now in my current context I'm working on a multisite Drupal installation with several internal sites (more than a hundred sites) and among other experiences, I'm facing new issues that I had not experienced before. This little post is about that: a very specific error that can be common and how to solve it.
+Now in my current context I'm working on a multisite Drupal installation with several internal sites (more than a hundred sites) and among other experiences, I'm facing new issues that I had not experienced before. This little post is about that: a very specific error that can be common and how to solve it.  
 <!--more-->
 
-Well, now I'm working in a different stack from what I'm used to: I'm using [Docksal](https://docksal.io/), a software virtualization tool for containers, and [Acquia BLT](https://github.com/acquia/blt) (or Acquia Build and Launch Tool), a resource for automatization of tasks, deploys and testing. The combination of both allows to build Docker container networks in your local environment and to have pre-configured different tasks for the daily management of a Drupal-based websites. I recommend you to try them, although for containers I prefer [DDEV](https://ddev.readthedocs.io/en/stable/), that's true, but I think that experiencing a containerization tool (Docksal, DDEV, [Docker4Drupal](https://github.com/wodby/docker4drupal), [Gitpod](https://github.com/shaal/ddev-gitpod)...) and a maintenance and development task management tool (Acquia BLT, [Robo](https://robo.li/) / [Drobo](https://github.com/Ymbra/Drobo), [Deployer](https://deployer.org/docs/7.x/recipe/drupal8) is a MUST for any Drupal developer.  
 
-**Acknowledgments**
------------------------  
-This post was composed from my current position as Senior Drupal Developer at [FFW Agency](https://ffwagency.com/), one of the biggest companies oriented to Open Source in the world and specifically focused in Drupal.   
+Well, now I'm working in a different stack from what I'm used to: I'm using [Docksal](https://docksal.io/), a software virtualization tool for containers and [Acquia BLT](https://github.com/acquia/blt) (or Acquia Build and Launch Tool), a resource for automatization of tasks, deploys and testing. The combination of both allows to build Docker container networks in your local environment and to have pre-configured different tasks for the daily management of Drupal-based websites.   
 
+I recommend you to try them, although for containers I prefer [DDEV](https://ddev.readthedocs.io/en/stable/) -that's true- but I think that experiencing a containerization tool (Docksal, DDEV, [Docker4Drupal](https://github.com/wodby/docker4drupal), [Gitpod](https://github.com/shaal/ddev-gitpod)...) and a maintenance and development task management tool (Acquia BLT, [Robo](https://robo.li/) / [Drobo](https://github.com/Ymbra/Drobo), [Deployer](https://deployer.org/docs/7.x/recipe/drupal8) is a MUST for any Drupal developer.  
 
 
-## The Issue  
+
+## Acknowledgments  
+
+This post was composed from my current position as Senior Drupal Developer at [FFW Agency](https://ffwagency.com/), one of the biggest companies oriented to Open Source in the world and specifically focused in Drupal.    
+
+
+
+## The Issue   
 
 When I want to build up the frontend of a site, I execute a combined Docksal + BLT instruction, something like using the classical @alias/naming of a site:  
 
@@ -48,6 +53,22 @@ And then the process is stopped and it is not possible to build the frontend of
 | :-------------------------------------------------------------------------------------------------------------------:        |
 |              *Python2 error while we're building up the frontend*                                           |
 
+
+So what I do is first of all, check the version numbers of each element involved in the Issue, using command line for the first items and then reviewing `package.json` file and getting some versions, or by using `yarn` with subcommands just like:  
+
+```
+$ yarn list --pattern "node-sass"
+```
+
+And so I get all the values I am interested in, since I will have to google the status of each one, looking for issues, known bugs or deprecated code ;-) :      
+
+```
+node -v: v16.16.0
+npm -v: 8.11.0
+node-sass:  4.14.1
+node-gyp: 3.8.0
+```
+
 ## Fixin'  
 
 Ok, let's try to get a good understanding of what is happening throughout this process since we execute the frontend startup commands. As I said, when I'm running my current configuration in CLI, mixin' docksal commands + Acquia tooling, I'm trying to run the build up for theming by usings something like this:
@@ -68,7 +89,7 @@ So finally, when you (or your scripts) launch `yarn run build:sass`  finally you
 ```
 node-sass src/_patterns -o src/_patterns --include-path ./node_modules/breakpoint-sass/stylesheets
 ```
-Just in order to transpiling the CSS files in theming from SCSS syntax to processed CSS, marking source, destiny folder (`-o /folder/`) and other resources to integrate in the process (`--include-path`) as usual.    
+Just in order to transpiling the CSS files in theming from SCSS syntax to processed CSS, marking source, the destiny folder (`-o /folder/`) and other resources to integrate in the process (`--include-path`) as usual.    
 
 Ok, **What's the problem?** Well, the first key here: `node-sass`. I've discovered the dependency is marked as deprecated from more than two years ago (nothing interesting from my side, just the magic of the hyperlink and a little of Google)... It causes problems and errors because nodejs compatibility with the current version of `node-sass` installed. [You can see the current status of `node-sass` here](https://www.npmjs.com/package/node-sass) or [in tickets from some Drupal distributions like Varbase](https://www.drupal.org/project/varbase/issues/3271850). This issue has been detected by me at least in a pair of themes of my current multisite structure, think about theme_one and theme_two. So, we'll need a new resource instead the deprecated `node-sass`. Ok, but, **what's the solution?**  
 

_posts/2022-09-16-tooling-python2-error-in-sass-building-frontend.md

@@ -7,7 +7,6 @@
 
 @import "reset";
 @import "variables";
-@import "spotify-embed";
 // Syntax highlighting @import is at the bottom of this file
 
 /**************/