You could learn to love the mundane aspects of your job. Seriously though, no one expects you to be creatively invested in that fix to the contact form, but that's the work people need done.
This is thinking like a user, not thinking like a programmer. As a programmer, you don't want to fix the contact form, you need to fix the need to fix the contact form. This is how you avoid deathmarch projects; you program away the tedious parts so that you have a functioning system instead of a bunch of code that does stuff.
But programming actually ends up taking less time than coding. Coding a page takes an hour. Coding twenty pages takes twenty hours. Programming a page maker takes a day. Making a million pages then takes no additional time.
Unless you really only have one page that never needs to change (and when has that ever happened?), programming is going to beat coding every time. And it's more fun!
A lot of the repetitive stuff that professional programmers do could be automated. Writing code to automate the problem and then having the problem itself solved automatically tends to be both more efficient and more interesting than tediously coding up the naive solution many times. However, it also requires actual thought and understanding, where an entry-level drone copying and pasting from a web page can follow the tedious, repetitive approach. This is one reason why good programmers are much more productive than bad ones, and it's one of the reasons good programmers tend to dislike working with bad (naively written, non-automated) code.
