Is It Out of Scope? — Web development
Is adding dark mode support out of scope for a web development project?
Yes, unless it was quoted. Toggle logic, persisted preference, and per-component styling for a second theme is real added build work.
The site was built against one theme, styled once. Adding dark mode means a toggle, a persisted user preference, and every component actually supporting a second set of styles — not just flipping a CSS variable.
Is it out of scope?
Yes, unless it was quoted. Making every component correctly support a second theme, plus the toggle and preference logic, is real implementation work beyond a single-theme build.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers building against a single theme; dark-mode toggle logic and dual-theme component support is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build covers the site in its single approved theme. Supporting dark mode means toggle logic and dual-theme styling across every component, which I'd scope as an add-on.
How MarginFlow flags it
MarginFlow flags dark-mode implementation requests outside_scope on development contracts unless the SOW explicitly listed dual-theme support as a deliverable.