What’s Holiday Appropriate?
Here at ThoughtMatrix, we do a considerable amount of PHP development. We work with everything from Drupal and WordPress to Zend Framework, Concrete5, CodeIgniter and custom home-grown apps. It’s necessary for me to have a local LAMP environment so I can quickly and efficiently set up and work on new and existing projects. About four years ago, I made the switch to MAMP. The fact that MAMP was a completely self-contained LAMP stack appealed to me as I’ve had some bad experiences in the past using Mac’s native PHP and Apache—OS updates would wipe out the customizations I had made. Shortly after starting to use MAMP, I became sick of manually editing my hosts file and adding new Virtual Host directives to MAMP’s Apache config. Enter MAMP PRO.
The ThoughtMatrix team recently attended SDL Innovate 2013 in San Jose, CA. It was quite an impressive event, with people worldwide in attendance including both SDL customers and partners. Last month, Forrester gave SDL its top score among all vendors in the Experience Management category in its annual Forrester Wave report. To solidify that top position, SDL has rearranged their product and solution offerings and unveiled its new messaging for their Customer Experience Management (CXM) initiative during the recent SDL Innovate conference.
The CXM messaging revolves around three pillars—”Insights, Orchestration and Contextual Experiences.”
In a previous post—“Using Salesforce for Authentication”—I described an enterprise partner portal built on WordPress that used the Salesforce SOAP API for user authentication. As a result of the architectural design, all user interactions with the site took place on the partner portal with no distracting redirects to Salesforce for authentication.
There are a few more components needed for a fully functional portal authentication system, which I’ll describe further in this post. One commonly found feature on such sites is the “forgot password/password reset” component. Our aim was to keep the interactions with Salesforce transparent to portal users so we could focus their attention on our portal. We didn’t want users to have to perform repetitive activities with temporary passwords or log in/out of the portal or Salesforce.
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.
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.