1 / 13

CMS 2: Advanced Web Editing - Content

CMS 2: Advanced Web Editing - Content. Presented By: Katie Pagano, Special Projects Manager Steve Pont, Product Architect. Learning Points. Configure a custom Community Landing Page Customize the Recent Blogs Control Syndicate the Google Translate Widget across a Microsite

jordan-savage
Télécharger la présentation

CMS 2: Advanced Web Editing - Content

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CMS 2: Advanced Web Editing - Content Presented By: Katie Pagano, Special Projects Manager Steve Pont, Product Architect

  2. Learning Points • Configure a custom Community Landing Page • Customize the Recent Blogs Control • Syndicate the Google Translate Widget across a Microsite • What is an API? • Where can I find examples of API’s in use? • What does the Higher Logic API do and how can I leverage it? • What does the future look like for the Higher Logic API?

  3. What is this “API” thing I keep hearing about? • “API”: Application Programming Interface • An API allows data and functionality to be shared between Software Applications to enhance one or both Applications. • Multiple API’s can be utilized to create a “Mashup” Website.

  4. API Examples • Twitter (Web API) • Google Maps (Javascript API)

  5. API Consumer Examples • Likely – your AMS • MemberCentric!

  6. Design Considerations behind the Higher Logic API • Security and Context • What Data should be made available, and how should it be structured? • Multiple Connection Options, with flexible data representation • Ease of documentation

  7. Authentication • Token-based Access lowers strain on system resources, and speeds data retrieval. • Multiple Ways to Authenticate adds flexibility in how users can access the API. • Unique Security Keys will enable developers to utilize the API as different users from within the same system.

  8. What Data is Available • Events • Contact/Profile Information • Announcements • Discussions / Communities • Friend Requests • Messaging • Blogging

  9. Options for API Interaction • Direct Client-side AJAX calls • JQuery, Javascript– Our upcoming Widget-Builder! • Server-side Web Request • .Net, PHP, Ruby, Java... • Mobile Apps • objective c, Java, .Net... • Flexible Data Formats - XML Data and JSON from the same Endpoint

  10. JSON Data Returned

  11. XML Data Returned

  12. Documentation • https://api.connectedcommunity.org/help

  13. Katie Paganokatie@higherlogic.comSteve Pontsteve@higherlogic.com

More Related