pstephens/kingjames.bible

Source for the King James Bible

kingjames.bible's Issues

Automated S3 deployments for VOTD

The existing sync script is PowerShell based. Let's make this xplat by using the AWS nodejs SDK and the biblecli wrapper.

Add rel="next" and rel="prev" to various hyperlinks.

Implement node-js based static content server.

Simulate S3 and Cloudfront's capabilities. Support mime types, compression headers (but not compression negotiation), and cache-control.

Implement optimized asset pipeline

• Leverage the node.js and npm ecosystem.
• Hash all resources except html to maximize cache-control max age.
• Modify the publish script to publish all non-html resources first, then html resources. This will ensure that html pages will not be broken during the publishing window.

Minify votd.js to reduce bandwidth

Documentation - How to embed the verse of the day

Use a markdown processor.

Rebrand to https://kingjames.bible

everlastingbible.com -> kingjames.bible

Cleanup code

Some of these things have been completed already:

• Cleanup some of the redundant code in bucketsync.
• Add profiles to gulp file to deal with prod/beta differences. Work done for #35.
• Add canonical base url / base url parameters to static generation. Work done for #23.

Implement persistent -> runtime model with basic bible API

Must support:

• browser hosted
• async I/O

Split into two parts:
Create 'ensure*' functions which performs I/O to bring in missing data.
And then pure functions on top of the runtime model to implement the API.

Implement basic BrowserStack integration

Implement a basic smoke test.

Clickable elements too close together and Content wider than screen

hi am using bridge wordpress theme.
Am checking in console no issue found. website is fully responsive on mobile device.
but when am checking in webmaster it show 2 error "Clickable elements too close together" and "Content wider than screen".
I had update line-height & margin but issue are same.
Please help me to fix out this for my website.

Resolve "Clickable elements too close together" mobile usability error.

See guidelines here: https://www.portent.com/blog/seo/dont-fail-googles-mobile-friendly-test.htm

Here's a testing tool: https://www.google.com/webmasters/tools/mobile-friendly/?url=https%3A%2F%2Fkingjames.bible

More information about the "mobile friendly badge": https://webmasters.googleblog.com/2014/11/helping-users-find-mobile-friendly-pages.html

Seed VOTD differently for each domain name

Harden security settings

See the report generated at https://securityheaders.io/?q=kingjames.bible&followRedirects=on

Mitigate as many as possible within the limits of Cloud Formation and Certificate Manager.

Parse raw bible text into cljs data and write out normalized form

Implement basic down-level compatibility for "Old-IE" and other statistically relavent browsers

Render chapters with Om/react.

Will also need to render static html wrapper with Hiccups.

Stage initial bible resource files

Write out files by book in Transport format. Also write out gzip'd versions.

Concordance...

One thing that could be done to make this project even better would be to include a concordance as well.

Rudimentary static website

One chapter per page. And a table of contents.

No searching. Minimal formatting.

Separate resource for each book index

This will create 66 additional html resources, one for each book, and will enable browsing the entire site with JavaScript disabled.

Also-- the original URLs (i.e. http://kingjames.bible/#Genesis) should have a client side redirect to maintain continuity for legacy bookmarks.

Redirect from /#Genesis to /Genesis

Redirect previous hash tag based book chapter indexes to the new resource based chapter indexes.

This must be accomplished in JavaScript as the hash id is only available on the client side.

Documentation - About Page

Write this.

Implement "Verse of the Day"

• Preset list of verses.
• Static randomization seed.
• Links back to the respective verse at https://kingjames.bible

Add preload directivies for svg icons.

<link rel="preload" href="home.svg" />

This is only needed for SVG icons. The PNG fallbacks can be loaded on demand as needed.

Add a favicon

Several resources:
http://stackoverflow.com/questions/25952907/favicon-ico-vs-link-rel-shortcut-icon
http://stackoverflow.com/questions/2268204/favicon-dimensions
http://caniuse.com/#feat=link-icon-svg

Wrong domain in sitemap.xml and robots.txt

These files are references beta.kingjames.bible but should be referencing kingjames.bible

Incorrect text in Revelation 17:5

Per e-mail feedback:

Please note the following text in Rev 17:5 from your page:
5 And upon her forehead was a name written, MYSTERY, BABYLON THE GREAT, THE MOTOF HARLOTS AND ABOMINATIONS OF THE EARTH.

Of course, it should read:
5 And upon her forehead was a name written, Mystery, Babylon The Great, The Mother Of Harlots And Abominations Of The Earth.

Fix w3c validator errors.

Highlighted verse displays under menu for mobile views

• Mobile view can be simulated by sufficiently reducing web page width on a desktop browser.
• A couple of possible ways to fix:
  • Make the verse content area a div that does not intersect the menu.
  • Or, don't use automatic browser hash scrolling and scroll the highlighted verse into view using JavaScript.

Example: Navigating to this url, https://kingjames.bible/Genesis-1#4, yields this screenshot:

Documentation - How to link to verses

Use a markdown processor.

Add Home icon in menu

Add to menu/breadcrumb bar.

• Icon should be svg with fallback to png.
• Link should return back to the home page https://kingjames.bible/

Fix vertical scrolling issue in Opera Mini

This happens when a verse is selected as in https://kingjames.bible/Ruth-3#3

The 'display:fixed' CSS renders in the middle of the page where the JavaScript attempts to ScrollTo(...).

Implement browser side routing

Add <link rel="canonical" /> to all html pages

"As a search bot I would like to discern between the beta and production websites."

The beta and production website will both have canonical link relations to the production site.

See https://webmasters.googleblog.com/2013/04/5-common-mistakes-with-relcanonical.html for details.

Implement CloudFront logging to bucket.

This will supplement Google Analytics for ebook downloads and plugin usage like VOTD.

Will also help with crafting missing redirects.

read_the_bible

Basic browsing and reading of the bible.

Add nav menu to home page and markdown pages

The navigation is as follows:

Book Chapter Page

1. Home
2. Previous, next chapter
3. Book - to select a different book
4. Chapter - to select a different chapter within this book
5. [Future] Search
6. [Future] Hamburger (?) for misc navigation.

Home Page

1. Home
2. Read -> Goto John 1
3. [Future] Search
4. About
5. Help
6. [Future] Hamburger (?) for misc navigation.

Help/About Page

1. Home
2. Read -> Goto John 1
3. [Future] Search
4. About
5. Help
6. [Future] Hamburger (?) for misc navigation.

Add Google Analytics tracking bug to each html page

Remove about footer