I've moved all of my private repos. It's not because I don't trust Microsoft... it's because I don't trust their developers. I don't think Microsoft would do anything to jeopardize their new love with the FOSS community. On the other hand, in a world of quotas and time restraints, I dont want my software in the hands of another software company as big as Microsoft. Eventually I'll host my own private repos.
I've been working on a few things in Clay 1.3 and getting ready to shift gears for a stretch of Clay 2 development. In Clay 1, I'm working on DataObjects (DO) and a Forum app. DO is a way to group features by objects and allow apps to use them as if they were native to the app. At least that's the abstract description. The Forum app is just a simple message board, which uses the Comments app for threads.
The Clay 2 work will mostly be rebuilding the installer to be an app within Clay, rather than a separate entity using the Clay Framework.
Microsoft has announced it has acquired GitHub for $7.5B and a lot of people aren't happy about it. I've been looking into alternatives for my private repositories, but I may leave the public ones on GitHub. The problem is I can see some other corporations reacting by making similar moves.
I've been evaluating new services, both by quality features and potential acquisition cost to determine if I should move or if I'll just be looking for a new service again soon. I predict an explosion of growth (at GitHub's expense) soon for a few services, so I can see how one service in particular could exceed $10B in the potential acquisition cost in the near future.
I may have to take my private repos off the grid. I don't want to, because sites like GitHub are cheaper to use than hosting the projects myself. There are also few choices on the open source front for direct GitHub alternatives. Is Microsoft trustworthy? Unsure if I want to find out.
One of the tools Clay has been missing is an analytics system. I'm working toward adding one, but I don't want to use Google or any of the big corps. I have some simple pieces in place, but nothing competitive. I may go with an integrated version of an open source tool, which means I'll probably contribute some ideas to it. I'm still looking for the right one. I'd rather not fork one, but that's a possibility as well.
I've been working on DataObjects for Clay. It's an extensible library that helps you build apps faster, by giving you a unified api to handle data and relationships. It's like scaffolding, but better. I had been reserving Clay 2.0 for it, but I decided to begin implementing a light version for 1.x to aid in the upgrade process in thr future. I don't plan on building it into every Clay 1.x app. In the future I plan to replace the plugins system with DataObjects, but for now it will use hooks to and from plugins as an interface into apps. I'm liking the direction so far.
My new hobby is checking logs for hackers. Kind of makes me feel important. I didn't mention my improved logging features in Clay 1.3 maybe? If they keep it up I'll start sharing their information... I'm sure they are just bored, but I get bored too... ;) Who knows? Maybe some of my friends want to have fun too. I'm assuming you know English, if not, oh well.
ProfoundGrace.org will have Bible commentaries one day. It's going to take a lot of work, between building the functionality into Clay and formatting the texts. To help things along, I made a github repo to store the texts as markdown in the meantime. Check it out. I'll be adding texts when I have time, but the formatting is a work in progress.
I've launched a Bible site, built on Clay, at https://profoundgrace.org (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.