Merge pull request #14 from dlang/fix-402

Link to SDL doc page from JSON doc page broken

Author: wilzbach

netlify.sh

@@ -34,6 +34,9 @@ mv "127.0.0.1:8005" ${BUILD_DIR}
 find out -name "logo" | xargs -I {} mv {} {}.svg
 sed 's/src="\([^"]*\)\/logo"/src="\1\/logo.svg"/'  -i $(find out -name "*.html")
 
+# Replace all local links with dub.pm
+sed 's/http:\/\/127.0.0.1:8005/https:\/\/dub.pm/'  -i $(find out -name "*.html")
+
 kill -9 $PID_DOCS || true
 
 # Final cleanup (in case something was missed)

views/package_format_json.dt

@@ -9,7 +9,7 @@ block body
 	h2 Introduction
 
 	p
-		strong NOTE: this describes the JSON version of the package file format. See also the <a href="package-format?lang=sdl">specification based on SDLang</a>.
+		strong NOTE: this describes the JSON version of the package file format. See also the <a href="package-format-sdl">specification based on SDLang</a>.
 
 	p Every DUB package <em>should</em> contain a <code>dub.json</code> (or <code>dub.sdl</code>, formerly also <code>package.json</code>) file in its root folder. This file contains meta-information about the project and its dependencies. This information is used for building the project and for deploying it using the registry. The following sections give an overview of the recognized settings and their meaning. Note that any unknown settings are ignored for backwards compatibility reasons.
 
@@ -398,7 +398,7 @@ block body
 		li Require a version range: <code>"&gt;=1.3.0 &lt;=1.3.4"</code>
 		li Match any released version (equivalent to <code>"&gt;=0.0.0"</code>): <code>"*"</code>
 		li Use a GIT branch (deprecated): <code>"~master"</code>
-	
+
 	p Numbered versions are formatted and compared according to the <a href="http://semver.org/">SemVer specification</a>. The recommended way to specify versions is using the <code>~&gt;</code> operator as a way to balance between flexible upgrades and reducing the risk of code breakage.
 
 	p Whenever you refer to (sub) packages within the same repository, use the "any version" version specifier: <code>"*"</code>

views/package_format_sdl.dt

@@ -9,7 +9,7 @@ block body
 	h2 Introduction
 
 	p
-		strong NOTE: this describes the SDLang version of the package file format. See also the <a href="package-format?lang=json">specification based on JSON</a>.
+		strong NOTE: this describes the SDLang version of the package file format. See also the <a href="package-format-json">specification based on JSON</a>.
 
 	p Every DUB package <em>should</em> contain a <code>dub.sdl</code> (or <code>dub.json</code>) file in its root folder. This file contains meta-information about the project and its dependencies. This information is used for building the project and for deploying it using the registry. The following sections give an overview of the recognized settings and their meaning. Note that any unknown settings are ignored for backwards compatibility reasons.
 
@@ -382,7 +382,7 @@ block body
 		li Require a version range: <code>"&gt;=1.3.0 &lt;=1.3.4"</code>
 		li Match any released version (equivalent to <code>"&gt;=0.0.0"</code>): <code>"*"</code>
 		li Use a GIT branch (deprecated): <code>"~master"</code>
-	
+
 	p Numbered versions are formatted and compared according to the <a href="http://semver.org/">SemVer specification</a>. The recommended way to specify versions is using the <code>~&gt;</code> operator as a way to balance between flexible upgrades and reducing the risk of code breakage.
 
 	p Whenever you refer to (sub) packages within the same repository, use the "any version" version specifier: <code>"*"</code>