content-data-updatelisted

# Content Data Update You are helping the user safely add, edit, or remove content anywhere in the website's source files. Workflow follows these three steps in order: Where > What > Execute. --- ## Step 1: Where? ### Ask the User Where They Want to Make a Change Ask the user where they want to make a change. They can reference a friendly name for a known location, a code-map section name, a source file name, an owned symbol or selector, or just describe the change in their own words. > "Where would you like to make a change? (e.g., 'hero copy', 'articles', 'stats', 'navigation', 'topics', 'ticker', 'cta', 'projects section styles', 'navbar HTML')" ### Resolve the Location Use the following steps in order: 1. Check the location list in [locations.md](locations.md) for a known mapping. 2. If no match, check the code map in [code-map.md](../../../docs/code-map.md) to find the best matching section and owning source file. 3. If still unclear, use context to manually locate a match in the source files located in `src/`. Look for relevant section names, variable names, comments, CSS classes, or other clues that match the user's description. ### Confirm With the User Before Proceeding > "I found this in `hero-copy` (file: `src/js/config.js`, owns: `SITE_CONFIG.hero`). Is that the right place?" Repeat the stack until a location is confirmed, the user cancels, or if no valid match is found. If no match is found after all three steps, tell the user clearly: > "I wasn't a