I normally work on an ASP.NET site, which has its own ASP.NET Membership and profiles. Salesforce was introduced to the company to provide a CRM. Initially the member profiles that the site creates are then copied by a scheduled job into Salesforce as contacts. Salesforce has now started to be used for other aspects of the company, like creating solutions for customer support.
I'm now looking at providing a public help and support area to provide a public knowledge base, and private ticket support area.
I believe I can do this with a customer portal/Knowledge and provide the following features:
- SEO friendly knowledge base urls.
- Integration and single sign on provided by the original ASP.NET site.
- Maintaining a consistent look and feel between the ASP.NET site and the Salesforce Customer Portal.
- Translatable into multiple languages.
- Working via support.companywebsite.com rather than companywebsite.force.com
I look at the site like support.activision.com and all of this appears possible, but as I'm unfamiliar with Salesforce I don't know what work went into it. I don't know what the usual development time would be for a project like this. I'm thinking from the point of view of an experienced Salesforce developer, rather than someone like me who has no knowledge of Salesforce, who would be having to learn about the system as he worked.
My understanding is that I would create html/css static resources to upload to the customer portal, and probably use SAML to provide authentication between the ASP.NET login page and the Salesforce customer portal. I would have to create Salesforce contacts at the point of registration on the ASP.NET site.
Could someone give me some indication of how long the Salesforce part of this would take? Is it a common scenario? What problems should I be aware of?