Even a decade at least after developing the first iteration of Battle Blog I'm still improving it.
An astute reader, probably the reader, of Explaining Myself noticed that the "new post" notifications used an indirect link back to this website.
This broad link back was fine before I added a permanent-state "elastic" feature to Battle Blog, which is basically a Battle Blog setup mode that turns Battle Blog into more of a static website than a blog. I refer to this make up as "repository mode".
As a blog, the latest entry is always the top post, so the previous indirect method of calling subscribers attention to it was good enough. A publisher makes a post, an email goes out that includes a generic link back to the main landing page, and users spot the post when they do. Easy-peasy if not a bit programmatically lazy.
But when the platform is set to its repository mode, everyone lands back at the main page that never changes. So, there's confusion.
I am hoping that as of this post that I've modified the outgoing message to always include a link back to the actual entry so that no matter which mode it's in, subscribers will see the content they opted to be tipped off about, directly.
This is the first post going out with the fix, so, I may wind up tweaking it further if it doesn't work as planned.
 By Dave for Personal Blog.
Comments (0) | Promote (0) | PermShare | Focuses (2)
Status quo institutions are attempting to kill the hyperlink and relegate you to social media. Resist by sharing this content's hyperlink. To share this content copy the URL below to your clipboard and paste it to the medium of your choice. Never let the world forget about the World Wide Web.
The COPY button may not work in all browsers. If not, rely on clicking on the box and pressing CTRL+A, CTRL+C to get the link into your clipboard (or long-press if you are on mobile device).