I've still been working on ClaySS, trying to get a baseline in there so I can begin working it into the 1.6 alpha codebase (coming some day). That means I am actually going to release 1.0 soon. I've still been holding off for the Pages and Contact apps, but I'm about to shift toward getting those finished, then there will be some clean up, a new menu and we'll see where we need to go from there. I'd imagine at least 1 beta release will come out, but I don't see a lot changing after that.
I've kind of made a 1.0 release my own mental hurdle, so I need to get it out so I can move on!
I've been working on ClaySS, have the base in there, just need to add some default styling. I'm not to the point where I've started making a theme yet, but it's getting there. ClaySS wont be used in 1.0-1.5, it's for the next major version, which starts at 1.6. It could take a while to finish...
I've been working on the Pages and Contact apps. The Pages app will just be for making custom pages, for now. Eventually it will replace the System app as the default app.
Hope everyone is having a good weekend and please remember to keep the areas affected by Hurricane Harvey in your prayers.
I've been working on a new themeable CSS framework and today I named it and created a repo: ClaySS. Who saw that coming, right? 😉
ClaySS will replace Bootstrap and jQuery in Clay 2.0, but will be available as a standalone SASS package on npm. ClaySS is based on iotaCSS, so you will be able to use iota's components for React, Angular, and Vue as well.
I've been torn on whether or not I wanted to go this direction, but with my focus shifting away from PHP somewhat and more toward node.js, I think it's time to create something different. Bootstrap is awesome, I've used it for several years and it has in a lot of ways shaped the way web sites look today. On the other hand I think it's dependency on jQuery is holding us back. They've both served us well, but it's time to move on.
Clay 1.0 will continue to use Bootstrap, as it is built into all of the apps and themes. Clay 2.0 will be very different in a lot of ways, I think moving away from Bootstrap at the same time is the best approach. I still plan to write Clay 2.0 in PHP, but there are some twists (not spilling the beans yet).
One of my projects is a Baptist web site I'm launching "soon". If you've followed me over the years you may recognize the name, but it's been sitting idle for a while.
I've found it's easier to build features into Clay and other projects if I have a real world use for them, so I'll be expanding into several different directions. I'm learning a lot, so I think it's worth it just for that, but I'm also building a nice tool set for future projects as well. More to come on the Baptist site, it'll start small and grow over time. It's really just my personal commentary and a study site, but it'll also be open for other contributors as well.
I've been fairly busy lately, a few different projects going on at the same time. No complaints though, it's good to stay busy. I look to expand the widgets app with some additional APIs and blocks over the next few weeks. I also have some Zillow features to add, probably over the next week. Of course there are the usual suspects within Clay to finish as well. I'll get to them eventually. After working with several CMS' over the last couple of weeks, I think one of the things I've neglected in Clay is a good menu system. I have the utilities in place to build one, but never implemented the actual menu. I'll have to work on that as well.
Clay now has a Widgets application which allows you to use APIs from 3rd parties on your site. It isn't feature complete, but you can view the Zillow Reviews API on my client's site at L&M Realty. If you get an error, that's because Zillow hasn't approved my request increase and L&M gets a lot of traffic. I haven't finished the template for the API, but right now it splits between team requests and agent requests. If multiple agents are requested it will split them into tabs, which I haven't finished implementing.
I'm working on an app that will allow you to build portable website widgets using 3rd party api's. It'll also provide hooks within Clay so you can plugin the widgets to other apps. Any requests for api's to use?
I'm officially a New Mexico business owner. I'll be doing web sites, apps, customization and consulting. Pretty excited :)
Part of the last few things I'd like to implement before the 1.0 release are some SEO optimizations. Clay itself gets indexed really well, but the theme doesn't have all of the meta tags that help page rank and the page titles could be adjusted to improve search rankings. Most of the optimizations will be in the theme for now.
Once I branch off into the 2.0 dev builds (1.6+), I will be implementing a router to allow human friendly URLs. It won't take a lot to do it, since I most of the utility functions are built into the core and apps already. That will be a big SEO improvement.
I'm working on finishing the contact app and pages app, so I can release Clay 1. I want to also finish the generic menu block, but that may just be an update after Clay 1. I'll be back porting some things into 1.x once I start on Clay 2. I have some other projects coming up so I'm just trying to put time into Clay while I can.
I've finally enabled user registration and comments. Took a while longer than I planned. Register and try it out. Let me know what you think.
Was looking for a tweet to test Twitter embeds and saw this...