Second Concrete Post

This is a post that should show up on my Concrete website.

Hello, world!

I am on the intarweb!

This is the post that was put up as I tested out the Zend framework for connecting - it came from the command line :)

I think that this is working, but the more that I dig into it, the more difficult it seems like it's going to be. It's not too hard to actually bring up the posts, but it does seem really slow. I'm not sure if that's just my server and connection, if it's google, or if it's the framework.

Then there's the matter of display - right now I'm just doing a loop over all the entries for a given blog, that could be part of the speed problem. I'll need to come up with several different formats for the output, as well:

• Archives (monthly, yearly, weekly)
  
• Tag Cloud
• Recent Posts (full, title+short text, titles only, date only - nav list on the last two?)
• Posts by Category - same as recent
  
• Single Post

Of course, the next question is posting and commenting. That gets into the logging in questions, too. Right now, I'm saving the username and password in the database and submitting it as plain text. There is a method for doing a round-trip sign in, so I'm going to have to run that and check against the session. New post link will have to appear only if you own the block.

I wonder if I can use the concrete content editor to submit the blog posts, too? It seems like this would be a much nicer interface than this stupid one on the blogger site.

I'm not sure what the real benefits of this are over just creating Concrete pages. I guess the posting and feeds and discovery - your content is more accessible. You could email posts in and have them show up on your site. It seems like twitter would be the next step, though I'm guessing there are a lot more APIs out there to get into.

First post

One thing that I've noticed on the Concrete forums is that people want a blogging component - I'm going to try to set it up with blogger using the Zend framework to communicate with the blogger back end. So basically, concrete content editing interface submitting to google - it should be a good way to get started on some further integration with google.

Anyway, this is the first post on the test blog - have to have something to pull out of the data, right?