Converting links to footnotes

Author: gvwilson

basics.tex

@@ -585,8 +585,7 @@ \section{Exercises}\label{s:basics-exercises}
 (You might notice that \texttt{typeof\ typeof} is syntactically invalid.
 In such circumstances,
 an internet search engine is your friend,
-as is the Mozilla Developer Network\index{Mozilla Developer Network} (MDN) JavaScript reference
-at \url{https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference}.
+as is the \hreffoot{https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference}{Mozilla Developer Network}\index{Mozilla Developer Network} JavaScript reference.
 
 \exercise{Fill in the Blanks}
 

capstone.tex

@@ -2,7 +2,7 @@ \chapter{Capstone Project}\label{s:capstone}
 
 It's time to bring everything together in an extended example:
 a (slightly) interactive visualization of species data from
-\url{https://figshare.com/articles/Portal_Project_Teaching_Database/1314459}.
+the \hreffoot{https://figshare.com/articles/Portal\_Project\_Teaching\_Database/1314459}{Portal Project Teaching Database}.
 Our plan is to:
 
 \begin{itemize}
@@ -716,9 +716,9 @@ \section{Running It}\label{s:capstone-run}
 
 \noindent
 The ``Learn More'' link given with the error message takes us to
-\href{https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin}{this page},
+\hreffoot{https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin}{this page},
 which uses many science words we don't know.
-A web search turns up \href{https://en.wikipedia.org/wiki/Cross-origin_resource_sharing}{this article on Wikipedia},
+A web search turns up \hreffoot{https://en.wikipedia.org/wiki/Cross-origin\_resource\_sharing}{this article on Wikipedia},
 which tells us that \gref{g:cors}{cross-origin resource sharing} (CORS)\index{CORS}
 is a security mechanism.
 If a page loads some JavaScript,

collab.tex

@@ -29,7 +29,7 @@ \section{Licensing Software}\label{s:collab-software}
 
 That is easier said than done,
 not least because the law hasn't kept up with everyday practice.
-\cite{Mori2012} and \href{http://www.astrobetter.com/blog/2014/03/10/the-whys-and-hows-of-licensing-scientific-code/}{this blog post}
+\cite{Mori2012} and \hreffoot{http://www.astrobetter.com/blog/2014/03/10/the-whys-and-hows-of-licensing-scientific-code/}{this blog post}
 are good starting points from a scientist's point of view,
 while \cite{Lind2008} is a deeper dive for those who want details.
 In brief,
@@ -55,8 +55,8 @@ \section{Licensing Software}\label{s:collab-software}
 
 To make license selection as easy as possible,
 GitHub allows you to select one of the most common licenses when creating a repository.
-The Open Source Initiative maintains \href{http://opensource.org/licenses}{a list of licenses},
-and \href{http://choosealicense.com/}{choosealicense.com} will help you find a license that suits your needs.
+The Open Source Initiative maintains \hreffoot{http://opensource.org/licenses}{a list of licenses},
+and \hreffoot{http://choosealicense.com/}{choosealicense.com} will help you find a license that suits your needs.
 Some of the things you will need to think about are:
 
 \begin{enumerate}
@@ -87,7 +87,7 @@ \section{Licensing Software}\label{s:collab-software}
 Any modifications to or software including (via compiler) GPL-licensed code must also be made available under the GPL
 along with build \& install instructions.
 
---- \href{https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3)}{tl;dr}
+--- \hreffoot{https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3)}{tl;dr}
 \end{quote}
 
 We recommend the MIT license:
@@ -99,7 +99,7 @@ \section{Licensing Data and Documentation}\label{s:collab-datadocs}
 
 The MIT license and the GPL apply to software.
 When it comes to data and reports,
-the most widely used family of licenses are those produced by \href{https://creativecommons.org/}{Creative Commons},
+the most widely used family of licenses are those produced by \hreffoot{https://creativecommons.org/}{Creative Commons},
 which have been written and checked by lawyers and are well understood by the community.
 
 The most liberal license is referred to as \gref{g:cc-0}{CC-0},
@@ -175,8 +175,9 @@ \section{Code of Conduct}\label{s:collab-conduct}
 
 Just as you shouldn't write your own license for a project,
 you probably shouldn't write your own Code of Conduct.
-We recommend using the \href{https://www.contributor-covenant.org}{Contributor Covenant} for development projects
-and the \href{http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy}{model code of conduct} from the \href{http://geekfeminism.wikia.com/}{Geek Feminism Wiki} for in-person events.
+We recommend using the \hreffoot{https://www.contributor-covenant.org}{Contributor Covenant} for development projects
+and the \hreffoot{http://geekfeminism.wikia.com/wiki/Conference\_anti-harassment/Policy}{model code of conduct}
+from the \hreffoot{http://geekfeminism.wikia.com/}{Geek Feminism Wiki} for in-person events.
 Both have been thought through carefully and revised in the light of experience,
 and both are now used widely enough that
 many potential participants in your project will not need to have them explained.

conduct.tex

@@ -71,7 +71,7 @@ \section{Scope}\label{s:conduct-scope}
 \section{Enforcement}\label{s:conduct-enforcement}
 
 Instances of abusive, harassing, or otherwise unacceptable behavior
-may be reported by \href{[email protected]}{emailing the project team}. All
+may be reported by \hreffoot{[email protected]}{emailing the project team}. All
 complaints will be reviewed and investigated and will result in a
 response that is deemed necessary and appropriate to the
 circumstances. The project team is obligated to maintain
@@ -85,4 +85,4 @@ \section{Enforcement}\label{s:conduct-enforcement}
 \section{Attribution}\label{s:conduct-attribution}
 
 This Code of Conduct is adapted from
-the \href{https://www.contributor-covenant.org}{Contributor Covenant} version 1.4.
+the \hreffoot{https://www.contributor-covenant.org}{Contributor Covenant} version 1.4.

contributing.tex

@@ -2,14 +2,12 @@ \chapter{Contributing}\label{s:contributing}
 
 Contributions of all kinds are welcome, from errata and minor improvements to
 entirely new sections and chapters: please
-\href{mailto:[email protected]}{email us} or submit an issue or pull
-request to \href{https://github.com/software-tools-in-javascript/js4ds/}{our
+submit an issue or pull request to \hreffoot{https://github.com/software-tools-in-javascript/js4ds/}{our
   GitHub repository}. Everyone whose work is incorporated will be acknowledged;
 please note that all contributors are required to abide by our Code of Conduct
 (\appref{s:conduct}).  Please note that we use Simplified English rather than
 Traditional English, i.e., American rather than British spelling and grammar. We
-encourage translations; if you would like to take this on, please
-\href{mailto:[email protected]}{email us}.
+encourage translations; if you would like to take this on, please \hreffoot{[email protected]}{email us}.
 
 If you wish to report errata or suggest improvements to wording, please include
 the chapter name in the first line of the body of your report (e.g., \texttt{Testing\ Data\ Analysis}).

dataforge.tex

@@ -449,8 +449,8 @@ \section{Subsets}\label{s:dataforge-subset}
 You may have noticed that the color values in the table above are strings rather than numbers.
 If we want Data-Forge to convert values to more useful types,\index{dataframe!type conversion}
 we can use the methods \texttt{parseDates}, \texttt{parseFloats}, and so on.
-The program below does this for data about earthquakes in August 2016,
-a subset of the dataset which can be found at \url{https://earthquake.usgs.gov/earthquakes/feed/v1.0/csv.php}:
+The program below does this for a subset of
+\hreffoot{https://earthquake.usgs.gov/earthquakes/feed/v1.0/csv.php}{USGS data about earthquakes in August 2016}:
 
 \begin{minted}{js}
 const fs = require('fs')

dataman.tex

@@ -94,7 +94,7 @@ \section{Data Formats}\label{s:dataman-formats}
 \section{Slicing Data}\label{s:dataman-slicing}
 
 The data we will use as an example is available in a variety of formats
-from \url{https://figshare.com/articles/Portal_Project_Teaching_Database/1314459}.
+from the \hreffoot{https://figshare.com/articles/Portal\_Project\_Teaching\_Database/1314459}{Portal Project Teaching Database}.
 We will focus on \texttt{surveys.csv},
 which has over 35,500 records.
 That's a lot to look at,
@@ -192,7 +192,7 @@ \section{Data Manager}\label{s:dataman-manager}
   to particular columns.
 \end{enumerate}
 
-We will use \href{https://www.papaparse.com/}{PapaParse}\index{PapaParse} to parse our CSV,
+We will use \hreffoot{https://www.papaparse.com/}{PapaParse}\index{PapaParse} to parse our CSV,
 so our first step is to install it:
 
 \begin{minted}{shell}
@@ -382,7 +382,7 @@ \section{Exercises}\label{s:dataman-exercises}
 a pseudo-random number generator will always produce the same sequence of values.
 
 There is no way to set a seed for \texttt{Math.random} out of the box,
-but the \href{https://www.npmjs.com/package/seedrandom}{seedrandom} package provides an add-on function for this purpose.
+but the \hreffoot{https://www.npmjs.com/package/seedrandom}{seedrandom} package provides an add-on function for this purpose.
 Install the package and modify the slice selection utility
 so that it takes a word or phrase as a command-line argument
 and uses it to seed the random number generator.
@@ -421,7 +421,7 @@ \section{Exercises}\label{s:dataman-exercises}
 \exercise{Handling Command-Line Arguments}
 
 Read the documentation for
-the \href{https://www.npmjs.com/package/command-line-args}{\texttt{command-line-args}} package
+the \hreffoot{https://www.npmjs.com/package/command-line-args}{\texttt{command-line-args}} package
 and rewrite the data slicing script to use it instead of \texttt{process.argv.slice}.
 
 \section*{Key Points}

db.tex

@@ -16,7 +16,7 @@ \chapter{Using a Database}\label{s:db}
 We will use a SQL database because it's still the most common choice,
 but we won't try to introduce SQL itself:
 for that,
-see \href{https://swcarpentry.github.io/sql-novice-survey/}{this short tutorial}.
+see \hreffoot{https://swcarpentry.github.io/sql-novice-survey/}{this short tutorial}.
 
 As an example problem,
 we will store information about workshops.

deploy.tex

@@ -6,7 +6,7 @@ \chapter{Deploying}\label{s:deploy}
 particularly because it shouldn't be done without thinking carefully about security,
 but there are now a few entry-level platforms you can try out.
 
-One of the simplest of these platforms is \href{https://glitch.com/}{Glitch},
+One of the simplest of these platforms is \hreffoot{https://glitch.com/}{Glitch},
 which is designed to help students build their first interactive websites.
 It isn't designed to host large, high-traffic applications,
 but is great for prototyping and classroom use.

dynamic.tex

@@ -11,8 +11,8 @@ \chapter{Dynamic Pages}\label{s:dynamic}
 the HTML is generated on the \gref{g:server}{server},
 and it was popular because that's where the data was,
 and that was the only place complex code could be run.
-(This tutorial uses a templating tool called \href{https://jekyllrb.com/}{Jekyll}.
-It's clumsy and limited, but it's the default on \href{http://github.com/}{GitHub}.)
+(This tutorial uses a templating tool called \hreffoot{https://jekyllrb.com/}{Jekyll}.
+It's clumsy and limited, but it's the default on \hreffoot{http://github.com/}{GitHub}.)
 
 Server-side generation can be done statically or dynamically,
 i.e.,
@@ -37,7 +37,7 @@ \chapter{Dynamic Pages}\label{s:dynamic}
 
 Many (many) JavaScript frameworks for client-side page generation have been created,
 and more are probably being developed right now.
-We have chosen \href{https://reactjs.org/}{React}\index{React} because it is freely available,
+We have chosen \hreffoot{https://reactjs.org/}{React}\index{React} because it is freely available,
 widely used,
 well documented,
 simpler than many alternatives,
@@ -140,7 +140,7 @@ \section{Hello, World}\label{s:dynamic-hello}
 \section{JSX}\label{s:dynamic-jsx}
 
 Writing nested functions is a clumsy way to write HTML,
-so most React programmers use a tool called \href{https://reactjs.org/docs/introducing-jsx.html}{JSX}\index{JSX}
+so most React programmers use a tool called \hreffoot{https://reactjs.org/docs/introducing-jsx.html}{JSX}\index{JSX}
 that translates HTML into JavaScript function calls.
 And yes,
 those JavaScript function calls then produce HTML---it's a funny world.
@@ -169,7 +169,7 @@ \section{JSX}\label{s:dynamic-jsx}
 \end{minted}
 
 Along with the two React libraries,
-this page includes a tool called \href{https://babeljs.io/}{Babel}\index{Babel}
+this page includes a tool called \hreffoot{https://babeljs.io/}{Babel}\index{Babel}
 to translate a mixed of HTML and JavaScript into pure JavaScript.
 To trigger translation,
 we add the attribute \texttt{type="text/babel"} to the \texttt{script} tag.
@@ -299,9 +299,9 @@ \section{Developing with Parcel}\label{s:dynamic-parcel}
 As with front-end frameworks,
 there are many to choose from,
 and new ones are being added almost weekly.
-\href{https://webpack.js.org/}{Webpack}\index{Webpack} is probably the most widely used,
+\hreffoot{https://webpack.js.org/}{Webpack}\index{Webpack} is probably the most widely used,
 but it is rather complex,
-so we will use \href{https://parceljs.org/}{Parcel},\index{Parcel}
+so we will use \hreffoot{https://parceljs.org/}{Parcel},\index{Parcel}
 which is younger and therefore not yet bloated
 (but give it time).
 
@@ -362,7 +362,7 @@ \section{Developing with Parcel}\label{s:dynamic-parcel}
 Parcel also caches things in \texttt{./.cache} so that it doesn't need to do redundant work;
 both directories are normally added to \texttt{.gitignore}.
 To learn more about Parcel,
-see \href{https://medium.com/codingthesmartway-com-blog/getting-started-with-parcel-197eb85a2c8c}{this short tutorial}.
+see \hreffoot{https://medium.com/codingthesmartway-com-blog/getting-started-with-parcel-197eb85a2c8c}{this short tutorial}.
 
 \figpdf{figures/dynamic-parcel.pdf}{What Goes Where with Parcel}{f:dynamic-parcel}
 

finale.tex

@@ -18,18 +18,18 @@ \chapter{Finale}\label{s:finale}
 as a data store.
 Beyond that,
 you could look at more advanced techniques in JavaScript \cite{Have2018},
-explore the full power of the \href{https://d3js.org/}{D3} library for interactive visualization \cite{Meek2017},
+explore the full power of the \hreffoot{https://d3js.org/}{D3} library for interactive visualization \cite{Meek2017},
 dive into data wrangling \cite{Davi2018},
 or start over completely the way JavaScript programmers do every eight months
-and rewrite everything with \href{https://developer.mozilla.org/en-US/docs/Web/Web_Components}{Web Components}.
+and rewrite everything with \hreffoot{https://developer.mozilla.org/en-US/docs/Web/Web\_Components}{Web Components}.
 Whatever you do,
 we hope that this tutorial has helped you get started.
 
 Contributions of all kinds are welcome,
 from errata and minor improvements to entirely new sections and chapters.
-Please \href{https://github.com/software-tools-in-javascript/js4ds/issues}{file an issue}
-or \href{https://github.com/software-tools-in-javascript/js4ds/pulls}{submit a pull request}
-in \href{https://github.com/software-tools-in-javascript/js4ds/}{our GitHub repository}.
+Please \hreffoot{https://github.com/software-tools-in-javascript/js4ds/issues}{file an issue}
+or \hreffoot{https://github.com/software-tools-in-javascript/js4ds/pulls}{submit a pull request}
+in \hreffoot{https://github.com/software-tools-in-javascript/js4ds/}{our GitHub repository}.
 Everyone whose work is incorporated will be acknowledged.
 Please see the contributors's guide for more information,
 and please note that all contributors are required to abide by

glossary.tex

@@ -578,8 +578,6 @@ \chapter{Glossary}\label{s:gloss}
 A pattern for matching text, written as text itself. Regular expressions
 are sometimes called ``regexp'', ``regex'', or ``RE'', and are as powerful as
 they are cryptic.
-See \href{https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions}{this documentation}
-for more details.
 
 \gitem{g:relational-database}{relational database}
 A database that organizes information into \grefcross{g:table}{tables}, each of which

htmlcss.tex

@@ -485,7 +485,7 @@ \section{Cascading Style Sheets}\label{s:htmlcss-css}
 A detailed discussion of the order of precedence for CSS rules
 is outside the scope of this tutorial. We recommend that those
 likely to work often with stylesheets read (and consider bookmarking)
-\href{https://www.w3schools.com/css/css_specificity.asp}{this W3Schools page}.
+\hreffoot{https://www.w3schools.com/css/css\_specificity.asp}{this W3Schools page}.
 
 One other thing CSS can do is match specific elements.
 We can label particular elements uniquely within a page using the \texttt{id} attribute,\index{element!ID}
@@ -539,7 +539,7 @@ \section{Bootstrap}\label{s:htmlcss-bootstrap}
 
 CSS can become very complicated very quickly,
 so most people use a framework to take care of the details.
-One of the most popular is \href{https://getbootstrap.com/}{Bootstrap}\index{Bootstrap}
+One of the most popular is \hreffoot{https://getbootstrap.com/}{Bootstrap}\index{Bootstrap}
 (which is what we're using to style this website).
 Here's the entire source of a page that uses Bootstrap
 to create a two-column layout with a banner at the top:

interactive.tex

@@ -542,7 +542,7 @@ \section{Fetching Data}\label{s:interactive-fetching}
 \texttt{React} will complain if we don't provide a unique key\index{React!need for unique keys}
 to distinguish elements that we create,
 since having these keys helps it keep track of the component-to-DOM relationship,
-which in turn \href{https://stackoverflow.com/questions/28329382/understanding-unique-keys-for-array-children-in-react-js}{makes updates much more efficient}.
+which in turn \hreffoot{https://stackoverflow.com/questions/28329382/understanding-unique-keys-for-array-children-in-react-js}{makes updates much more efficient}.
 Since each asteroid's name is supposed to be unique,
 we use that name as the key for each table row.
 
@@ -779,7 +779,7 @@ \section{Exercises}\label{s:interactive-exercises}
 
 Are the curly braces necessary when exporting from a component file?
 What happens if you remove them?
-Read this \href{http://2ality.com/2014/09/es6-modules-final.html}{blogpost} and then consider whether it might
+Read this \hreffoot{http://2ality.com/2014/09/es6-modules-final.html}{blogpost} and then consider whether it might
 have been more appropriate to use default exports and imports
 in the examples above.