What do I love about working at Sundog? The tough challenges that our clients bring us, not to mention the way Sundoggers challenge ourselves. Around here, we’re all obsessed with quality and the drive to make our clients heroes in everything we do. And as a Systems Architect, that means I get to do some really cool things.
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.
We’re approaching a crossroads for the CMS world: Most systems are intricately linked to the desktop experience and, as we all know, more organizations are wrestling with how to accommodate their growing mobile audience.
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.