Add a staging config.yml for use when deploying to staging slot and r…

…eplace absolute links with relative links (#357)

.github/workflows/publish_to_production_slot.yml

@@ -25,7 +25,7 @@ jobs:
         run: |
           docker run \
             -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
-            jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future"
+            jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --config _config.yml --future"
 
       - name: Log in with Azure # Using Azure Service Principal
         uses: azure/login@v1

.github/workflows/publish_to_staging_slot.yml

@@ -25,7 +25,7 @@ jobs:
         run: |
           docker run \
             -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \
-            jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future"
+            jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --config _config_staging.yml --future"
 
       - name: Log in with Azure # Using Azure Service Principal
         uses: azure/login@v1

_config_staging.yml

@@ -0,0 +1,31 @@
+# Site settings
+title: OData - the Best Way to REST
+email: odata-discussion@googlegroups.com
+description: > # this means to ignore newlines until "baseurl:"
+  OData, short for Open Data Protocol, is an open protocol
+  to allow the creation and consumption of queryable and interoperable RESTful APIs
+  in a simple and standard way.
+baseurl: "" # the subpath of your site, e.g. /blog/
+url: "https://odata-prod-stage.azurewebsites.net" # the base hostname & protocol for your site
+twitter_username: odataorg
+github_username:  odataorg
+
+collections:
+  ecosys:
+    output: true
+    permalink: /ecosystem/:categories/:title/
+  libraries:
+    output: true
+  tutorials:
+    output: true
+    permalink: /tutorials/:title/
+
+permalink: /blog/:title/
+
+# highlighter: pygments
+
+# Build settings
+markdown: kramdown
+
+gems:
+  - jekyll-sitemap

_ecosys/consumers/Client-Libraries.md

@@ -2,6 +2,6 @@
 layout: default
 category: consumers
 title: "Client Libraries"
-link: "https://www.odata.org/libraries"
+link: "/libraries"
 ---
 Client libraries are programming libraries that make it easy to consume OData services. We already have libraries that target: Javascript, PHP, Java, Windows Phone 7 Series, iPhone (Objective C) and .NET. For a complete list visit the OData SDK.

_ecosys/sdk/Sample-Services.md

@@ -4,4 +4,4 @@ category: sdk
 title: "Sample Services"
 github: "https://github.com/OData/ODataSamples"
 ---
-Github repository of ODataSamples, including code used in [here](https://www.odata.org/odata-services/).
+Github repository of ODataSamples, including code used in [here](/odata-services/).

_includes/head.html

@@ -31,7 +31,7 @@
   
   -->
 
-  <link rel="stylesheet" href="https://www.odata.org/public/css/bootstrap.min.css"/>
+  <link rel="stylesheet" href="{{'/public/css/bootstrap.min.css' | prepend: site.baseurl | prepend: site.url}}">
   <link rel="stylesheet" href="{{'/public/css/site.css' | prepend: site.baseurl | prepend: site.url}}">
   <link rel="stylesheet" href="{{'/public/css/syntax.css' | prepend: site.baseurl | prepend: site.url}}">
   <link rel="stylesheet" href="{{'/public/css/autocomplete.css' | prepend: site.baseurl | prepend: site.url}}">

_posts/2010-04-13-odata-weekly-roundup-2.html

@@ -19,8 +19,8 @@
 <li><strong>Open Source the .NET producer libraries:</strong> This is something that we've now heard from a number of people.  We are working through the feasibility and associated logistics at the moment.  We will let you know as we make progress on our thinking around this request.</li>
 <li><strong>Create or Foster producer libraries for different platforms:</strong> Closely related is the need to make it easy to create OData Services on all major platforms. The most common requests being Java (because of it's importance to the enterprise), PHP, Python and Ruby (OData on Rails?). Doug Purdy has a blog post asking for your opinions <a href="https://www.douglaspurdy.com/2010/04/03/open-source-odata-server/"> here</a>. Again we are investigating options here. We are also trying to figure out how we can help simplify creating libraries and services. So far we've released the OData Validation Toolkit to help you validate your service. Can you think of anything else beyond just libraries that would help? We'd love to hear you suggestions here.</li>
 <li><strong>Sample Producer code on different platforms:</strong> We've heard a lot of requests for sample code to create an OData Service in language X on platform Y. You might think this is dependent on the above, and to implement the whole of OData it certainly is, but OData is flexible enough that you can do a rudimentary OData service - in any language - very easily. Check out  <a href="https://blogs.msdn.com/pablo/archive/2010/01/26/implementing-only-certain-aspects-of-odata.aspx"> Implementing only certain aspects of OData</a> for more.</li>
-<li><strong>Test Suite for Producers and Producer Libraries:</strong> Anders Hol wondered if we would release our test suites too. The OData Validation Toolkit - part of the <a href="https://www.odata.org/developers/odata-sdk">OData SDK</a> - should help. The toolkit looks at your service's data model, which it tries to extract by going to $metadata, and then runs some <a href="https://msdn.microsoft.com/en-us/library/bb126445.aspx">T4 templates</a> against your model to produce tests bound to your service. The cool thing is that the location of the T4 templates can easily be changed, so you can reference your own T4 templates. Why would you do that? Well you could extend our, admittedly rudimentary, templates or refactor the existing templates so they emit Ruby or Java tests instead of C#. In fact we hope community authored language packs will emerge over time. Indeed if you create them we will definitely let the community know.</li>
-<li><strong>Hiding Properties:</strong> Luigi wanted to know how to hide properties. If you use the .NET Data Services producer libraries then by default every property in your underlying class gets exposed. So you should think of the classes exposed by your data service in the same way you think about a View Model for UI code: if you don't want to expose it don't put in your class. If re-working your class isn't a realistic option, you can still hide properties by creating a  <a href="https://blogs.msdn.com/alexj/archive/2010/01/07/data-service-providers-getting-started.aspx"> Custom Data Services Provider</a>. You can find more Custom Data Service samples and guidance in the <a href="https://www.odata.org/developers/odata-sdk">OData SDK</a>.</li>
+<li><strong>Test Suite for Producers and Producer Libraries:</strong> Anders Hol wondered if we would release our test suites too. The OData Validation Toolkit - part of the <a href="/developers/odata-sdk">OData SDK</a> - should help. The toolkit looks at your service's data model, which it tries to extract by going to $metadata, and then runs some <a href="https://msdn.microsoft.com/en-us/library/bb126445.aspx">T4 templates</a> against your model to produce tests bound to your service. The cool thing is that the location of the T4 templates can easily be changed, so you can reference your own T4 templates. Why would you do that? Well you could extend our, admittedly rudimentary, templates or refactor the existing templates so they emit Ruby or Java tests instead of C#. In fact we hope community authored language packs will emerge over time. Indeed if you create them we will definitely let the community know.</li>
+<li><strong>Hiding Properties:</strong> Luigi wanted to know how to hide properties. If you use the .NET Data Services producer libraries then by default every property in your underlying class gets exposed. So you should think of the classes exposed by your data service in the same way you think about a View Model for UI code: if you don't want to expose it don't put in your class. If re-working your class isn't a realistic option, you can still hide properties by creating a  <a href="https://blogs.msdn.com/alexj/archive/2010/01/07/data-service-providers-getting-started.aspx"> Custom Data Services Provider</a>. You can find more Custom Data Service samples and guidance in the <a href="/developers/odata-sdk">OData SDK</a>.</li>
 <li><strong>RDF data sources and RDF format:</strong> Jay Funnell would like to have the ability to consume and produce RDF built-in to the protocol. Consuming RDF in a Data Service is possible today, but you have to write a <a href="https://blogs.msdn.com/alexj/archive/2010/01/07/data-service-providers-getting-started.aspx"> Custom Data Service Provider</a>. And as of today there isn't a prescribed way to translate OData into RDF. We wonder whether RDF integration with OData is important beyond those who are extremely passionate about RDF? Is this something that you want to see?</li>
 <li><strong>Primitive Types and Namespaces:</strong> Eric Westenberger asked a good question about how to map his Java types into OData. Basically when you create your model, you can choose any Namespace and Name so long as it complies with the <a href="https://www.ecma-international.org/publications/standards/Ecma-334.htm"> C# identifier rules</a> and is no more the 480 characters long. What this means in practice is that most Java class and namespace names should be fine. OData also ships with a built-in set of  <a href="https://www.odata.org/media/6652/%5bmc-csdl%5d%5b1%5d.htm#_Toc246717571"> primitive types</a>, that you must be able to map your properties into. Please let us know if you think we are missing key primitive types.</li>
 <li><strong>Licensing questions:</strong> Gustavo Andriotti wanted to know more about the licensing of the Protocol and the OData SDK. The OData Protocol itself is released under the <a href="https://www.microsoft.com/interop/osp/default.mspx">Open Specification Promise</a>, if you take another look at the OData home page you will notice we reworked it to make this clearer.  The OData SDK on the other hand is a collect of resources, each of which have their own license. Most of the time the license is either  <a href="http://en.wikipedia.org/wiki/Shared_source#Microsoft_Public_License_.28Ms-PL.29"> Ms-PL</a> or <a href="http://en.wikipedia.org/wiki/Apache_License">Apache</a>. To be sure simply follow the download link for licensing terms. Thanks again for the feedback Gustavo.</li>

_posts/2010-05-07-odata-roundup-3.html

@@ -14,10 +14,10 @@
 <div>
 <p>Many exciting things have happened in the OData world since our last post.</p>
 <ul>
-<li>We <a href="https://www.odata.org/blog/the-open-data-protocol-net-framework-client-library-source-code-available-for-download"> released the source code</a> for our .NET client library on <a href="http://odata.codeplex.com/">codeplex</a>.</li>
-<li>We announced the <a href="https://www.odata.org/blog/odata-roadshow">OData Roadshow</a> which will visit: New York, Chicago, Mountain View, Shanghai, Tokyo, Reading and Paris in the coming months. See if you can get along.</li>
+<li>We <a href="/blog/the-open-data-protocol-net-framework-client-library-source-code-available-for-download"> released the source code</a> for our .NET client library on <a href="http://odata.codeplex.com/">codeplex</a>.</li>
+<li>We announced the <a href="/blog/odata-roadshow">OData Roadshow</a> which will visit: New York, Chicago, Mountain View, Shanghai, Tokyo, Reading and Paris in the coming months. See if you can get along.</li>
 <li>The <a href="http://windowsteamblog.com/blogs/windowslive/archive/2010/04/29/messenger-across-the-web.aspx"> next version of Windows Live Messenger</a> will include a RESTful interface that supports OData.</li>
-<li>We asked whether people thought making <a href="https://www.odata.org/blog/queryable-odata-metadata"> OData metadata queryable</a> would be useful?</li>
+<li>We asked whether people thought making <a href="/blog/queryable-odata-metadata"> OData metadata queryable</a> would be useful?</li>
 <li>Tomorrow we are putting on a free webcast, <a href="https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032450906&amp;EventCategory=2&amp;culture=en-US&amp;CountryCode=US"> OData and You: An everyday guide for Architects Featuring Douglas Purdy</a>.</li>
 <li>We released an updated version of the <a href="http://www.silverlight.net/content/samples/odataexplorer/">OData Explorer</a> that now works with the RTM version of Silverlight 4.</li>
 <li>And as always lots of things are happening on <a href="https://twitter.com/home#search?q=%23odata">twitter</a>.</li>
@@ -27,7 +27,7 @@
 <li>Michael asks how do you consume a .NET 4.0 Data Service from Silverlight 3?<br />
 Today in SL3 there is no supported way to consume V2 features of an OData service.<br />
 Which means Data Services built with either .NET 4.0 or the Data Services Update for .NET 3.5 Framework SP1 aren't fully supported. If it is an option you should upgrade to <a href="https://www.microsoft.com/silverlight/">Silverlight 4</a>.</li>
-<li>We keep hearing requests to make OData and RDF more interoperable. And at the moment we are thinking about that that might mean. We even made <a href="https://www.odata.org/blog/queryable-odata-metadata"> one related proposal</a> to try to gauge community interest.</li>
+<li>We keep hearing requests to make OData and RDF more interoperable. And at the moment we are thinking about that that might mean. We even made <a href="/blog/queryable-odata-metadata"> one related proposal</a> to try to gauge community interest.</li>
 <li>Vasa asked: "How do I consume the Reporting Services OData Report feed programmatically"?<br />
 You can generalize this question down to: "How do you program against a single feed with no service documents and no $metadata support?"<br />
 A very interesting question. One that I plan on reporting back on once I've had a chance to investigate more.</li>
@@ -38,7 +38,7 @@
 <li><a href="https://delicious.com/kidehen/odata_demo">Virtuoso Sponger Middleware &amp; OData Demo</a></li>
 </ul>
 </li>
-<li>One person wanted to know how to expose a Service Operation via a custom Data Service Provider. There is a sample of this in the <a href="http://odata.org/developers/odata-sdk">OData SDK</a> - but it is well hidden - you need to download the code Sample code for the Sample Services, unzip and look inside <em>/ODataWeb/OData/OData.svc.cs</em>. It is a Data Service Provider based Service that exposes a service operation.</li>
+<li>One person wanted to know how to expose a Service Operation via a custom Data Service Provider. There is a sample of this in the <a href="/developers/odata-sdk">OData SDK</a> - but it is well hidden - you need to download the code Sample code for the Sample Services, unzip and look inside <em>/ODataWeb/OData/OData.svc.cs</em>. It is a Data Service Provider based Service that exposes a service operation.</li>
 <li>John asked for more public OData Services to be listed on the Producers page. Especially ones that have geo data included, so he and other can create some compelling mashups. We hear you John and are trying to make the Producers page more reactive.</li>
 <li>John also hopes that one day his browser will become OData aware, with special OData specific options and commands becoming available. This is definitely part of the dream John!</li>
 </ul>

_posts/2010-05-12-odata-roadshow.html

@@ -12,7 +12,7 @@
 author: OData.org Archive
 ---
 <div>
-<p>In case you haven't heard already we are putting on an <a href="https://www.odata.org/blog/odata-roadshow">OData Roadshow</a>.</p>
+<p>In case you haven't heard already we are putting on an <a href="/blog/odata-roadshow">OData Roadshow</a>.</p>
 <p><a href="https://twitter.com/douglasp">Douglas Purdy</a> and <a href="https://twitter.com/lostintangent">Jonathan Carter</a> will be presenting and guiding attendees through a free day's worth of OData goodness.</p>
 <p>The Roadshow will visit each of these locations:</p>
 <ul>

_posts/2010-06-01-odata-workshops-in-raleigh-charlotte-atlanta-chicago-and-nyc.html

@@ -12,7 +12,7 @@
 ---
 <div>
 <p>Chris (aka <a href="http://www.chriswoodruff.com/">Woody</a>) Woodruff has organized a series of <a href="http://www.chriswoodruff.com/index.php/2010/05/11/odata-blowout-in-june-8-odata-workshops-in-raleigh-charlotte-atlanta-chicago-and-nyc/"> OData workshops</a> to compliment the official <a href="http://odata.org/roadshow">OData Roadshow</a>.</p>
-<p>This is highly recommended. So if for whatever reason you can't make it to one of the OData Roadshow events, or you just can't get enough <a href="http://odata.org/">OData</a>, see if you can get along to one of Chris' workshops.</p>
+<p>This is highly recommended. So if for whatever reason you can't make it to one of the OData Roadshow events, or you just can't get enough <a href="/">OData</a>, see if you can get along to one of Chris' workshops.</p>
 <p>The workshops start in Raleigh tomorrow and finish in NYC on June 28th.</p>
 <p><a href="http://www.chriswoodruff.com/index.php/2010/05/11/odata-blowout-in-june-8-odata-workshops-in-raleigh-charlotte-atlanta-chicago-and-nyc/"> Learn more and register here</a>.</p>
 </div>

_posts/2010-06-28-join-the-odata-mailing-list.html

@@ -14,7 +14,7 @@
 <div>
 <p>Today we released an OData Mailing List.  This is the list to use if you have OData questions, comments on OData or want to discuss how OData should evolve over time.</p>
 <p>To sign up to the list go <a href="http://mailinglist.odata.org/SCRIPTS/WA-ODATA.EXE?SUBED1=ODATA&amp;A=1"> here</a> and follow the instructions provided.  The list is fully open so anyone can subscribe and participate.  Be sure to read the terms of use on the signup page to understand how your feedback on the mailing list may be used to enhance OData over time.</p>
-<p>You can see a read only archive of all the messages from the mailing list here: <a title="/mailing-list" href="https://www.odata.org/join-the-odata-discussion/">/mailing-list</a></p>
+<p>You can see a read only archive of all the messages from the mailing list here: <a title="/mailing-list" href="/join-the-odata-discussion/">/mailing-list</a></p>
 <p>We look forward to hearing your thoughts, comments and feedback!</p>
 <p>&nbsp;</p>
 <p>-<a href="http://www.flasko.net/">Mike Flasko</a></p>

_posts/2010-07-30-enhancing-odata-support-for-querying-derived-types.html

@@ -111,6 +111,6 @@ <h3>Pros and Cons?</h3>
 <h3>Summary:</h3>
 <p>As you can see we've come up with two options to add better support for Derived types in OData queries.</p>
 <p>Which do you prefer? And why? Perhaps you have another suggestion?</p>
-<p>Whatever you think, please tell us all about it on the <a href="https://www.odata.org/join-the-odata-discussion/">OData Mailing List</a>.</p>
+<p>Whatever you think, please tell us all about it on the <a href="/join-the-odata-discussion/">OData Mailing List</a>.</p>
 <p><a href="https://twitter.com/adjames">Alex James</a></p>
 </div>