SO I’m just wondering why you’d want to do it that way, which seems complicated, instead of just setting up his devotionals as (unique) future scheduled Posts? You could schedule each one of them to publish at midnight or a minute after each day on successive days. Then like from his Splash page to a “blog” page on which you limit the number of Posts to 1, and possibly list below or link to an archive of past devotionals?
Maybe if you explain a bit more about why you want to go the hard route, I could come up with something more beer-worthy.
🙂
Hi. Thanks for the help. As for doing things the hard way, it could have something to do with my upbringing. 🙂
On his splash page, located in the space where posts of a blog would normally go, he wants to put buttons/links with blurbs that correspond to a page of cops singing Taylor Swift songs, a page of cute cat videos, etc., and a button/link that would either take the click(er) to a page containing that day’s devotional or perhaps even open that day’s devotional right there beneath the button on his splash page.
His goal, and by extension mine, since I will be doing most of the “heavy lifting”, is to make it as simple as possible for visitors to his website to read that day’s devotional. For me, that means the least amount of clicks required, with the penultimate being that the devotional would be right there on the splash.
I think I understand what you mean by ‘scheduled posts’. A scheduled post could start loading at 12 a.m. on his splash, right? My fear is that this will entail me creating 366 different ‘posts’. Is that correct? If I created a page that would hold all his devotional, and then linked to them, it just seemed easier in my mind than creating a page and/or post for each one.
Hope this helps. And thanks again. And just kidding about the cops and cats. 🙂
