SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

First let me categorize SharePoint consumer modifiers as below

  1. End Users - people who basically browse the portal and do operations like upload, download and navigate..

  2. Limited customization of the SharePoint Pages/lists through browser - creating pages/libraries/views, editing HTML, writing basic CAML etc

  3. Customization using SPD, ah must be knowing CSS3 and javascript/jquery to be a great SharePoint Branderrrr.

  4. SharePoint Administartor, a lot on configuration and troubleshooting.

  5. A good SharePoint developer should have indepth knowledge of ASP.Net, SP object Model, Client Object model, WCF, Workflows and Silverlight.

  6. The man I am talking about, A SharePoint Architect - what should this guy capable of, all of the above! Then what else, how to on Performance, Capacity Planning, Virtualization, Deployment etc?

Search is one important factor which I missed, definitely. Would like to understand what people think of "What a great Architect should know"?

share|improve this question

closed as not a real question by Anders Rask Nov 3 '12 at 20:13

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Here is a related post that should give you some… – user7400 Nov 2 '12 at 15:42

Browse other questions tagged or ask your own question.