npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@flowup/contentful-rich-text-angular-renderer

v0.8.0

Published

**An Angular library for template-driven custom rendering of Contentful rich text fields.**

Downloads

191

Readme

@flowup/contentful-rich-text-angular-renderer

An Angular library for template-driven custom rendering of Contentful rich text fields.

Check out the live demo.

Motivation

From the Contentful docs:

Rich Text is a field type that enables authors to create rich text content, similar to traditional "What you see is what you get" (wysiwyg) editors. The key difference here is that the Contentful Rich Text field response is returned as pure JSON rather than HTML. It offers common text formatting options such as paragraphs, lists and blockquotes, and allows entries and assets within our Contentful space to be linked dynamically and embedded within the flow of the text.

Contentful provides official SDKs for custom rich text rendering, but only for pure HTML strings and for React components. This library provides the same functionality for Angular apps, giving developers the freedom to customize how individual rich text nodes/marks are rendered using Angular templates.

Setup

Assuming you already have an Angular project, simply install this package from NPM, along with its peer dependencies:

npm install @flowup/contentful-rich-text-angular-renderer @contentful/rich-text-types fast-deep-equal

Usage

To simply render a rich text document using the default configuration:

<div [cfRichTextDocument]="document"></div>

The input object is expected to match the Document type from @contentful/rich-text-types (*). This is the JSON format of rich text fields, as returned by the Contentful Delivery API. Contentful entries may be fetched from the API using the official JavaScript SDK. (Note: If want you the entry fields to be strongly typed, you may use the @flowup/contentful-client and @flowup/contentful-types-generator packages instead.)

(*) If you're using the Contentful GraphQL API, then the input object should instead contain the json and links GraphQL fields (this will take care of resolving linked entries and assets).

The main feature of this library is allowing you to easily override how different types of nodes in the document tree are rendered. Using the provided structural directives, you define not just your own HTML markup, but also your own components, directives, etc.

This next example configures the following overrides:

  • hyperlinks from YouTube will be rendered as an embedded YouTube player instead of a plain link,
  • other hyperlinks will be opened in a new browser tab,
  • embedded blog posts entries will be rendered as cards using a custom Angular component, and will also function as an internal page link,
  • embedded gallery entries will be rendered using a custom Angular component,
  • text marked as code will be rendered as a standalone code block with syntax highlighting.
import { Component, Input } from '@angular/core';
import { BLOCKS, Document, INLINES, MARKS } from '@contentful/rich-text-types';
import { highlightAuto } from 'highlight.js';
import {
  CfRichTextChildrenDirective,
  CfRichTextMarkDirective,
  CfRichTextNodeDirective,
  CfRichTextDocumentComponent,
} from '@flowup/contentful-rich-text-angular-renderer';

@Component({
  selector: 'app-foo',
  templateUrl: './foo.component.html',
  standalone: true,
  imports: [
    CfRichTextDocumentComponent,
    CfRichTextNodeDirective,
    CfRichTextMarkDirective,
    CfRichTextChildrenDirective,
  ],
})
export class FooComponent {
  @Input() document: Document;

  readonly BLOCKS = BLOCKS;
  readonly MARKS = MARKS;
  readonly INLINES = INLINES;

  readonly YT_EMBED_REGEX = /^https?:\/\/(?:www\.)?youtube\.com\/embed\//;

  highlightCode(code: string): string {
    return highlightAuto(code).value;
  }
}
<div [cfRichTextDocument]="document">
  <ng-container *cfRichTextNode="INLINES.HYPERLINK; let node = node">
    @if (YT_EMBED_REGEX.test(node.data.uri)) {
      <iframe [src]="node.data.uri" [title]="node.content[0].value"></iframe>
    } @else {
      <a [href]="node.data.uri" target="_blank" rel="noopener noreferrer">
        <ng-container [cfRichTextChildren]="node" />
      </a>
    }

  </ng-container>

  <ng-container *cfRichTextNode="BLOCKS.EMBEDDED_ENTRY; let node = node">
    @switch (node.data.target.sys.contentType.sys.id) {
      @case ('blogPost') {
        <a [routerLink]="['/post', node.data.target.sys.id]">
          <app-blog-post-card [entry]="node.data.target" />
        </a>
      }
      @default {
        <app-gallery [entry]="node.data.target" />
      }
    }
  </ng-container>

  <code *cfRichTextMark="MARKS.CODE; let node = node" class="hljs" [innerHTML]="highlightCode(node.value)"></code>
</div>

Check out demo app for another example of customizing a rich text document (used in live demo).