My approach would be the following: define you own macro. For example, \myorangetext
; then use a global search and replace to change every occurrence of textcolor{Orange}
into myorangetext
; rinse, repeat.
Now you can do simply this thing:
\documentclass{article}
\usepackage[svgnames]{xcolor}
\usepackage{xstring}
\newcommand{\EatOneArg}[1]{}
\newcommand{\myorangetext}{\textcolor{Orange}}
\newcommand{\myaquatext}{\textcolor{Aquamarine}}
%
% comment or uncomment these
%
% \renewcommand{\myorangetext}{\EatOneArg}
\renewcommand{\myaquatext}{\EatOneArg}
\begin{document}
And this is my code
\myaquatext{Some text Aquamarine},
some text without color,
\myorangetext{some text in Orange}
\end{document}
Commenting or not each redefinition of your command you can change the appearance of it... and if in the future you want to change the Orange text into for example a footnote you can do it...
\renewcommand{\myaquatext}{\footnote}
The main philosophical difference here is that, defining your own macro, you do not state how to print some text, but what the text IS: this is the fundamental idea about LaTeX: describe semantically, not visually, keep content and visualization as separate as possible.
(So, really, do not name the macros \myorangetext
and so on: call them \commentforFred
or \commentforProf
or whatever they really mean)
\textcolor
commands with a custom macro (that either outputs colour or nothing depending on a list )