Filed under

frameworks

 

Coding Update #2: Front-end Builds Framework

A quick update for those who are interested and don't follow me on Github, I wrote this tool for people like me who write a lot of HTML/CSS at their jobs, and especially have to present those templates as deliverables. A lot of the times you're only responsible for the frontend development, so it's hard to get the benefits of server-side web development. In other words, you have to repeat yourself a bunch of times as you're coding, and it starts to get messy. I just hacked together something using XML and PHP to keep the content separate. There's not much separate documentation, just inline comments, but the tool is definitely usable (especially by those who understand basic PHP). A demo, also in progress, can be seen here.  

Filed under  //   PHP   development   frameworks   open-source   software   web  

Coding Update #1: Git, MVC, & .NET

I've finally started using my GitHub account. I've had it since almost a year ago, but only recently decided to dive into the Git commands in bash. The learning curve is definitely manageable, if you're not afraid to google. This sudden shift from SVN is mostly invoked by jQuery's move. A good amount of the source code I 'clone' for my own use (I'm not a fan of browsing for download links) is on GitHub, too. As awesome as TortoiseSVN is, GitHub just seems to have so much potential, at least over Google Code. 

I've also started venturing into MVC web frameworks again, mostly in PHP, since it's mostly what I know server-side. I'm going to redo the back-end for my site, so I can extend it with more flexibility and creativity. This will definitely be a long-term project, with a lot of long pauses and short spurts of activity. But it just plain sucks that I can't easily build new portions of my site without affecting or changing the old, because Indexhibit or WordPress are simply not designed to be highly extensible, from a development standpoint. They're also not really getting improved upon very quickly, at least in the rate their language platform (PHP) is -- which actually isn't that quickly. And as a side note, looking at the BuddyPress source--which sits on top of WordPressMU, induces powerful headaches. So I've just abandoned what most of the internet runs on; what do I want? 

Read the rest of this post »

Filed under  //   WordPress   development   frameworks   open-source   web  

Essay: Navigating The New Housing Boom

blogpost header: a city of markup, a house in focus with #fff hex on its roof

Websites are like houses. The creator of Django confirms this idea I've had in my head for a while. While I lack his experience working with the internet, and I have not worked in construction or studied architecture, I see the similarities in the processes. I also believe these similarities will can help us correctly defined the future of websites.

Definitions

Most websites are, or should be, functional, so they're rarely foremost works of visual spectacle. I am excluding the genre of the Flash-based brochure sites, as they are closer to commercialized movies. I am referring to sites that foremost deal with data: its storage, distribution, presentation, aggregation, and management. Since the internet is about interacting with information, it doesn't do much good if the information is static, like in a brochure site. Therefore I'm referring to sites where the data is very dynamic. Of course, it doesn't matter what the site does; sites do a lot of things, from tracking your life to being a game.

If making websites was about visual spectacle, it would be more like making a painting or a movie, all about the visual feel with little concern about supporting functional, non-linear interactivity. Rather, making websites is different and harder in two ways. First, websites, like other software that support user-interaction are non-linear. This changes a lot of the underlying creative thought process. Instead of just imagining the natural, cumulative, visual progression of strokes on the canvas or frames in the clip, you have to think of use cases, the variety of paths that branch and fork depending on what the user is looking for. The user is given too much interactive power for linearity to work.

And that's how, for a while now, I've realized like many, many others, the website of our time is actually software.

Analogies

And making software is like making houses. Both tasks take a very long time. There are numerous stages, and I'm sure, variations of processes for projects of various scale. There are many components and with them, are constraints. And these standards must be met, or the result is unusable. Just like poisonous Chinese drywall doesn't meet standards, make people sick, and devalue the houses they're in; a website where there are ads anchored to malware or flash banners that interfere with the layout and content upon mouse-over will drive away readers and actually lower revenue, thanks to ad-block features on browsers and userscripts. Or something as careless as forgetting user-friendly color contrast.

Read the rest of this post »

Filed under  //   WordPress   design   development   frameworks   usability   web   writing