Allan Lasser
Allan Lasser
Do you have an idea for how to capture and observe events like this? One approach would be enhancing our ability to store and query server logs. Since we already...
Strategy: set up a Netlify Log Drain into Logz.io https://www.netlify.com/blog/bring-your-own-log-drains-integration/
Two approaches: 1. Support direct Add-On uploads 2. Support MP3s as a first-class file upload format like PDFs
This is a result of using props to control the styles. There may be other ways to achieve this, like deprecating Flex and creating a global .flex class instead.
Oh yeah, a bunch of conditional classes would be another way to split the difference. I agree that the component has good ergonomics for layouts we're frequently building.
Just needs to be loaded for legacy embeds. Right now it's loaded on every page, adding an unnecessary network request.
Simplest approach: indicate to users that other OCR options are available as add-ons with a link in the upload/reprocess dialog. Another approach: add support for "Don't OCR" on upload, with...
We already wrap the `AppLayout` in `PlausibleTracker`, so that component could set context pretty easily.
That might also be unnecessary, since there's a `plausible-event-name=*` CSS class [that will track automatically](https://plausible.io/docs/custom-event-goals#step-3-add-a-css-class-name-to-the-element-you-want-to-track-on-your-site), provided already have custom events set up.
This could cause heavy load on the search service — performance concerns.