Good question.  The answer is that I don't want to give them access to any of the advanced settings - it isn't necessary or required in this instance. 

I specifically do not want them to be able to change the skin or container.  I've seen other people in the past have a requirement to provide certain "Administrative" functionality - but do not want to open-up all of the Admin pages by making the Admin user an "Administrator" by adding them to that role for the portal.

All that is needed  for my requirements is to pragmatically add a page and add a Text/HTML Module to the Content Pane.  In the module I'm building, the "Site Admin" user (not the default Administrator role- but a separate defined role) will select the parent page, provide a name for the new page, add a name for the Text/HTML Module, assign view permissions to (1) All, (2)  Registered, or (2) Site Admin role  for the page, and assign "Edit" permissions to the "Site Admin" role.  Sort of a scaled down version of the existing functionality for Page Management for non-administrators.

I spent some time yesterday on a module that will accept the required inputs and call a stored procedure I've created that will do everything mentioned above using T-SQL.  Further testing is required, but so far it is looking good.