I've launched a Bible site, built on Clay, at (PFG). Currently, it's only an online KJV Bible with a search engine. I plan to add more features in the future, such as commentary, discussions, and open blogs. Check it out and let me know what you think.

PFG is using the Potter theme, which was the first theme I built using ClaySS. The Bible app was an old Xaraya module I made about 15 years ago, which I updated and converted to a Clay app. The search engine is the greatest improvement over the old Xaraya module and returns better results than any other online Bible I've tried. The search engine also breaks down the results by Old/New Testament and books, which allows you to more easily filter results.

The upgrade to Clay 1.3 is now complete and everything should be functioning as normal.


  • Markdown support in Blog and Comments
  • New ClaySS sass-based CSS framework (no Bootstrap)
  • Vue.js support in all applications (no JQuery)
  • New admin friendly Navigation plugin (top navbar)
  • Vision 2 theme replaced Vision theme
  • Refined privilege system
  • New Blog app layout

We love markdown :)

Potential Changes Coming for Clay 1.3.1

Clay 1.3 brings a new frontend system and will likely before the last major version before Clay 2.0's beta. That doesn't mean I don't have more work to do in Clay 1. The Pages and Contact apps are on deck for 1.3.1, as well as another navigation block and some new plugins. I'm not sure what all will make it into the next update, but I plan to round out a few features before 2.0.

I have some privileges to finish adding, but as you can see, the site is back up. Once I'm finished, I'll go into some details about the upgrade.

I'm in the processing of upgrading the site. This should take less than an hour, but I'll be doing backups first, then the actual upgrade should be fairly quick.

1:08 am

I've been working on my car this week, so no coding for me. The good news is I think its fixed. I'll find out on my way to/from work tomorrow I guess. I hadn't been driving it, but I got the OBD codes to clear tonight and it's running a lot smoother. I had gotten a little lazy on maintenance and it made me pay for it. I'll have to give it more attention and maybe I can do some preventive maintenance. The last code it was showing is no joke, so hopefully I ran it down to the correct part and it wont be back. If not, I may have to do some internal maintenance, which isn't exactly my forte.

11:14 pm

I finally got to work on Clay more. I've fixed a few bugs and small issues here and there. I ran into an issue with the delete hook for markdown deleting all markdown copies of entries, I guess I probably hadn't tested that very much. It appears everything is ready for the upgrade here.

I also did some minor updates on a few apps to fix  some uniformity issues. I have some more testing in the Bible app, which will go on a new site. That's the only thing preventing me from upgrading here right now. I'll probably run one more local upgrade, just to make sure everything is good. Hopefully by Wednesday I can do it here for real.

2:12 am

After a lot of thinking about it, I really want to build a social network. Everyone seems to tired of companies abusing their power. I think if the right solution came out people would leave sites like Facebook by the millions. I'm going to give it shot...

2:05 am

Well, I had some work stuff come up this past weekend so I wasnt able to finish testing for the upgrade. Tonight I should have finished it, but i ran into some problems that ended up being a simple file permissions issue. I was really concerned before I discovered the mistake, because my dev build worked fine, but the upgrade kept crashing for no apparent reason. 

I rewrote the same few lines of code every way I could think of and it ended up not even being the code. Oh well, at least I have another improvement to work into 2.0 now. Tuesday I'll try again with the issue tonight fixed. Upgrade "week" continues for now...

12:37 am

First round of upgrade tests have gone well, no major issues yet. The new blog layout looks nice and I really like the new navbar. The only issues I've found are in ClaySS and they are minor. Even the mobile display looks good for minimum test cases during development.

One thing I've noticed was held over from a previous upgrade: when I merged blocks into plugins for 1.1, I did a fresh install and imported the old database. Well, that meant the blog app id changed, so the comments app recreated all of the threads for the new blog app id. It didn't hurt anything, just meant there were a lot of unused threads in the database. In the future I'll probably add a prune feature to remove unused threads, but for now I can just delete threads assigned to the old blog app id.

10:58 pmUpgrade week?

I'm doing some upgrade tests this week, so if all goes well, I may be upgrading the site. This is one of, if not, the biggest upgrades I've done on Clay, so I'm not sure what to expect yet. I'm doing the testing locally, so (hopefully) there wont be any downtime. This is the upgrade from Clay 1.1 to 1.3, so if you've been following the blog you have an idea how much work has gone it.

1:00 am

Clay 1 now has over 1200 code commits on github. I've been working on rounding out Clay 1.3 and I'd planned on updating the site today, but I got sidetracked working on the Pages app and then some other things came up.

On my marathon to Clay 1.3, I forgot to update the comments app, so that is what I've mostly been working on lately. A lot of comment systems, that work with as a plugin, create orphanned data when something they are attached to is deleted. Clay supports a delete hook, which resolves that, so I've made sure it is supported by the comments app. 

Something interesting I've done lately is hook a plugin to a plugin, by hooking a markdown plugin into comments. It works perfectly, even the update and delete hooks. 

Other than those things, I've been working on my Bible app. It is coming along and I  plan to put it online when I upgrade to 1.3. It'll also drive a few other apps in Clay 1.3.x, such as categories and pages, maybe even a simple forum. 

Finally, I also plan to build a store front app in the not so distant future. I'm not sure what I'll sell yet.

Our story begins like no other: a message is typed on one computer and then sent to another. It wasn't even sent to another person. When Ray Tomlinson sent that first email in 1971, to himself, he began something that has forever changed the world.  It was before the Internet, but it was a step, a step among many beginnings that has shaped the digital world in which we live.

Philosophically, every action has an effect, an affect, and a return.  We are finite beings and we see the world in a finite plain, but the reality is beginning is infinite and end is infinite. The digital world we live in provides infinite possibilities, but we are so consumed by the finite now, that we lose sight of the beginnings and the ends.

The Internet today is seen as a few conglomerate services provided by seemingly infinite corporations. The Internet is Facebook or YouTube. It's Google. It's Netflix. It's Amazon. I remember when it was Compuserve. It was AOL. It was MySpace. It was Digg. It was Yahoo! We built PHPBB forums for our friends. We built GeoCities web pages. It was infinite, it was beginnings. 

We look at what we have today and we think, "this is it, this is what we wanted." Just as we did when we signed into AOL or committed our code to CVS. That wasn't it, it was only what we had. This isn't it either, it's just what we have. The Internet is changing as much now as it ever has, we are infinitely on the cusp of what we want it to be. One day we will look back at the Internet we have now and marvel as much as we can looking back today. 

The future of the Internet isn't a single social network. Facebook is not the end, at least not the only end. It's just a beginning of many beginnings. We have come too far for that to be true and we haven't gone nearly far enough. The future of the web is social, just as one of the first beginnings was when Ray Tomlinson sent himself an email across a room. 

The inception of the social web is upon us, we are on the cusp of what we want. We don't need a social network to build it, we are the conglomerate, we are the social web and what we build will only be a beginning.