Table of Contents
main tags with the following:
<h4 class="list-heading"><span>Select a Verse</span></h4><div id="verse-list" class="list-container numeric-list"></div><div class="eb-container" id="chapter-text"></div>
Also, right below the link to
main.css in the header, link to
scripture.css with this line:
<link href="css/scripture.css" rel="stylesheet" />
scripture.css contains styles specifically for the HTML returned from the API. For the style to work correctly, the returned HTML must be enclosed in an element containing the class
If you use
scripture.csson your page, make sure to enclose the HTML returned from the API in a container that has the class
my_key.js, add the following line so we are able to use FUMS data (this is explained more later in this section).
Whenever your page will get verse text from API.Bible, you should include the line above to handle FUMS data.
Some key things to notice:
- Line 26:
bibleChapterIDreturned from the API includes both the book abbreviation and chapter number. Here they are broken out into individual variables.
- This page has two API calls. Both the
getChapterTextfunctions get data from the API.
getChapterTextfunction is the first time we use FUMS data.
FUMS is the Fair Use Management System. It's a system that we ask all API developers to use as a way to help us ensure that the API contents are being used fairly. It also allows us to profile usage of the various versions, books, chapters, and verses that are requested from the API, so that we can communicate the value of API-accessible Scripture texts back to copyright holders and publishers.
fumsv2.min.js) in your project. All API calls that return verse text also return a
fumsId in the
meta section. To send API.Bible data about your request, make a call to the
On this page, include the
searchButtonfunctions from before.