I have just installed another instance of this CMSbyCW software package, this time, on the main home page.  

I have also installed and have been testing different portals, like 

1) Demo Portal 

- changed the logo into something generic, so Users can see the "skeleton" infrastructure.  Initially, I thought, like when I was building the Wordpress CW "Simplified" Theme, that has served me and 25+ websites for MORE than 10 years, without any updates or glitches, all hardcoded codes worked and in the end brought me to the decision to just develop my own CMS). 

- But then I thought, if I, a Techie, have experienced this much overwhelm and troubleshooting - that lead to - creating and building this site - how can others use it too?  

- That's why the Demo.  

- Because this will be for sale, too.  Why for sale?  It will detract from those who would reverse engineer ANY software, and then turn and sell it too.  (Like my experience before in donating source codes to an "opensource" Clinical Information System (CIS) , and then the CIS turned "Commercial" ... that was my fault because when I donated the source code, I "Copy left" it - meaning, they can do whatever they want, update the code, etc.  Anyway, no Intellectual Property protections). 

- the Demo site will show what the CMS can do, what it looks like, BEFORE anyone buys it. 

2)   Docs Portal

- which will actually be a Tutorial Blog / FAQs / How do I .. / Documentation Blog.  

- it made me laugh, yesterday, at the CMSbyCW's portability and the speed at which I can upload the ENTIRE package via FTP.  It took less than 5 minutes, and one installation, when I actually timed it, it only took less than THREE minutes.  

Portable!  

3) Actual Package Portal

- had to also install it on the dot . net, for screenshotting purposes which I will document on the Docs / Tutorial Portal. Once the photo ops is finished, I can either remove it, or not ... we'll see.  

- had to do that because there are a whole LOT of moving parts, and editing that has to be made, especially folder structures and such.  

- I want to create a package that would be a little "simpler" for Users to deploy on their own, just following instructions on the Tutorials Blog. So I have to take those screenshots of the exact spots they need to tweak (example, where to update their Admin email address for the contact or comment forms, etc)

4) I will keep the Sandbox in place, because that was where I thoroughly developed it with the features included, like: 

- Adding / Deleting Users

- Adding / Deleting Comments

- Adding / Deleting and Creating Shortlinks (for Long Links).  

- Adding Share buttons

- Adding Comments selectively

- Adding a Comments on a Feedback Page (instead of adding them on all blog posts) - which is public, displaying them will be "manual" - it will not automatically display on the website, as I programmed the comments to default to "pending".

- Adding a Comment Moderation Panel on the Dashboard. . 

- Adding a Contact Form on the page

There's going to be a lot of screenshotting in the next couple of days.  

And then I will just blog here when the Package is ready for the Marketplace.  :-) 

I think I will just keep the older blog posts here too, because it chronicles the headaches and troubleshooting that happened during the many iterations of this package. 

How portable was it? 

I just downloaded the entire contents of the CMS folder, and then uploaded the entire thing on the public_html folder. 

Simple! 

But I'd have to go through the files, to make sure I fix the hardcoded links that link to the sandbox.  :-)