Include External Assets in Articles
Authors can include external assets in articles. Assets are external files, such as multimedia (images/videos), documents such as PDFs, or even code patches or other binary files. Authors can include these external assets using either of these methods:
-
Embed the asset inline in an article field.
-
Attach the asset so that it appears at the end of the article.
Embedded inline assets are managed in a central asset repository called CKFinder. When authors embed an asset inline, it is stored in the CKFinder repository, which makes it available for other authors to use in their articles. The CKFinder asset library is available only in the CKEditor rich text field toolbar. Authors can find assets that have been uploaded to the library, or upload new assets, and then place them inline in rich text fields.
Authors can also add assets so that they appear outside of the body of an article using the attachment attribute. This method is useful to provide additional content that is suplemental to the main subject of an article. The attachment attribute is available in articles based on their content type configuration. Authors attach assets by choosing and uploading them from their own file systems.
There are some important security differences between embedded assets in CKFinder and attached assets. Assets that are stored in CKFinder and embedded inline in articles do not automatically inherit the access level aspects of the article. Embedded inline asset URLs are publicly available, but their availability has a time limit that you can configure for your organization. Attachments, on the other hand, do inherit the article's overall access level restrictions, and are protected by single sign on (SSO).