Change Details

Once partner descriptions are located in json files in the codebase (T278334) and have converted those back to HTML (), we need to update Library Card's templates to use this data instead of fetching them from the database. **Acceptance criteria** - Nothing in the Library Card should be loading partner descriptions stored in the database.

Once partner descriptions are located in json files in the codebase (T278334), we need to update Library Card's templates to use this data instead of fetching them from the database. Because we're now storing those descriptions as HTML, we can do away with our Pandoc parsing/caching and revert to using the strings directly. **Acceptance criteria** - Nothing in the Library Card should be loading partner descriptions stored in the database. - Fragment caching shouldn't be used for partner descriptions.

Once partner descriptions are located in json files in the codebase (T278334) and have converted those back to HTML (), we need to update Library Card's templates to use this data instead of fetching them from the database. Because we're now storing those descriptions as HTML, we need to update Library Card's templates to use this data instead of fetchwe can do away with our Pandoc parsing/caching and revert to using them from the database strings directly. **Acceptance criteria** - Nothing in the Library Card should be loading partner descriptions stored in the database. - Fragment caching shouldn't be used for partner descriptions.