Recently, a WordPress-based web portal was built for a technology company to serve the needs of several thousand partners and resellers worldwide, which included providing access to confidential documents for registered users. The new portal replaced a very basic site they had built using Salesforce’s “Partner Portal” offering. As such, we had to evaluate the options for logins to the new WordPress site:
Given the current proliferation of mobile touchpoints, we are often tasked with helping clients create mobile roadmaps and strategies. Inevitably, we are asked if there is a way to build content or functionality once and deploy it on a variety of different mobile platforms. The answer, of course, is yes. In fact, there are several ways, and the benefits of doing so vary from a more streamlined development process to higher adoption rates to lower costs. However, when is the right time to use cross-platform solution? What kind of requirements lend themselves to this simpler approach? When is the cross-platform approach actually simpler than developing for native applications?
In early March, we heard a new SDL Tridion User Interface 2012 was arriving, and we received an invitation to one of the SDL Bootcamps where Mihai Cadariu, Principal Consultant at SDL Tridion, demonstrated the new interface along with the installation and configuration steps.
Although there is no official name for ‘the new interface’, existing SDL dev folks will be somewhat familiar with it as it was formerly known as SiteEdit. This new UI looks very promising with new cool features and also incorporates an architectural change. In addition, from a business user’s standpoint this probably is a much-needed fresh approach with respect to the authoring arena as content editors and authors need not use the traditional CME interface.
As you’re surfing the Internet you see a fantastic article about how to make the perfect cat video. You also want to save some photos from Google Image Search and store them somewhere you can access on the go. What about recipes? Do you have a recipe box gathering dust because you search the Internet now for recipes? Where do you keep all this stuff so you can easily reference it later?
In this post, we will go over how to set up the Deployment module (http://drupal.org/project/deploy) on Drupal 6.
The Deployment module is meant to provide an easy way to stage and push content from one server to another. But, as the project page states, “There are a lot of moving parts and while it’s not “hard” to setup, there are several steps to go through.”
I regularly advise clients as to which hosting provider to utilize for their new website or web application. The choice is wide and varied, and there is no “one-size-fits-all” solution that I point to every time. If you are currently considering your hosting options, or are looking for a place to start your research, you may well find this brief guide helpful. I’ll start off with a definition of terms, then detail a small checklist of questions you will need to answer, and then finish up with a brief summary of my preferred hosting providers.
Having the ability to quickly deploy a live microsite is becoming easier and easier. Microsites can be great choices for supporting strategic launches, special events and limited Enterprise initiatives. Microsites allow easy inclusion into existing sites as a portal element or as a jump site. Since the lifecycle of a microsite tends to change frequently, developers need a way to ensure quick and perhaps timed deployments. In this blog post, I’ll cover how to quickly and concisely package and deploy the GAE (Google App Engine) application to create a microsite.
2011 proved to be an exciting year, and we anticipate 2012 to be even better. Take a peek at the trends we’ll be watching in 2012. Happy Holidays!
Mobile Payments Accelerate
Wallet? What wallet? I have my phone.
There is no doubt the penetration of smartphones has changed the way we communicate, inform and entertain each other. Mobile devices have also changed the way we shop—helping us locate, evaluate and recommend every kind of product or services imaginable, but we still have to pull out the plastic (yeah, some still carry cash) to transact… Well, that final frontier of the commerce experience is also changing, and fast.
For now, the winner is clear.
We recently uncovered an excellent example of the immature state of Drupal 7 versus its well-established predecessor Drupal 6. We noticed early on in a recent project that the underlying data structure for content had changed in Drupal—there is now a component of the content-element data object that stores a Language ID for each value, which didn’t exist in D6 (granted, it’s always set to “undefined”, but it is there). This means that, in theory, individual content elements can have different language values, even in a single node (e.g. /node/123 can be displayed with English or French content).
Recently, my frustration with Tomcat and Jetty set me off Googling for possible alternatives. After some searching, I came across a relatively new open-source servlet engine called Winstone. I think this server may well be a great replacement for both Tomcat and Jetty, at the very least as a development tool. Before I delve in to more detail on Winstone, let me share a little background on Java servlet engines, and my particular issues with Tomcat and Jetty.