Skip to main content
PhotoEditor

( Public history )

Changelog

Published, verifiable changes to the product, content, and architecture. This record does not include ideas or features that have not shipped.

Architecture and editorial

Seven new task landings, topic hubs, and deep photography guides

  • Published seven dedicated, verified task landing pages: /heic-to-jpg, /compress-photo, /resize-photo, /convert-image-format, /black-and-white-photo, /remove-photo-metadata, and /photo-curves.
  • Launched two topic hubs with CollectionPage schemas: Color and Light (/color-and-light) and Files and Formats (/files-and-formats), interconnecting all tools and articles.
  • Updated top navigation with a 2-column dropdown grid grouping all 16 tools and guides on desktop and mobile viewports.
  • Published the official blog editorial standard (docs/GUIA-EDITORIAL-BLOG.md) enforcing the 70/30 rule (70 percent universal photographic theory / 30 percent private browser execution) with 1,800+ words per guide.
  • Overhauled key guides (cropping, Instagram optimization, analog film aesthetics) to deep, comprehensive references with interactive tables, real screenshots, and 8-question semantic FAQs.
Content and evidence

Pages and guides rewritten for the new editor

  • The noise, vignette, grain and filter pages were rewritten from the editor's code: filters that never existed (sepia, duotone, cross-process) and wrongly described controls were removed.
  • Blog guides were expanded and now carry real screenshots of the current editor, in English and Portuguese, generated by a script from the demo photo.
  • The privacy section no longer repeats on every tool page; the full text lives on the home page and on Local processing.
  • A /llms.txt was published: a plain-text site map for AI assistants, built from the same sources as the pages.
  • The sharing image was redone from the current page, in English and Portuguese; the header, the editor and structured data now use the PhotoEditor.sbs name and icon, and the menu lists only this site's tools and guides.
Product

New editor on every page

  • An Automatic panel with seven recipes analyzed photo by photo, and separate Auto Tone, Auto Contrast and Auto Color.
  • New panels: Curves and levels, B&W by color, Detail (masked sharpening and guided-filter noise reduction) and .cube LUTs in Filters.
  • Before/after divider, histogram, zoom up to 800%, step-by-step history and command search (Ctrl+K).
  • AVIF, HEIC and TIFF input; AVIF output; export with presets, maximum size in KB, naming pattern and an EXIF choice.
SEO and ad policy

Thematic links and fail-closed AdSense protection

  • Priority pages and all nine articles now use visible breadcrumbs and topic-specific related reading.
  • A reproducible audit visits every sitemap URL and blocks delivery when it finds broken links, redirects, or orphan pages.
  • The future manual ad unit remains disabled and can render only when approval, consent, route, editorial placement, publisher, and slot are all valid.
  • Studio, download, trust pages, product UI, and active interaction states remain outside the ad pilot.
Content and evidence

Visual HSL guide with reproducible results

  • One project-owned source and three PNG exports made through the real interface now demonstrate changes to blue, purple, and yellow ranges.
  • Each sample publishes its settings, changed-pixel percentage, mean RGB difference, method, environment, and limitations.
  • The raw JSON dataset and images are downloadable, and the HSL landing page and tutorial link to the experiment.
Content and evidence

Verifiable benchmark, formats, architecture, and help

  • The batch-editor report now publishes its method, environment, ranges, medians, and raw JSON data.
  • A reproducible comparison now publishes matching JPEG, PNG, and WEBP outputs when the browser supports them, including size, parameters, RGB differences, and downloadable samples.
  • A factual diagram now separates the local pixel path from the page's optional connections.
  • A bilingual help page now documents uploads, memory, previews, ZIP, WEBP, and transparency with solutions aligned with the product.
  • The assets gained bilingual routes, canonical, hreflang, sitemap entries, and browser tests.
Product and quality

Real workflows and regression prevention

  • JPEG and PNG export, WEBP output when the browser supports it, resizing, rotation, transparency, ZIP batches, cancellation, and partial failures gained automated coverage.
  • Batch processing gained a preventive budget based on decoded pixels and estimated-load messages.
  • Test-image generation gained safe retries for transient Windows file locks.
Experience and accessibility

Visual system and navigation

  • Geist typography, cards, hierarchy, movement, and purple tokens were normalized across product and content pages.
  • The language dialog, keyboard focus, touch targets, and reduced-motion preference were verified.
  • Twenty visual references cover five pages at four viewport sizes.
SEO and trust

Bilingual architecture and transparency

  • English now uses the unprefixed root while Portuguese keeps the same slug under /pt/.
  • Routes, sitemap, canonicals, hreflang, and ad policy now share a central registry.
  • Author, methodology, changelog, and free-access transparency pages were published.
Content and privacy

Verifiable claims

  • A factual matrix now records editor formats, controls, limits, and verification state.
  • Copy and audits were aligned with local image processing and the network connections the page may still make.
  • Operational studio and download routes were removed from search indexing and ad eligibility.

How to read this changelog

Why do some entries describe copy corrections?
Because published text is part of the product. When copy claims something the code cannot do, fixing that copy is just as genuine a change as fixing a function — and often more urgent, because that is what users read before deciding to trust the tool.
Are dates based on publication or repository commits?
They record when changes landed in the repository, traceable through Git commits. Deployment may follow later; keeping Git dates prevents the record from depending on infrastructure pipeline delays.
What is omitted from this changelog?
Internal maintenance without user-observable effects — code refactoring, dependency updates with identical behavior, and test harness adjustments. The changelog exists for users of the photo editor, not as a repository commit dump.