Content Component

the ' content component ' is the successor of the legacy issue component docid\ n5a70nkf czbmbsxr57o by using this component, you resolve any content of the different types available in purple, be it an issue, bundle or post introduction to the content types in purple because of purple's origins, 'issue' originally referred any piece of content, such as posts, articles or magazines by creating the "content component" we are streamlining the logic issues are contents that are closely connected in a content binder, and will usually not change their connection after publication editors explicitly chose content to put into an issue just like a printed magazine, it consists of various other contents issues may use pdf or pkar contents originating in print workflows bundles are a truly digital product they provide a more flexible concept for a content binder you can use them in two ways as 'issues' or as 'dossiers' bundle issues , also known as purple issues, are true digital magazines they follow the logic of a print magazine, all content is published with the issue and does not change throughout the lifecycle of the issue dossiers offer more flexibility content can be added, removed or published at any time for end users, this may be part of the value proposition "i've bought a dossier on this topic, and new content can be added to it with good reason if there are new developments" posts are the smallest type of content, a single item, that you can publish they consist of elements that make up articles, image galleries, videos, etc you now will reference any content through the ' content component ' mixing the 'content component' and 'issue component' in the same project may cause unexpected behavior overview of content types in purple actions / content type post issue bundle read only with access only with access only with access customer preview not supported only without access not supported download not supported only with access not supported subscribe only without access only without access only without access login only without access only without access only without access price only without access only without access only without access find here an extensive overview of content binders in purple docid 9rvub5neagmvlcpruvljc access posts via content component clicking on a post via a content component triggers the "onclick" action configured for this component along with the correct configuration in the url resolver js docid\ eyelpz6whk apgmrtbzqk , it opens the post in another view or popup you can also execute different actions a single posts cannot be downloaded access bundles via content component bundles have limited offline functionality in general, it is not currently possible to download bundles as a whole and use them offline we are planning a major overhaul of the offline functionality to provide the best possible user experience both 'manager issues' and 'bundles' (which are 'purple issues' or 'dossiers') can be accessed via the 'content component' their types are not distinguished in the purple experience, so you need to know which issues are present in your app for details, see access bundles docid\ td9f5qelpst5pm1knqbhe setting largest contentful paint (lcp) lcp reports the render time of the largest image, text block, or video visible in the viewport, relative to when the user first navigated to the page notifying the browser to load such content as soon as possible improves this metric this option is available to set up on 'content component' via config called ' lcpprioritized' for details, see lcp priority https //app archbee com/docs/qtjkvew7g556yo3qfoyay/11rq8uyrivp624kxufubz anchor tags in the content component the content component contains two major parts, the cover (image) and data (title, description, etc)and it's possible to configure both a tapcontent and tapcover action separately when the regarding action results in the navigation to a new path like a navigateaction or a opencontenaction that is handled by the url resolver js, anchor tags ( \<a href=" "> ) are rendered for the regarding part of the component, based on the path that the action navigates to if no action is configured for either the tapcontent or tapcover but the content still resolves to a path through the url resolver js, this link is still rendered as anchor tags for the regarding part (cover or content) to disable this behaviour, the disablecontentlinkfallback option can be enabled on the content component