Fully decoupled cms built with internationally recognized leading technologies, free and open source

Introduction

Since EFV began, its CMS and transcoding have been integrated. This is harder to implement than transcoding alone but makes operation and permissions simpler. Some users prefer separation. As the api in EFV Advanced has matured, integration with other systems and an app has become easier. At a user's request, we used the EFV api with internationally recognized leading technologies to build a fully separate CMS. Users now have more CMS options, including the built-in CMS and the CMS described here.

Features

1. An open-source CMS driven entirely by EFV API2, built with svelte, whose runtime efficiency ranks highly and exceeds vue and react, with server-side rendering favorable to SEO and advanced responsive design.
2. Dynamic rendering similar to bilibili: clicking a recommended video does not reload the page; video information, recommendations and comments update dynamically.
3. Preview-video support for series and films: hovering over a poster plays the preview automatically.
4. Advanced player technology with seamless resolution switching without restarting playback, picture-in-picture, external vtt subtitles and other features, starting playback immediately on page opening.
5. Site-wide memory caching: every 10 minutes, data is retrieved from the EFV api into memory, offering reads n times faster than ssd. Where network latency allows, pages open immediately.
6. Supports previews, payments, VIP groups, series, movies and related features.
7. The site can be installed as a home-screen quick app for direct icon access, faster than ordinary web access. At the time of this post, iQiyi was the only domestic video platform using this.
8. Sensitive-word filtering automatically substitutes *** in requests and comments. For example, fuck you becomes **** you. Add more sensitive words, one per line.
9. Video requests and film comments use redis-based API rate limits: at most one comment every 2 minutes and 2 video requests every 60 minutes.
10. Integrated EFV timestamp/play-count hotlink protection restricts API requests to site visitors, maximizing protection against hotlinking and unauthorized playback.

Without an existing cache, the first visitor's api response is stored in the cms server's memory. For the next 10 minutes, users of the same page read directly from memory for immediate loading.

Screenshots