Fixed other urls and tag 🚀

Author: chicio

_layouts/home.html

@@ -168,7 +168,7 @@ <h1>ID3TagEditor</h1>
                             </ul>
                             <a class="btn btn-default" href="https://github.com/chicio/ID3TagEditor"
                                target="_blank">Github repo</a>
-                            <a class="btn btn-default" href="/ID3TagEditor"
+                            <a class="btn btn-default" href="{{ site.url }}/ID3TagEditor"
                                target="_blank">Documentation</a>
                         </div>
                     </div>
@@ -253,7 +253,7 @@ <h1>RangeUISlider</h1>
 							</ul>
 							<a class="btn btn-default" href="https://github.com/chicio/RangeUISlider"
 							   target="_blank">Github repo</a>
-							<a class="btn btn-default" href="/RangeUISlider"
+							<a class="btn btn-default" href="{{ site.url }}/RangeUISlider"
 							   target="_blank">Documentation</a>
 						</div>
 						<div class="project-image-container col-12 col-lg-6 order-0 order-lg-1">

_posts/2017-11-14-react-native-realm-custom-manual-linking-app-custom-directories-ios.md

@@ -59,8 +59,7 @@ So we need to find another way to install the library.
 
 ![React Native realm link fails](/assets/images/posts/react-native-realm-2-link-fails.jpg "React Native realm directories")
 
-Usually, if the previous command fails, you have to do the [manual linking](https://facebook.github
-.io/react-native/docs/linking-libraries-ios.html "manual linking"). 
+Usually, if the previous command fails, you have to do the [manual linking](https://facebook.github.io/react-native/docs/linking-libraries-ios.html "manual linking"). 
 To do it we navigate inside the `node_modules` folder, contained in the React Native folder of our project, to found the realm folder. 
 Inside it you will find an Xcode project named `RealmReact`, that you have to drag into our project. After that we 
 have to add a reference to 

_posts/2018-03-02-code-review-whats-it-is-and-why-it-is-important.md

@@ -18,7 +18,7 @@ authors: [angelo_sciarra, fabrizio_duroni]
 In some of my previous posts (for example [in this one](/2017/09/11/clean-code-meaningful-names.html "clean code 
 meaningful names")), I talked about my new experience at [lastminute.com group](http://www.lastminutegroup.com 
 "lastminute.com group") and how much we care about code quality. In fact I already talked about the fact that we do 
-[pair programming during our daily job](2018/01/16/ide-refactoring-android-studio-xcode-appcode-webstorm-jetbrains.html "pair programming").
+[pair programming during our daily job](/2018/01/16/ide-refactoring-android-studio-xcode-appcode-webstorm-jetbrains.html "pair programming").
   But pair programming is not the only techniques we use to be sure that our software matches high 
   code quality standard :sunglasses:.  
   One of the most important procedure I use during my daily job with my colleagues is code review. What is it? Let's 
@@ -92,7 +92,7 @@ resolve/unmask multiple fields input.
 
 ![stateless object](/assets/images/posts/02-minesweeper-fields-as-parameter.jpg "stateless object")
 
-* The objects that are the building block of a [chain of responsability]("https://en.wikipedia.org/wiki/Chain-of-responsibility_pattern" "chain of responsability")   
+* The objects that are the building block of a [chain of responsability](https://en.wikipedia.org/wiki/Chain-of-responsibility_pattern "chain of responsability")   
 named `FieldRowParser` could become lighter and some of their responsibility could be assigned to some new 
 collaborators. Also the object that contains the parsing status could become more lighter.
 

_posts/2018-05-08-id3tageditor-swift-read-write-id3-tag-mp3.md

@@ -297,9 +297,7 @@ subclass of the `ID3FrameCreatorsChain` class is a specialization with the respo
     in other future posts :stuck_out_tongue_winking_eye: This framework contains too much cool swift stuff :flushed:)
     . One important thing to note: the `ID3AttachedPicturesFramesCreator` class is able to create attached picture 
     frames that sets the type of the cover to one from the list defined in the ID3 standard. In this way I can use my 
-    [ID3TagEditor framework to tag the mp3 with the correct data that I need to display the mp3 files cover on the 
-    media nav system of my clio](/blog/2018/05/25/born-id3tageditor-mp3id3tagger.html "born mo3id3tagger 
-    id3tageditor")!!! :relieved:
+    [ID3TagEditor framework to tag the mp3 with the correct data that I need to display the mp3 files cover on the media nav system of my clio](/2018/05/07/born-id3tageditor-mp3id3tagger.html "born mo3id3tagger id3tageditor")!!! :relieved:
 
 ```swift
 class ID3FrameCreatorsChainFactory {

_posts/2018-07-05-distribution-enterprise-app-ios-beta.md

@@ -17,7 +17,7 @@ authors: [giordano_tamburrelli, fabrizio_duroni]
 
 ---
 
-In a [previous post](/2018/05/07/react-native-typescript-exsisting-app.html "react native typescript") I talked about 
+In a [previous post](/2018/07/04/react-native-typescript-exsisting-app.html "react native typescript") I talked about 
 the "app relaunch" project I was involved in the last few months at [lastminute.com group](http://www.lastminutegroup.com/ "lastminute.com group"). 
 During one of the last sprint before the release we started to think about putting in place an internal beta testing 
 program to have more testing data and eventually discover more bugs before the release on the App Store (we really 

scripts/test.sh

@@ -7,4 +7,4 @@ npm run build
 npm run generate
 
 # Unit test website
-htmlproofer --http-status-ignore "999" ./_site 
+htmlproofer --http-status-ignore "999" ./_site --