Links: Remove http scheme from project cgit and wiki URLs.

7 files changed, 54 insertions, 54 deletions

diff --git a/developers/contribute.html b/developers/contribute.html
index 40e2b34..43b4cf1 100644
--- a/developers/contribute.html
+++ b/developers/contribute.html
@@ -38,8 +38,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
diff --git a/developers/gsoc/2008ideas.html b/developers/gsoc/2008ideas.html
index c7c0a9a..d888bb6 100644
--- a/developers/gsoc/2008ideas.html
+++ b/developers/gsoc/2008ideas.html
@@ -37,8 +37,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -63,9 +63,9 @@
 <ul>
 <li>Join our IRC channel <code>#netsurf</code> on <a href="http://freenode.net/">Freenode</a> and introduce yourself. Also, subscribe to the <a href="http://www.netsurf-browser.org/lists/netsurf-dev">developer mailing list</a>.</li>
 <li>Have access to a computer with supported OS (RISC OS, Linux, FreeBSD, etc) or an OS relevant for the project you want to apply for (Windows, Mac OS).</li>
-<li>Get up to speed with <a href="http://wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>.</li>
+<li>Get up to speed with <a href="//wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>.</li>
 <li><a href="http://www.netsurf-browser.org/documentation/develop#Compiling">Build NetSurf</a> and enjoy using it. (Ask if you need help.)</li>
-<li>Get familiarised with the source code &ndash; read the <a href="http://git.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
+<li>Get familiarised with the source code &ndash; read the <a href="//git.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
 </ul>
 <dd>
 <dt>When applying for a project<dt>
@@ -79,7 +79,7 @@
 <dd>
 <ul>
 <li>Most of NetSurf team communication happens via #netsurf IRC during evenings and nights (<a href="http://en.wikipedia.org/wiki/Central_European_Time">CET</a>). We expect you to join in on a regular basis for help, discussions and project updates. Note that you're not restricted to speaking to your assigned mentor; the whole development team are willing to help wherever they can.</li>
-<li>When improving NetSurf's layout engine, be able to create <a href="http://source.netsurf-browser.org/trunk/netsurftest/">test cases</a> and verify that existing test cases don't get broken.</li>
+<li>When improving NetSurf's layout engine, be able to create <a href="//source.netsurf-browser.org/trunk/netsurftest/">test cases</a> and verify that existing test cases don't get broken.</li>
 <li>Keep NetSurf's <a href="http://www.netsurf-browser.org/about/#ProjectGoals">project goals</a> in mind, especially the first point.</li>
 </ul>
 </dd>
@@ -105,33 +105,33 @@
  <li>Focus upon and fix the limitations in the current CSS engine</li>
  <li>Develop an entirely new CSS engine to replace the existing one</li>
 </ul>
-<p>There is an outline description of a <a href="http://git.netsurf-browser.org/netsurf.git/tree/docs/ideas/css-engine.txt">new CSS engine</a>, which may be of interest to those who want to take the second approach to this project. This description is fairly complete from an external API perspective. The implementation details of a new engine are completely negotiable &ndash; we have some idea of what's needed, but the student's input will be highly valued.</p>
+<p>There is an outline description of a <a href="//git.netsurf-browser.org/netsurf.git/tree/docs/ideas/css-engine.txt">new CSS engine</a>, which may be of interest to those who want to take the second approach to this project. This description is fairly complete from an external API perspective. The implementation details of a new engine are completely negotiable &ndash; we have some idea of what's needed, but the student's input will be highly valued.</p>
 <p>Regardless of which approach is taken, we would expect that testing of the code is performed on a regular basis to ensure that things are still working as expected. New testcases should be written to exercise existing bugs and test out new functionality.</p>
 </div>
 <p><strong>Skills required:</strong> C, CSS, parsing</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/netsurf.git/tree/content/handlers/css">CSS parser and modules</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/netsurf.git/tree/content/handlers/css">CSS parser and modules</a></p>
 <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21/">CSS 2.1 specification</a> <a href="http://www.w3.org/TR/DOM-Level-2-Style/">DOM Level 2 Style specification</a></p>
 
 <h2>Native Windows or Mac OS X ports</h2>
 <p>NetSurf currently has user-interface layers for the RISC OS Window Manager and for GTK (on Linux, FreeBSD, etc.). The GTK interface works on Windows or Mac OS X, but a native interface for these systems would give a better experience.</p>
 <p><strong>Skills required:</strong> C, Windows UI development or Mac OS X UI development</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/gui.h?view=markup">Declarations of functions that each interface must implement</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/gui.h?view=markup">Declarations of functions that each interface must implement</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Keyboard navigation</h2>
 <p>The browser currently requires a mouse to use. Keyboard shortcuts would move between and activate links, inputs, etc. The document structure is stored in a tree, and algorithms for walking through the tree to find the next link or input would need to be developed. A further improvement would be to take layout position into account and implement moving in 2D.</p>
 <p><strong>Skills required:</strong> C, HTML, CSS, usability</p>
 <p><strong>Difficulty:</strong> Easy</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/textinput.c?view=markup">Key press handling</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.h?view=markup">Box tree structures</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/textinput.c?view=markup">Key press handling</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.h?view=markup">Box tree structures</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Printing improvements</h2>
 <p>Printing is currently only available on RISC OS, and the output is difficult for the user to predict. Work could include implementing printing for GTK, print preview, intelligent paging or reformatting, support for print stylesheets, and user control over what parts of the page are printed. This might include writing a portable base and platform-specific layer.</p>
 <p><strong>Skills required:</strong> C, CSS, GTK, possibly Cairo, possibly Postscript</p>
 <p><strong>Difficulty:</strong> Hard</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/print.c?view=markup">RISC OS printing implementation</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/riscos/print.c?view=markup">RISC OS printing implementation</a></p>
 <p><strong>References:</strong></p>
 
 <h2>PDF plotter</h2>
@@ -146,7 +146,7 @@
 </div>
 <p><strong>Skills required:</strong> C, graphics, PDF</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">Plotter interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/plotters.c?view=markup">RISC OS plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/gtk_plotters.c?view=markup">GTK plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/save_draw.c?view=markup">DrawFile plotter</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">Plotter interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/plotters.c?view=markup">RISC OS plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/gtk_plotters.c?view=markup">GTK plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/save_draw.c?view=markup">DrawFile plotter</a></p>
 <p><strong>References:</strong></p>
 <p><strong>Mentor:</strong> John Tytgat</p>
 
@@ -169,7 +169,7 @@
 <p>NetSurf currently has no support for CSS dynamic pseudo classes (e.g. :hover). The work would involve adding support for these classes to the CSS parser and selection engine and modifying the layout engine to handle dynamic style changes.</p>
 <p><strong>Skills required:</strong> C, HTML, CSS</p>
 <p><strong>Difficulty:</strong> Hard</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/css">CSS parser</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render">HTML handler and layout engine</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/css">CSS parser</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render">HTML handler and layout engine</a></p>
 <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21">CSS 2.1 specification</a></p>
 
 
@@ -177,7 +177,7 @@
 <p>NetSurf's RISC OS user interface is rich and powerful. It supports many features such as editable toolbars, dialogue box handling and menu generation. If the interface code was abstracted into a separate library, other RISC OS applications could benefit from the availability of a sophisticated, tried and tested and style guide compliant GUI toolkit.</p>
 <p><strong>Skills required:</strong> C, RISC OS WIMP, OSLib</p>
 <p><strong>Difficulty:</strong> Medium &ndash; Hard</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a></p>
 <p><strong>References:</strong> <a href="http://ro-oslib.sourceforge.net/">OSLib</a></p>
 
 <h2>Extracting the core into a library</h2>
@@ -190,7 +190,7 @@
 <p>Ideally, the back-end part of the browser would be abstracted to a stand-alone library, which a front-end could provide a table of entry points to. This allows for more than one program to use NetSurf's abilities efficiently, as well as giving us a chance to rationalise and tidy up the current rather ad-hoc API.</p>
 <p><strong>Skills required:</strong> C</p>
 <p><strong>Difficulty:</strong> Medium &ndash; Hard</p>
-<p><strong>Existing code:</strong> See &quot;Native Windows or Mac OS X ports&quot; and &quot;PDF plotter&quot;. <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/options.c?view=markup">Options code in back-end</a></p>
+<p><strong>Existing code:</strong> See &quot;Native Windows or Mac OS X ports&quot; and &quot;PDF plotter&quot;. <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/options.c?view=markup">Options code in back-end</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Improved inline element handling</h2>
@@ -203,7 +203,7 @@
 </ul>
 <p><strong>Skills required:</strong> C, HTML, CSS</p>
 <p><strong>Difficulty:</strong> Hard</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/render/layout.c?view=markup">Layout code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/render/layout.c?view=markup">Layout code</a></p>
 <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21/">CSS 2.1 specification</a></p>
 
 <h2>Improved GTK front end; tabs, downloads, etc</h2>
@@ -216,7 +216,7 @@
 </ul>
 <p><strong>Skills required:</strong> C, GTK</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/">Core code for text selection, export, etc</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/">Core code for text selection, export, etc</a></p>
 <p><strong>References:</strong></p>
 
 <div class="footer">
diff --git a/developers/gsoc/2009ideas.html b/developers/gsoc/2009ideas.html
index dd353ed..991819d 100644
--- a/developers/gsoc/2009ideas.html
+++ b/developers/gsoc/2009ideas.html
@@ -37,8 +37,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -61,9 +61,9 @@
 <ul>
 <li>Join our IRC channel <code>#netsurf</code> on <a href="http://freenode.net/">Freenode</a> and introduce yourself. Also, subscribe to the <a href="http://www.netsurf-browser.org/lists/netsurf-dev">developer mailing list</a>.</li>
 <li>Have access to a computer with supported OS (RISC OS, Linux, FreeBSD, BeOS, AmigaOS etc) or an OS relevant for the project you want to apply for (Windows, Mac OS).</li>
-<li>Get up to speed with <a href="http://wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>.</li>
+<li>Get up to speed with <a href="//wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>.</li>
 <li><a href="http://www.netsurf-browser.org/documentation/develop#Compiling">Build NetSurf</a> and enjoy using it. (Ask if you need help.)</li>
-<li>Get familiarised with the source code &ndash; read the <a href="http://source.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
+<li>Get familiarised with the source code &ndash; read the <a href="//source.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
 <li>Consider submitting a patch to fix an issue on our <a href="http://sourceforge.net/tracker/?func=browse&group_id=51719&atid=464312">bug tracker</a> or <a href="http://sourceforge.net/tracker/?func=browse&amp;group_id=51719&atid=464315">feature request tracker</a></li>
 </ul>
 <dd>
@@ -88,7 +88,7 @@
 </dd>
 </dl>
 
-<p>There is some more information in the <a href="http://wiki.netsurf-browser.org/google-summer-of-code">GSoC section</a> of our wiki. Note particularly the <a href="http://wiki.netsurf-browser.org/gsoc-student-guidelines">student guidelines</a>.</p>
+<p>There is some more information in the <a href="//wiki.netsurf-browser.org/google-summer-of-code">GSoC section</a> of our wiki. Note particularly the <a href="http://wiki.netsurf-browser.org/gsoc-student-guidelines">student guidelines</a>.</p>
 
 <p>Please <a href="/contact/">get in touch</a> if any of these ideas appeal to you or if you have your own idea for either <a href="/">NetSurf</a> or one of NetSurf's <a href="/projects/">sub-projects</a>. Come and chat to the developers in the NetSurf IRC channel or post to the developer mailing list.</p>
 
@@ -100,7 +100,7 @@
 <p>The browser currently requires a mouse to use. Keyboard shortcuts would move between and activate links, inputs, etc. The document structure is stored in a tree, and algorithms for walking through the tree to find the next link or input would need to be developed. A further improvement would be to take layout position into account and implement moving in 2D.</p>
 <p><strong>Skills required:</strong> C, HTML, CSS, usability</p>
 <p><strong>Difficulty:</strong> Easy</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/textinput.c?view=markup">Key press handling</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.h?view=markup">Box tree structures</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/textinput.c?view=markup">Key press handling</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.h?view=markup">Box tree structures</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Page reader</h2>
@@ -146,7 +146,7 @@
 </div>
 <p><strong>Skills required:</strong> C, DOM, XSLT (for the test suite)</p>
 <p><strong>Difficulty:</strong> Medium &ndash; Hard</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/dom/">LibDOM sources</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/dom/">LibDOM sources</a></p>
 <p><strong>References:</strong> <a href="http://www.w3.org/DOM/DOMTR">DOM specifications</a></p>
 
 <h2>Layout engine improvements</h2>
@@ -161,7 +161,7 @@
 <p>There are also other layout issues which could be tackled. For example in table layout some CSS properties, like <code style="color:#46a;">height</code>, are not handled for table rows.</p>
 <p><strong>Skills required:</strong> C, HTML, CSS</p>
 <p><strong>Difficulty:</strong> Medium &ndash; Hard</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/render/layout.c?view=markup">layout engine</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/html_redraw.c?view=markup">rendering code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/render/layout.c?view=markup">layout engine</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/html_redraw.c?view=markup">rendering code</a></p>
 <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21">CSS 2.1 specification</a>, <a href="http://www.w3.org/TR/CSS21/propidx.html">CSS 2.1 property index</a></p>
 
 <h2>Automated layout test engine</h2>
@@ -187,7 +187,7 @@
 </div>
 <p><strong>Skills required:</strong> C, HTML, CSS, scripting</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurftest/">existing test case repository</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.c?view=markup">box dump code &ndash; box_dump() (note that this is extremely verbose and contains much data that is of little use in automated testing)</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/debug/">debug front end</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/framebuffer/">framebuffer front end</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurftest/">existing test case repository</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.c?view=markup">box dump code &ndash; box_dump() (note that this is extremely verbose and contains much data that is of little use in automated testing)</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/debug/">debug front end</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/framebuffer/">framebuffer front end</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Core UI enhancements</h2>
@@ -201,15 +201,15 @@
 <p>Further to the above, the way NetSurf's core implements HTML frames is not particularly portable. This could be addressed as an extension.</p>
 <p><strong>Skills required:</strong> C, Usability</p>
 <p><strong>Difficulty:</strong> Easy &ndash; Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/tree.h?view=markup">Core treeview interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/tree.c?view=markup">Core treeview code</a></p>
-<p><strong>References:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">plotters interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/textarea.c?view=markup">textarea widget code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/tree.h?view=markup">Core treeview interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/tree.c?view=markup">Core treeview code</a></p>
+<p><strong>References:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">plotters interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/textarea.c?view=markup">textarea widget code</a></p>
 
 <h2>Native Windows or Mac OS X port</h2>
 <p>NetSurf currently has user-interface layers for several systems including RISC OS, GTK (on Linux, FreeBSD, etc.), AmigaOS and BeOS. The GTK interface works on Windows or Mac OS X, but a native interface for these systems would give a better experience.</p>
 <p>The existing front end implementations can be used as examples. Of these, the framebuffer front end is very self contained and the debug front end is the most minimal. For the rendering of NetSurf's content area, a set of plotters needs to be implemented for drawing primitives such as rectangles, plotting bitmaps and text.</p>
 <p><strong>Skills required:</strong> C, Windows UI development or Mac OS X UI development</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/gui.h?view=markup">Declarations of functions that each interface must implement</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">plotters interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/beos/">BeOS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/amiga/">AmigaOS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/framebuffer/">framebuffer specific code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/gui.h?view=markup">Declarations of functions that each interface must implement</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">plotters interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/beos/">BeOS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/amiga/">AmigaOS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/framebuffer/">framebuffer specific code</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Improved GTK front end</h2>
@@ -227,7 +227,7 @@
 </ul>
 <p><strong>Skills required:</strong> C, GTK</p>
 <p><strong>Difficulty:</strong> Easy &ndash; Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a></p>
 <p><strong>References:</strong></p>
 
 <h2>Improved Haiku/BeOS front end</h2>
@@ -247,7 +247,7 @@
 </div>
 <p><strong>Skills required:</strong> C++, BeOS/Haiku UI toolkits</p>
 <p><strong>Difficulty:</strong> Easy &ndash; Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/beos/">BeOS specific code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/beos/">BeOS specific code</a></p>
 <p><strong>References:</strong> <a href="http://www.haiku-os.org/community/gsoc2009/ideas">Haiku organisation ideas</a></p>
 
 <h2>Improved RISC OS front end</h2>
@@ -261,7 +261,7 @@
 </ul>
 <p><strong>Skills required:</strong> C, RISC OS Wimp programming using OSLib</p>
 <p><strong>Difficulty:</strong> Medium</p>
-<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a></p>
+<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a></p>
 <p><strong>References:</strong> <a href="http://ro-oslib.sourceforge.net/">OSLib</a></p>
 
 <div class="footer">
diff --git a/developers/gsoc/2014ideas.html b/developers/gsoc/2014ideas.html
index e159604..d57ba4b 100644
--- a/developers/gsoc/2014ideas.html
+++ b/developers/gsoc/2014ideas.html
@@ -37,8 +37,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -59,10 +59,10 @@
 <dt>Before applying for a project<dt>
 <dd>
 <ul>
-<li>Get up to speed with <a href="http://wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>. Here are a couple of articles that may help you get started with the NetSurf codebase: <a href="http://vincentsanders.blogspot.co.uk/2013/03/the-way-to-get-started-is-to-quit.html">Getting &amp; building the source</a>, and <a href="http://vincentsanders.blogspot.co.uk/2013/03/man-cannot-discover-new-oceans-unless.html">Working with the codebase and community</a>.</li>
+<li>Get up to speed with <a href="//wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>. Here are a couple of articles that may help you get started with the NetSurf codebase: <a href="http://vincentsanders.blogspot.co.uk/2013/03/the-way-to-get-started-is-to-quit.html">Getting &amp; building the source</a>, and <a href="http://vincentsanders.blogspot.co.uk/2013/03/man-cannot-discover-new-oceans-unless.html">Working with the codebase and community</a>.</li>
 <li><a href="http://www.netsurf-browser.org/documentation/develop#Compiling">Build NetSurf</a> and enjoy using it. (Ask on IRC if you need help.)</li>
 <li>Join our IRC channel <code>#netsurf</code> on <a href="http://freenode.net/">Freenode</a> and introduce yourself. Also, subscribe to the <a href="http://www.netsurf-browser.org/lists/netsurf-dev">developer mailing list</a>.</li>
-<li>Get familiarised with the source code &ndash; read the <a href="http://source.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
+<li>Get familiarised with the source code &ndash; read the <a href="//source.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li>
 <li>Consider submitting a patch to fix an issue on our <a href="http://bugs.netsurf-browser.org/">bug tracker</a>.</li>
 <li>Ideally students will have a dialogue with us about what they intend to do, before they make their application.</li>
 </ul>
@@ -87,7 +87,7 @@
 </dd>
 </dl>
 
-<p>There is some more information in the <a href="http://wiki.netsurf-browser.org/google-summer-of-code">GSoC section</a> of our wiki. Note particularly the <a href="http://wiki.netsurf-browser.org/gsoc-student-guidelines">student guidelines</a>.</p>
+<p>There is some more information in the <a href="//wiki.netsurf-browser.org/google-summer-of-code">GSoC section</a> of our wiki. Note particularly the <a href="http://wiki.netsurf-browser.org/gsoc-student-guidelines">student guidelines</a>.</p>
 
 <p>Please <a href="/contact/">get in touch</a> our project idea appeals to you or if you have your own idea for either <a href="/">NetSurf</a> or one of NetSurf's <a href="/projects/">libraries</a>. Come and chat to the developers in the NetSurf IRC channel or post to the developer mailing list.</p>
 
@@ -110,7 +110,7 @@
 <p>We consider this task to be fairly easy to complete. The number of missing specialisations is quite large, so do not be surprised if it takes longer than expected! We do not expect this phase to fill an entire summer, however.</p>
 <p>Expected outcome: a complete implementation of the HTMLElement DOM classes, which enable the HTMLElement tests in the LibDOM testsuite to pass.</p>
 </dd>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/libdom.git/tree/src/html">libdom/src/html</a>.<br><strong>Specification:</strong> <a href="http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/idl-definitions.html">Level 2 Document Object Model HTML</a>, <a href="http://dom.spec.whatwg.org/">DOM Standard</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/libdom.git/tree/src/html">libdom/src/html</a>.<br><strong>Specification:</strong> <a href="http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/idl-definitions.html">Level 2 Document Object Model HTML</a>, <a href="http://dom.spec.whatwg.org/">DOM Standard</a></p>
 </dd>
 </dl>
 <h4>Phase 2</h4>
@@ -123,7 +123,7 @@
 <p>This task involves identifying the differences between the behaviour implemented in LibHubbub and the expected behaviour defined by the specification. Once these differences have been identified, the implementation in LibHubbub should be brought in line with the specification.</p>
 <p>We expect this task to require a great deal of attention to detail. The initial stage of identifying the places where LibHubbub's implementation does not match the specification is crucial to the success of this task.</p>
 <p>Expected outcome: a detailed summary of the deficiencies in the LibHubbub implementation and a decent amount of progress towards rectifying them, with passing tests in the testsuite.</p>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/libhubbub.git/tree/">libhubbub/src</a><br><strong>Specification:</strong> <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html">HTML5 Parsing</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/libhubbub.git/tree/">libhubbub/src</a><br><strong>Specification:</strong> <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html">HTML5 Parsing</a></p>
 </dd>
 <dt>LibCSS: add support for CSS 3 properties</dt>
 <dd>
@@ -138,7 +138,7 @@
 </ul>
 <p>This task involves adding support for parsing and selecting properties defined in other CSS 3 module specifications. As CSS 3 is comprised of a very broad suite of components, the precise selection of which modules to target will be decided as part of the task definition with the student.</p>
 <p>Expected outcome: a decision about which CSS 3 component modules to implement; an implementation of the relevant property parsing and selection rules, along with passing test cases for the LibCSS testsuite.</p>
-<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/libcss.git/tree/src">libcss/src</a><br><strong>Specification:</strong> <a href="http://www.w3.org/Style/CSS/specs.en.html">CSS Specs</a></p>
+<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/libcss.git/tree/src">libcss/src</a><br><strong>Specification:</strong> <a href="http://www.w3.org/Style/CSS/specs.en.html">CSS Specs</a></p>
 </li>
 </dl>
 <p><strong>Skills required:</strong> Experience of the C programming language<br><strong>Skills desirable:</strong> HTML, DOM, CSS
diff --git a/developers/gsoc/index.html b/developers/gsoc/index.html
index 38db61d..49f8deb 100644
--- a/developers/gsoc/index.html
+++ b/developers/gsoc/index.html
@@ -37,8 +37,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -92,7 +92,7 @@
 
 <p>Our <a href="2009ideas">project ideas</a> page for Google Summer of Code 2009 is still available.</p>
 
-<p>We ask students to keep NetSurf's <a href="http://www.netsurf-browser.org/about/#ProjectGoals">project goals</a> in mind, especially the first point. We also ask them to communicate with the developers as much as possible. More information for students is available on the <a href="http://wiki.netsurf-browser.org/">development wiki</a>.</p>
+<p>We ask students to keep NetSurf's <a href="http://www.netsurf-browser.org/about/#ProjectGoals">project goals</a> in mind, especially the first point. We also ask them to communicate with the developers as much as possible. More information for students is available on the <a href="//wiki.netsurf-browser.org/">development wiki</a>.</p>
 
 <h2>Google Summer of Code 2008</h2>
 
diff --git a/developers/index.html b/developers/index.html
index fa0b059..ef6335a 100644
--- a/developers/index.html
+++ b/developers/index.html
@@ -38,8 +38,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -114,9 +114,9 @@
 
 <p>The source is kept in a Git repository. To check the latest source out use the command provided in the <a href="/documentation/develop#SourceControl">developer documentation</a>.</p>
 
-<p>The recommended compilers are GCC or Clang.  Guides to <a href="http://source.netsurf-browser.org/netsurf.git/tree/docs">building NetSurf</a> for various platforms are available in the source tree.</p>
+<p>The recommended compilers are GCC or Clang.  Guides to <a href="//source.netsurf-browser.org/netsurf.git/tree/docs">building NetSurf</a> for various platforms are available in the source tree.</p>
 
-<p>It is also possible to browse the source online via the <a href="http://source.netsurf-browser.org/netsurf.git/">web interface</a>.</p>
+<p>It is also possible to browse the source online via the <a href="//source.netsurf-browser.org/netsurf.git/">web interface</a>.</p>
 
 <h2>Contact the other developers</h2>
 
diff --git a/developers/publicity.html b/developers/publicity.html
index 0040fe8..ff67b91 100644
--- a/developers/publicity.html
+++ b/developers/publicity.html
@@ -38,8 +38,8 @@
 
 <div class="navsection">
 <ul class="sitelinks">
-<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li>
-<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li>
+<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li>
+<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li>
 <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li>
 <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li>
 <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li>
@@ -60,15 +60,15 @@
 <dt>Full NetSurf logo</dt>
 <dd>
 <ul>
-<li><a href="http://source.netsurf-browser.org/art.git/plain/logo/full/NetSurf,d94">Original ArtWorks format</a></li>
-<li><a href="http://source.netsurf-browser.org/art.git/plain/logo/full/NetSurf.svg">SVG format</a></li>
+<li><a href="//source.netsurf-browser.org/art.git/plain/logo/full/NetSurf,d94">Original ArtWorks format</a></li>
+<li><a href="//source.netsurf-browser.org/art.git/plain/logo/full/NetSurf.svg">SVG format</a></li>
 </ul>
 </dd>
 <dt>NetSurf emblem (no text)</dt>
 <dd>
 <ul>
-<li><a href="http://source.netsurf-browser.org/art.git/plain/logo/emblem/NetSurf,d94">Original ArtWorks format</a></li>
-<li><a href="http://source.netsurf-browser.org/art.git/plain/logo/emblem/NetSurf.svg">SVG format</a></li>
+<li><a href="//source.netsurf-browser.org/art.git/plain/logo/emblem/NetSurf,d94">Original ArtWorks format</a></li>
+<li><a href="//source.netsurf-browser.org/art.git/plain/logo/emblem/NetSurf.svg">SVG format</a></li>
 </ul>
 </dd>
 </dl>