Sheila, I would recommend that you take a closer look at Post Nuke, Xoops, phpnuke and all the other phpnuke clones before you take the plunge.
The reason is that you will have to evaluate whether you really need such portal scripts or not.
The Nuke family has been trying to formulate itself as a CMS, but in reality it is a Community management system instead of a Content Management one.
Reason? Because its easier to operate a blog with Postnuke where you can post news and your users can comment on it, operate a downloads section, weblinks etc..
There are a great many modules to help you do what you want ur site to be, but after all that work I have gone through, I have come back to simpler Dreamweaver generated static pages.
Even after so much of development activity, none of the nukes promise a good Content management system where you can post hundreds of information pages with automatic navigation tools generated, etc.
Although some modules exist to add HTML pages to PostNuke, Xoops (Incontent) etc, they are inadequetely or not seamlessly merged into the main system... and stand out like sore spots.
I am yet to see a content rich site implemented using nukes.
If you want nuke, your priority must be:
User Management.. first and foremost... for enabling users to register for a profile that enables them to post news, comment on news, access restricted modules etc.
You all that you want is to maintain a site with information like portfolio, go for a static designing it yourself, where you enjoy the most flexibility in terms of layout, graphical elements and candy.
By the way, the nukes haven't yet broken out of the three column yet.. when they do, I will look at them more seriously.
Nice page you have Sheila, personal and unique: something you can say is your own creation.
I would NOT want to see a nuke in its place
