Actually, it's not really effective JSF if you are even using non-JSF tags.
If you go around dropping chunks of HTML in the abstract page definition, you defeat that intention. It may not bite you today, and it probably won't even bite you to morrow. But there may come a time when you'll wish you hadn't.
An IDE is no substitute for an Intelligent Developer.
You should learn Facelets! It is fairly simple to use, in fact easier to use than JSP. I agree with Tim that ideally you should not have any (X)HTML code in your JSF page definition. But I know it may be a good pragmatic solution sometimes. A good compromise may be to use Facelets templates. You can keep the actual page definitions strictly abstract JSF page definitions then and only add some (X)HTML to your Facelets template(s).