Resource scope question: privacy boundaries in browser color workflows #1138

I read the README resource schema (article, video, or presentation). Before submitting a resource file, could you clarify whether an educational article about preview-first image processing and privacy boundaries would fit the community resources collection?

The motivating example is LUT Generator: https://ailutgenerator.online/. It is a browser-based reference color workflow for photos and SDR video frames. Local matching, manual adjustments and PNG exports are free; custom .cube exports use credits. Optional AI assistance sends a reduced preview, and export validation sends the color table.

A proposed article would focus on developer-facing decisions rather than a product announcement:

• Separating local preview operations from optional remote requests.
• Explaining the data boundary before sending a preview or color table.
• Keeping creative color adjustments distinct from an editor's required input/output color transforms.
• Testing reusable LUTs on representative frames rather than treating one preview as a benchmark.

I am not claiming the product's deployed architecture has been verified as Jamstack, and its homepage is not being mislabeled as an existing educational article. If this topic is appropriate, should a contribution link to a standalone published guide instead of the product homepage?

Disclosure: this is a project-affiliated submission for LUT Generator, drafted with AI assistance. No maintainer endorsement or directory acceptance is implied.