How to create a new aspx page in Pages library using Elements.xml without including any aspx page layout in my feature?

Question

Is it possible to have the elements.xml file create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?
I see no reason to add a mywebpartlayout.aspx to my feature just so I can deploy a Home.aspx based on the BlankWebPart.aspx page layout. 
I'm sure there is something obvious I am missing with regards to the Elements schema (which is why I've almost given up on using it completely and just gone to pure C#) but
I would really like to do this kind of simple stuff with declarations if at all possible. Must less code to write, debug, test and maintain.

Answer 1

I don't see how my question keeps getting misunderstood. This seems to be very clear and clearly not answered: "Is it possible to have the Elements.xml file
create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?"
I can't be more clear than "without including ANY sort of page layout or aspx artifact (meaning anything ending in aspx) IN THE FEATURE". I am not capitalizing to yell,
only to emphasize. Your disagreement is based on a link that shows ADDING AN ARTIFACT (the dummy MyPage.aspx) to a feature. I am asking if it
is possible (again, I cannot be more clear) to just use an Elements.xml file to instruct SharePoint to make a new item in a Pages or SitePages library. 
Your definition of page includes Page Layouts and what you call Web Part Pages (again, a type of page layout + data in a site pages list that says what webparts
to display). Page Layouts are clearly NOT items stored inside of a SitePages or Publishing Pages library. Those libraries are just lists whose records
define the parts to show inside a specific layout.
When I refer to a Page I mean an entry into a pages (site pages/publishing pages) list. If I wanted to deploy a page layout then, quite obviously, I would need
to include it into my solution. I think maybe you are assuming that I do not know the difference. I do. The question is, can an Elements file alone be enough to instruct SharePoint to make a new entry into a Pages or SitePages library. 
Now, your second link does show how to reference an existing Page Layout. Thank you for that. It is excellent. But this still leaves the problem of having to
add some sort of aspx page into the solution. Let me try to explain why I feel this SHOULD BE unnecessary: The aspx file will not have anything on it if I am referring to the ~sitecollections/.../BlankWebPartPage.aspx layout.
All web parts and content that should appear on the new page can be described IN the Elements.xml file. Any sort of aspx file is unnecessary, it seems to me.
So, if I am referencing a ~sitecollections/.../BlankWebPartPage.aspx page layout and specifying the web parts to add to the page, why should there be a
requirement to have some aspx file within the feature? That's what I am trying to figure out.
I am not asking for source code as proof. I am asking for an Elements file that does NOT reference anything AT ALL inside the Visual Studio solution for reasons I just described.
If you do not know how to do it then perhaps it cannot be done but I would like the question to stay unanswered for a little while until someone can demonstrate either a) it CAN
be done or b) a link to some Microsoft document stating that it is MANDATORY to have a physical element within the feature that gets copied to the environment.
I think it is important to understand what is being asked before insisting you have answered. It is clear from your posts that you have not fully understood the question yet but
I am hoping this posts makes it clear. I really appreciate you taking the time to respond, though. You seem to be the only one up for the challenge! :)