There is a thing called "a coding architect". It basically means that you're a programmer just like any other, but you have more responsibility on the overall architecture of the project.
Sure, I've seen plenty of these "documentation architects" who don't produce that much value, but that's not the only type of architect out there.
Not a unicorn as one might think. Most of senior stuff in our consultancy shop ware software architect hat at very beginning of software project, and later on do fair share of coding, mostly critical stuff.
At the company I work for, they strive to hire this role (which is what I do). "Architects who code". Definitely the way to go. As a software consultant, I should also note that I have worked with a number of Architects who don't code, and in every case, they took away more than they added.
Sure, I've seen plenty of these "documentation architects" who don't produce that much value, but that's not the only type of architect out there.