fixing more broken links

mattmakai · mattmakai · commit a8ad4f4bcf7f · 2021-06-10T06:57:08.000-04:00
diff --git a/content/pages/04-web-development/00-web-development.markdown b/content/pages/04-web-development/00-web-development.markdown
@@ -100,11 +100,6 @@ world.
   something obvious you can handle in a few minutes that will improve
   your site's security, performance or usability.
 
-* [Web application development is different and better](http://radar.oreilly.com/2014/01/web-application-development-is-different-and-better.html)
-  provides some context for how web development has evolved from writing
-  static HTML files into the complex JavaScript client-side applications
-  produced today.
-
 * [The Browser Hacker's Guide to Instantly Loading Everything](https://www.youtube.com/watch?v=7vUs5yOuv-o)
   is a spectacular technical talk given by Addy Osmani at JSConf EU 2017
   that has great bits of developer knowledge for both beginner and 
diff --git a/content/pages/04-web-development/17-css.markdown b/content/pages/04-web-development/17-css.markdown
@@ -149,10 +149,6 @@ web application's design.
 * [Google's Web Fundamentals class](https://developers.google.com/web/fundamentals/)
   shows how to create responsive designs and performant websites.
 
-* [Tailoring CSS for performance](http://programming.oreilly.com/2014/04/tailoring-css-for-performance.html)
-  is an interesting read since many developers do not consider the 
-  implications of CSS complexity in browser rendering time.
-
 * [Can I Use...](http://caniuse.com/) is a compatibility table that shows
   which versions of browsers implement specific CSS features.
 
diff --git a/content/pages/04-web-development/32-pelican.markdown b/content/pages/04-web-development/32-pelican.markdown
@@ -76,10 +76,6 @@ to hosting services such as Amazon S3 and GitHub Pages.
   take in new input markup formats, modify the generator process and
   add handy features such as a custom table of contents.
 
-* [Pelican Sitemap and Pagination](http://www.vcheng.org/2014/02/22/pelican-sitemap-pagination/)
-  explains how to generate a `sitemap.xml` file for your static site that 
-  includes all pages instead of just auto-included top-level pages.
-
 * [Getting started with Pelican and GitHub pages](http://www.mattmakai.com/introduction-to-pelican.html)
   is a tutorial I wrote to use the Full Stack Python source code to create
   and deploy your first static site.
diff --git a/content/pages/04-web-development/43-webrtc.markdown b/content/pages/04-web-development/43-webrtc.markdown
@@ -26,11 +26,6 @@ browser) and server (usually a [web server](/web-servers.html)).
   dependencies. It allows 2 web browsers to exchange audio and video streams by
   using the `aiohttp` and `python-socketio` modules.
 
-* [A real world guide to WebRTC](https://deepstreamhub.com/tutorials/protocols/webrtc-intro/)
-  goes through WebRTC fundamentals such as data channels, audio and video,
-  screen sharing and file transfers with the JavaScript code provided
-  for each concept.
-
 * The 
   [Introduction to WebRTC video series](https://www.youtube.com/watch?v=ujpIAWmK2Vo)
   ([part 2](https://www.youtube.com/watch?v=cw2iTgIW-uk) and 
diff --git a/content/pages/04-web-development/48-api-creation.markdown b/content/pages/04-web-development/48-api-creation.markdown
@@ -26,9 +26,6 @@ applications through machine-to-machine communication.
   [own GitHub organization](https://github.com/flask-restful/flask-restful)
   so engineers from outside the company could be core contributors.
 
-* [Flask API](http://www.flaskapi.org/) is another common library for 
-  exposing APIs from Flask web applications.
-
 * [Sandman](http://www.github.com/jeffknupp/sandman) is a widely used tool to
   automatically generate a RESTful API service from a legacy database without
   writing a line of code (though it's easily extensible through code).
@@ -154,10 +151,6 @@ equivalent of browser testing in the web application world.
   will use your API, as well as what the documentation for endpoints
   and other important pieces should look like.
 
-* [1-to-1 Relationships and Subresources in REST APIs](http://developers.lyst.com/2015/02/20/1-to-1-relationships-and-subresources-in-rest-apis/)
-  tells the story of design decisions that were made during an API's creation
-  and why those choices were made.
-
 * [How many status codes does your API need?](https://blogs.dropbox.com/developers/2015/04/how-many-http-status-codes-should-your-api-use/)
   gives an answer from a Dropbox API developer as to their decision making
   process.
