4 Commits

Include renames

Author	SHA1	Message	Date
Paul Nothaft	de3a7f70bf	fix(cms): enable the Tailwind typography plugin so prose classes work (#1288) ... tailwind.config.js had plugins: [] and @tailwindcss/typography was never installed, so every prose / prose-neutral / dark:prose-invert class in the app resolved to nothing. Preflight, which IS active, resets h1-h6 to inherit size and weight and strips list-style from ul/ol — so an applied <h2> rendered pixel-identical to the <p> it replaced. The editor was never broken. The toolbar highlighted because editor.isActive('heading') correctly returned true; only the CSS to show it was missing. That also explains why pasting rendered rich text worked: it carries inline styles. Ten surfaces rely on these classes, including the PUBLIC CMS pages — so impressum/datenschutz were serving unstyled headings to visitors too. Review follow-ups: prose colours are mapped to the theme tokens wherever .text-theme marks theme-owned text (a dark gallery preset sets --color-text but no .dark class, so dark:prose-invert never engages and headings would have gone near-black on dark); code blocks inherit rather than being scaled twice; and H5/H6 get explicit rules, since the plugin only styles h1-h4. Closes #1288	2026-09-04 14:26:51 +02:00
Luca	d2a10f6523	fix(cms): apply dark mode to CMS editor, public CMS, and admin modals	2026-05-05 16:07:21 +02:00
paulandClaude	1b4b497fdf	chore: clean up codebase for production readiness ... - Remove all console.log/debug statements from production code - Add NODE_ENV checks for development-only logging - Remove test scripts (test-feedback, test-image-security, test-backup-*, test-restore) - Remove one-time fix scripts (fix-temp-photos, fix-migration-state, mark-migration-applied) - Remove sensitive files (.env.backup, ADMIN_CREDENTIALS.txt) - Update package.json to remove references to deleted scripts - Replace console statements with logger utility in backend - Secure error boundaries to not expose stack traces in production This makes the codebase production-ready with no debug output or test scripts. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>	2025-08-24 23:19:30 +02:00
paulandClaude	1773ed5f95	Initial commit - Project start (July 17, 2025) ... Original: feat: enhance security logging and ensure rate limit blocks are properly tracked - Add comprehensive logging for rate limit blocks with full request details - IP address (with proper proxy detection), user agent, headers, timestamps - Rate limit info (current count, limit, remaining, reset time) - Separate tracking for auth vs general endpoints - Enhance authentication failure logging - JWT validation failures with detailed error info - Admin auth attempts without token - Failed token validation with user context - All events include IP, path, method, user agent - Improve Winston logger configuration for production - Add automatic log rotation (10MB errors, 50MB combined) - Create separate security.log for auth/rate limit events - Ensure logs directory exists automatically - Add structured JSON format for log aggregation - Support container logging with LOG_TO_CONSOLE env var - Create comprehensive documentation - Security logging guide with examples - Monitoring recommendations - Configuration reference - Add test script to verify logging functionality All rate limit settings remain configurable via admin panel: - Window duration, max requests, auth limits - Skip authenticated requests option - Public endpoints only option 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>	2025-07-24 16:57:07 +02:00