player
payload
Our great sponsors
player | payload | |
---|---|---|
2 | 160 | |
1,715 | 19,608 | |
9.0% | 9.4% | |
9.8 | 9.9 | |
2 days ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
player
-
How to Write a Great Readme
vidstack is very light on technical details but starts with a concise intro and a screenshot, as well as relevant links: https://github.com/vidstack/player
payload is well-structured in general: https://github.com/payloadcms/payload
nanostores starts out with an intro and telling code examples, followed by lots of technical details: https://github.com/nanostores/nanostores
-
Show HN: Modern media captions parsing and rendering library (vtt/srt/ssa)
Hey everyone!
The motivation for this started with some initial exploration of how native captions are inconcistent and extremely limited with respect to positioning + styling across browsers. In addtion, existing captions work was glued inside player libs and all open-source parsers were ancient (e.g., mozilla/vtt)!
I wanted to modernize it all with newer web APIs such as `fetch` and `ReadableStream` and extend support out to multiple captions formats. I also noticed that a lot of popular players on the web in recent years started adding caption customization options. Turns out accessible captions can be legally enforced!
Do note that accessible captions not only includes sync/timing, but also an adequate set of controls to customize the style of the captions, ensuring they're readable for everyone. You can see an example of this on YouTube when you go to the captions and click customize.
It just seemed silly that probably every single company is internally building this type of lib which is insanely hard to get right. I built this to serve our accessiblity goals at Vidstack[1] where we're working on enabling you to build production-ready player quickly.
It took me about two weeks to build this and honestly there's still a lot of areas that need work but it's a great start. I hope you find it useful. You'll find a lot more helpful information in the repo.
I'll also leave you with this YouTube video where Dan Sparacio beautifully explains the complexities of building accessible media captions on the web at Paramount [2]. This is one of my favourite Demuxed talks. In there case, acessible enough to meet FCC guidelines _Highly_ recommend checking it out to learn more!
[1]: https://github.com/vidstack/player
payload
- Best way to build a modern back end and admin UI. No black magic
-
Headless CMS: Directus vs Payload vs Strapi in 2024
Despite being a relatively newer player, Payload's GitHub repository has accumulated 18.8k stars and 1.1K forks as of April 2024, reflecting its growing community. The project has also secured $5.6 million in funding, positioning it for continued growth and innovation.
-
Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
My most recent project launched in January. NextJS 14 client integrated with PayloadCMS (http://payloadcms.com) for the back-end. I love both technologies in theory, but they're both going through a renaissance period and "bleeding edge" doesn't even begin to describe it.
If I'm just building a client app, create-react-app is still my go to.
Before now, I'd been building on WordPress for 10+ years for anything client-administered. Planning on using Payload from here on out.
-
Open-Source Headless CMS in 2024
Payload CMS: The Customization Insurgent
-
Prismic.io is increasing our price by *1900%* over Christmas
Payload is free, you can self host it without paying a one time fee or a SaaS fee for its use, it even says so at the bottom of the homepage
-
Next.js 14: No New APIs & Breaking Changes
James, the co-founder of Payload, a headless CMS with MongoDB support, shared his insights on the drawbacks and limitations of using a headless CMS in the context of web development. He challenged the promises often made about headless CMS, such as separation of concerns and ease of content migration, revealing that these claims often don't align with the reality faced by developers and clients. James is considering integrating Payload directly with Next.js to overcome these limitations and offer a better developer experience, including out-of-the-box features and simpler deployments. Should Payload move to Next.js?
- Ask HN: Why aren't Django Admin style dashboards popular in other frameworks?
- Payload (app framework + CMS in TypeScript) releases 2.0
- Payload 2.0: Postgres, Live Preview, Lexical RTE, and More
-
Payload 2.0 released, TypeScript headless CMS and app framework
Hey HN, Dan here from Payload (YC S22), an open-source headless CMS that closes the gap between CMS and traditional app frameworks. We’re excited to announce Payload 2.0!
https://github.com/payloadcms/payload
If you’ve not heard of Payload you’re probably wondering why the world needs another CMS. Payload connects to your database and runs without the vendor lock-in and black box of SaaS based CMS solutions, and it’s far more extensible than off-the-shelf SaaS options. Enterprises in specific have been finding value in this control, and they’re using Payload to power content infrastructure that simply isn’t possible through integrating with SaaS webhooks alone.
Today’s announcement is all about features that strike at two neglected areas in the world of CMS. The first is application framework level control over your database that you’d expect with tools like Ruby on Rails or Laravel and the second area is making content editors effective by seeing their edits in realtime.
Here are the highlights on what we’ve been working on:
*Postgres Support*—in the same week we launched about two years ago,people asked for Postgres support. It brings me pure cathartic joy to finally give this to our community. To be fair, MongoDB has been a perfect solution for our architecture and it’s still recommended. But with a new adapter pattern for databases, you can stand your Payload project up on Postgres and run the same functionality as you can with MongoDB now. The crazy part is that we didn’t compromise on how nesting complex fields works. We could have taken the “easy” road and wrote things to JSON, but we leaned fully into the relational way and built the right tables and native column types for fields all the way throughout.
*Database Migrations*—maintaining a production app while deploying schema changes is something you come to expect from ORMs and backend frameworks, but rarely CMS. Payload 2.0 delivers full, first-party migration support all in TypeScript. We took a lot of care on the developer experience here so that when working with Postgres, thanks to our friends at Drizzle, we generate the migration files in TS that add the tables and fields for you. If you have to manipulate data before or after, you have a clear way forward now.
*Database Transactions*—when a request involves multiple inserts, updates or deletes to the database, you need control to rollback all changes when one part fails. The built-in Payload CRUD operations do this now for you and your custom hooks and other code can too.
*Live Preview*—the ability to quickly draft content and see it in context of a website is a literal game changer. We have taken the best dev experience of any headless CMS and given the editors a reason to demand Payload over the others.
*Lexical Richtext Editor*—our original Slate based editor has seen some great features added, like storing related documents directly in the JSON, uploads and any customizations. Unfortunately Slate leaves a lot to be desired on how to extend it, especially compared to Lexical. In a few short weeks we’ve built up a new editor experience inspired by Medium and Notion. Now type “/” and have embedded relationships, uploads, and custom blocks popping right up to be dropped in. Then drag and drop them to reorder your content. If you still want Slate, we continue to support that too.
We’re not compromising on editor experience. This is how we’re bringing the “head” to the headless CMS.
Building critical applications on top of a CMS may sound like blasphemy but it doesn’t have to be that way.
Thanks for reading! I look forward to hearing what you think.
What are some alternatives?
mp4-muxer - MP4 multiplexer in pure TypeScript with support for WebCodecs API, video & audio.
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
RVS_PersistentPrefs - A Simple Class For Basic Persistent Storage
Directus - The Modern Data Stack 🐰 — Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
drop - File dropping made simple
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
earwurm - An easier way to use the Web Audio API for playback of UI sound effects.
bulletproof-react - 🛡️ ⚛️ A simple, scalable, and powerful architecture for building production ready React applications.
LGV_MeetingServer - An aggregation server for meeting list servers.
webiny-js - Open-source serverless enterprise CMS. Includes a headless CMS, page builder, form builder, and file manager. Easy to customize and expand. Deploys to AWS.
analytics-next - Segment Analytics.js 2.0
Ghost - Independent technology for modern publishing, memberships, subscriptions and newsletters.