This document provides guidance on selecting the right technology for different use cases. It compares Framework API vs Search API, DMS vs Library, PageBuilder Pages vs ASP.NET Pages, PageBuilder Widgets vs ASP.NET User Controls, and Content Lists vs Collections. The key factors addressed include capabilities, control, flexibility, and how the technologies are affected by changes to the underlying content.

1. The Choice is Yours Best Practice Guidance on Selecting the Right Technology #ektron v8.5

2. Should I use __A__ or __B__?

3. Should I use Framework API or Search API? Framework API Returns a ContentData object Queries against the source of truth Queries against ContentData properties Express simple criteria using Filters Search API Returns a SearchResult object Search Index is not instantly updated Queries against properties that span types (taxonomy, etc) Express complex criteria using expression trees

4. Should I use DMS or Library? DMS Assets are added as first class content items Provides all content capabilities to assets, like permissions and approvals Is used primarily for content centric documents, like Office Documents and PDFs Is also used for images when history and approvals are needed Library Items are added as simple resources, not as first class content items Is not content, therefore provides no history, approvals, etc. Used primarily for web simple resources such as a company logo

5. Should I use a PageBuilder Page or ASP.NET Page? PageBuilder Page Supports assembling new landing pages, micro-sites, and web pages in the browser Allows page and elements to be created, controlled, and configured by Marketers Provides page-level permissions, approvals, workflow, etc. ASPX Page Provides exclusive IT control over page development and its behavior through Visual Studio Is used when you need to create web application with few or no content requirements

6. Should I use a ASP.NETUser Control or Widget? PageBuilder Widget Is used exclusively within the context of a PageBuilder Page Is an extension of a .NET User Control Provides browser-based control to content managers and marketers over its behavior Typically encapsulates content centric functionality ASP.NET User Control Is used to encapsulate functionality within an ASPX Page Is used within a PageBuilder Page when you need not provide Marketers with ability to configure or edit the control’s properties within a browser

7. Should I use a Content Listor Collection? Content List Is a list of content items generated dynamically using the API (Framework, Search) or a Server Control Used when there are rules that describe the characteristics of the items in the list, e.g. Today’s PDFs Used when the items in the list may change frequently Collection Is a manually curated list of content items Provides tight editorial control over the items in the list Used when items contained within the list are updated infrequently