Outgrowing your static website? A Content Management System (CMS) is the next logical step. These systems offer a long list of benefits compared to static sites, such as reusing content and layouts, centralized access control and user management.
Plus, the advantages apply to different roles – from content creators to editors to developers. Now identifying who’s going to fill these roles within your organization? That’s just as important as which CMS you choose, too. But let’s take it from the top.
Chris Kulish Posted in: CMS, Content Strategy, Data Integration, Digital Experience, IT, Programming, Software, Software Development, Software Maintenance, System Architecture, Technical Architecture, Technology, Technology Platforms, Targeted Marketing Programs, Technical Enablement, Technical Strategy
Building a content management solution goes beyond just picking a Content Management System (CMS). It starts with asking the right questions during discovery, selecting the right tool for the job, creating architecture, and setting the stage for development.
HealthKit, HomeKit and Swift, oh my! We totally nerd out on this episode as our panel of developers and architects review WWDC 2014, discussing the upcoming features of Apple’s Mac OS Yosemite and iOS 8 platforms.
You are in the process of building a super cool iOS application. For some reason or another you find the need to save either a view or the entire screen as an image programmatically but you are unsure of how to accomplish this. It is a good thing you have ran across this blog post!
At Sundog we use Salesforce as a solution on a number of different projects. Its a powerful CRM tool that allows developers to make robust systems. But when the project calls for allowing non-technical users to create and manage content, in addition to leveraging the data stored in Salesforce, we reach for another tool in the toolbox. Enter Site.com.
When we’re talking about cloud based platforms and applications, there’s one word that should be a part of almost every project for an enterprise: integration. Easily being able to integrate multiple types of systems quickly and without hardware is one of the best features the cloud has to offer.
Most every language and platform you develop for has its own boilerplate code—code that has to be included with little or no change. As a developer I appreciate tools that help remove boilerplate code.
Sharing a Salesforce org for development can be a challenge. I’ve heard about some teams successfully using version control and continuous integration in their Salesforce development, but their process may not work for every team for a variety of reasons. I’d like to point out a few issues in particular when sharing development sandboxes with other developers.