What Is Flippant Pixel?
It’s a place to put stuff. The stuff was made by an American named Adam. (That’s me.) All software not subject to someone else’s copyright is licensed as public domain by Creative Commons.
I made this site after developing whack. The blog is being hosted at Blogger. It uses SimplePie to pipe in an Atom feed. I have other goals for the site as well:
#1. Put the site structure in Cake. This should be a good exercise, a good foundation for all the other stuff I develop here and mod_rewrite will clean my URL’s up nicely.
#2. Manage the content with Textpattern. Since WYSIWYG editors do not and will never work as advertised, I'd like to take this lightweight markup-driven CMS tool for a spin. I’d also like to compose in the Textile lightweight markup at Blogger, but that’s a low priority.
#3. Touch up the design a little. For one, this should be an ordered list. There are also some little aesthetic tweaks, like the redoing the buttons, adding a sublte gradient to the background, finding a work-around for my Firefox font-rendering problem and maybe a doing background photo for this page.
#4. SEO it. A day at Google’s Web Master Central should be sufficient. I might study SEM, but that industry gives me the creeps.
#5. Extend the blog’s functionality. In order to post comments or look at a structured archive, you have to click on a link that takes you back to my blogspot page. I don’t like that. Everything should be internal to Flippant Pixel and be neatly organized. This will probably require a second level of navigation, which in turn will require additional CSS. I will definitely need to reverse-engineer Blogger’s comment tool as well as significantly extend SimplePie.
#6. Project: Chord. This is an idea I have for browsing XML files. I’ll probably end up using some combination of Prototype and script.aculo.us for the interface. The user input will be pretty substantial, so I’ll try session data, but may have to use my database.
#7. Add another style or two. Using cookies to remember which style the user picked would be cool.
#8. Add a download source link. What's the point of making this public domain if there's no way to see the source code? And why am I asking rhetorical questions?
#9. Design a favicon. I like favicons. There. I said it.