To Romance, Or Not To Romance

When I first started writing seriously in 2007 (by that I mean with the idea of getting published someday) I initially balked at the idea of calling myself a romance writer. Part of that had to do with impressions I formed as a child, part of it had to do with the not so great things many Christians think when they hear the words "romance novel".

But as I've grown and matured as a writer--and a woman--it's been easier and easier to accept that yes, I do indeed write romance. And I'm quite proud of it. Writing a good romance is hard work.

I'm hard at work on the second book of what I fondly call "the space opera", mostly because I haven't found the right series title yet. The first one was clearly a romance. Hero and heroine meet, instant attraction, he wants to protect her though he knows his heart will never survive losing yet another person he loves. She's waiting, without even knowing it, for the man who will see her and need her, unlike every other man in her life. Their first kiss clocks in at 600-something words. They get married at the end of the book. It's a romance. Set in the future. That involves faster-than-light travel and oh, can't forget the aliens!

The second one, not so much of a romance. H&H from first book are the main H&H in this one, are still very much falling in love and dealing with the fallout of who he really is and how it changes their relationship. So it's very romantic. But it's not a romance according to the definition of a romance.

Last week I realized I missed it. The whole crafting a romance thing. Boy meets girl, boy gets girl, boy loses girl, boy gets girl back. I really miss it. A lot. There's nothing more amazing, for me, than watching two people discover each other.

So while it is with great sadness that I finish up The King's Mistress and say goodbye to A'yen and Fae as my leads, it is with great anticipation I start plotting To Save A Life and make Ro and Jasmine fall in love.


Post a Comment