Have you been promoting JavaScript? Did you even know that you could/should be? It just got easier to help if you are using ExpressionEngine.
At JSConf 2010, Chris Williams started a project called PromoteJS to help get bad JavaScript references off the web. You will know how important a cause this is if you have ever done a Google search for JavaScript documentation or help. The top results are deplorable. (NEVER use w3schools.)
Last week we released a new design for Solspace. Everything went over pretty well, aside from some small hiccups. Not bad for a new site design launch. I am quite proud that we have a new face as we are very dedicated to our work and our old website just didn’t reflect that. Good change.
Like the blog post about the redesign suggests, it is hard to work on your on self image when you are spending all of your time trying to make sure everything else is taken care of. Customer service, bug fixes, and fresh products are first and foremost, because that’s what’s most useful to customers. However, a good face is very important.
So, I finally decided to take the time to update my website to the ExpressionEngine 2.0 Beta.
This means that some of my stuff is going to be broken, but I can live with that. Going to improve how things are done and use better components this way. But the transition had a couple of small hiccups…
Upon redesigning this website, I decided I wanted to do a little more with the front page. The first thing that I wanted to accomplish besides a new look was removing entire posts from the front page and just having short snippets of each post so that there would be less scrolling and a reason to view the entry/comments page.
ExpressionEngine has a built in word limiter function that can be used on template tags that produce words. My immediate problem with using the word limiter is that it would cut off paragraphs without closing the paragraph tag. I also show a lot of code within pre tags and those not being closed screwed up the entire page layout.
