A little bit on what I'm working on.

So I got involved with this interesting project. It's a small, self funded startup aimed at replacing Wix and Squarespace with something a little more interesting. The original idea was to offer something that would allow customers to build websites with a modern website builder, but on the back end, offer more of those traditional consulting services. And they wanted to build a cms that would support that. 

The project takes an interesting perspective on content generation and content delivery. Rather than using a CMS to generate and assemble websites and web pages the way everybody else does, the cms would be used to to generate what amounts to a group of static html pages. Everything on that of things gets optimized for speed.

Pages get built, and stored in local source code repositories, and the repositories get pushed and pulled into the places they need to be. For most sites, it'll be a real time process. The database on back end only stores meta information about the content, and enforces content integrity in a way that's both interesting and novel, in my opinion. In other words, as a customer, you'll never be able to unintentionally break anything. And code repository handles the revision history, providing some pretty robust functionality.

But the best part, and the thing that's more interesting about it is how we're using the blockchain. The assumption here, is that the way things are going, larger media files are going to become more common on normal websites in the years to come. The initial test clients we're lining up all have interest in video and audio broadcasting over the internet, and we want to give them a full service media solution in one place. And, we want to give them these tools in an interface that's both simple and familiar, drawing ui inspiration from common cms tools that customers are already familiar with.

The media files created get pre-processed on our servers, generating things like thumbnails and wave patterns that get tied to the media files the same way the system stores metadata about other types of files in the system.  And then after crunching and optimizing the files, we throw them into IPFS. That content gets seeded by vps images and private computers we have sitting in the office, each one running an ipfs node. 

And then, when the content gets implemented, things like, a video being embedded into a web page, or a blog post getting generated, that content gets aggregated to Steemit, providing value for the the larger network.

The CMS development is going pretty smoothly. Looking at implementing the blockchain features in the next couple of weeks. 

So far at least, everybody's having fun, and I'm hoping to build a team that's a little bigger, so I'm not spending my entire waking existence on the thing.

One step at a time though.