This is the current status of my latest project. Which publishes a Web3 blog from my personal Hive blockchain content.
Illustration created by me using Canva with the prompt, "A programmer's assistant updating a project status page".
Keith's Hive Frontend takes selected content from the Hive blockchain and presents it as a personal blog. Adding features that include:
This status page records the current development of Keith's Hive Frontend. Together with some planned improvements.
During the development of my Hive Frontend, I identified some Issues. Which I documented using the GitHub system. But I don't want a formal issues system unless I have a development team. So I'm moving my log of issues and their resolution onto the blockchain.
I need to remove AdSense from my .net domain. Then switch it on individually for sites that have 50 pages (or other quality assessments).
I overcomplicated image handling when I tried to make this tool accept as much content as possible. But the best way forward is to use the best image formats in the original blockchain post. And accept that original post editing is inevitable for the best presentation of evergreen content. Therefore, I'll remove the image enhancement plugin.
Also, I need to ensure that my deployment routines include steps to verify Lighthouse scores before publishing and promotion.
See Hive Frontend Content Filters (in preparation).
As part of this issue, I intend to enhance Keith Taylor Web3 Blog Search with Refinements for each tag that I want to identify as a different section.
I'm developing Keith's Hive Frontend as my own personal Web3 blog. However, I have always intended to open up this project to other users.
My progress on this issue is entirely dependent on feedback from other Hive users.
Currently, I am completing the list of issues above.
You have learned how I'm developing Keith's Hive Frontend as a personal blog tool. Next, you should think about how this might be relevant to your blogging needs.
Please share your questions, experiences, and opinions in the comments.