Ask HN: How do I make the transition from janitor - architect?

Right now I'm a frontend developer. I can design pretty things, I can make pixels look good, I can make things transition in pretty ways. I love what I do, but I don't feel like I'm truly sitting there and trying to wrap my head around a real problem, whether it be optimizing something (closest I've come to "optimization" is improving page performance) or coming up with a more efficient algorithm for something.

Right now I feel like a janitor. I'm not really innovating or creating, I mean I am, but it involves creative intelligence for the most part and isn't exactly the most challenging work.

This is where I'm coming from: I want to make a lot of money in this field, and while I make great money now, I want to take my knowledge and expertise to the next level. I can't just be a pixel pusher forever. I am always looking for something to study or read. I don't plan on going back to school, that ship has long sailed and there's better resources online.

How can I make the transition from a code janitor to a code architect? I want to build cool, complex shit, not just align pixels. I know elementary math and have been exposed to calculus and other maths but nothing remotely in depth.