Presentation is loading. Please wait.

Presentation is loading. Please wait.

Michael Atkins. Note:  This is a non-technical overview  Some light technical background is given, to put things in context  Some of the content is.

Similar presentations


Presentation on theme: "Michael Atkins. Note:  This is a non-technical overview  Some light technical background is given, to put things in context  Some of the content is."— Presentation transcript:

1 Michael Atkins

2 Note:  This is a non-technical overview  Some light technical background is given, to put things in context  Some of the content is included for completeness, and will not be dwelt upon  Demos and extended explanations will be given for the more typical “development” areas

3 Geek n. \ ˈ gēk\  an unfashionable or socially inept person  a knowledgeable and obsessive enthusiast

4 Development is not a Dirty Word  Development frightens off many managers and decision-makers  Excessive technical enthusiasm is counter-productive  Communication and understanding are crucial  Technical wizardry must translate into business benefit

5 Types of SharePoint Development (I)  “Normal” SharePoint Customization  Using Templates  Branding and User Interface Development  SharePoint Designer List Views and Data Forms  Business Intelligence  Metadata / Content Management  Advanced Search Customization  InfoPath Forms

6 Types of SharePoint Development (II)  Workflows  Accessing External Data  Development of Web parts  Event Receivers  Timer Jobs  Client-side Data Access  SharePoint 2013 Apps

7 Technologies and Tools  Browser  SharePoint Designer  SQL Server  Visual Studio

8 Where the Action Happens  Browser  SharePoint Server(s)  Database  External Systems  The Internet

9 Why are Custom Developments Needed?  Improve access to and manipulation of SharePoint (and other) content  Modify the user interface to suit users’ needs Make the users’ jobs easier!

10 Buy or Build?  Good Question!

11 Getting Easier to Install  It is much easier now for Site Collection Administrators, as opposed to Farm Administrators, to install solutions

12 What to Watch Out For  Cost of development  Reliability of developers  Availability of skills  Surviving SharePoint version upgrades  Managing expectations

13 The Key… … is to have small(ish), focused developments, working with SharePoint, not replacing it

14 EXPLANATIONS AND DEMOS

15 What?What? Why?Why? “Normal” SharePoint Customization  Logos; Themes; Custom Lists; List Views; Wiki Content; Web Parts; Navigation  Quick and easy (!) to get a working Intranet going

16 What?What? Why?Why? Using Templates  Lists; Sites  Create Consistency; Re-use work; Quick deployment

17 What?What? Why?Why? Branding and User Interface Development  Master Pages; Custom CSS; JavaScript  Corporate identity; Ease of use; Layout conveys logic

18 What?What? Why?Why? SharePoint Designer List Views and Data Forms  Custom Forms; Advanced Views; Composite Pages  Unlock power of data, through presentation and linking data

19 What?What? Why?Why? Business Intelligence  Summaries; Charts; Visualizations  Quick Access; Relevant Data; Visual Impact

20 What?What? Why?Why? Metadata / Content Management  Informal Tagging; Managed Metadata; Retention  Retrieval; Accuracy; Auditing

21 What?What? Why?Why? Advanced Search Customization  Custom Presentation; Custom Processing; FAST Search  Convenience; Intelligent Search

22 What?What? Why?Why? InfoPath Forms  “Pretty” (rich) Forms; Data linkage and lookup  Ease of use; Richness of content

23 What?What? Why?Why? Workflows  Enabling Business Processes within the SharePoint environment (often using Tasks)  Prompt alerts; Keeping track; Reporting

24 What?What? Why?Why? Accessing External Data  Business Connectivity Services (BCS) - External Data living in SharePoint  Easy lookups; Data kept up-to-date

25 What?What? Why?Why? Development of Web Parts  Custom Web Parts can access and display data in many different ways  Where SharePoint interface not fit for purpose

26 What?What? Why?Why? Event Receivers  Code that runs when something happens in SharePoint (like a new Item or Document being added)  Access or create content outside of current site

27 What?What? Why?Why? Timer Jobs  Code that runs at set times within the SharePoint environment  Useful for regular tasks, such as synchronizing data

28 What?What? Why?Why? Client-side SharePoint Data Access  Accessing SharePoint data directly, without using normal interface (JavaScript, desktop apps)  Use or interact with SharePoint data outside of normal SharePoint Lists or Web parts

29 What?What? Why?Why? SharePoint 2013 Apps  Downloadable “apps” that do useful things in SharePoint (extension of client-side data access)  Easy to distribute and install; Safe to run

30 Contact Me:  Mike Atkins  iTrend Business Solutions  083 953 8548  031-261 8000  atkins@itrend.co.za atkins@itrend.co.za  www.itrend.co.za


Download ppt "Michael Atkins. Note:  This is a non-technical overview  Some light technical background is given, to put things in context  Some of the content is."

Similar presentations


Ads by Google