My previous post just had the features, and story about what was built out of necessity. 

If I had that problem, surely, others have too. So as I am buulding all these, it's easy to get overwhelmed, so I am trying to document what I am doing (and hopefully not be training my next hacker).  

So after my last post, I have been working on the Software Licensing part of CMSbyCW.  

It is mostly done, when a Customer fills out the Purchase Form, with the following:

1) Name

2) Email

3) Phone Number

4) Domain Name / s - up to 3 active installations

- I decided to do this because a DOT.com might install it on their (1) Main site (2) a blog.DOT,com subdomain, or a subfolder. or they can have a dot com, dot net and dot org.  So it's like getting One Software License Key for three installations.  I configured it to have a one year expiration date.  

5) The Buy / Purchase Button will then do three things

5.1) Check if the Domain is already licensed, and displays the Existing License Key

5.2) If New, then it generates the Software License Key

5.3) It will also send an email to the Customer with these details. 

Then I thought about how to change customer names, or emails. or phone numbers, so I also built a separate Software Licensing Control Panel where  I can do this on the Front End ... like a dashboard.  

Software Licensing Control Panel

So I also have built this simple Software Licensing Control Panel (that requires a login.  

Of course this will NOT be a part of the CMSbyCW or CW Simple Site package .. :-) 

There is such a thing as Intellectual Property in software, and I have already done my share in donating source codes (and then get pissed off when the establishment I have donated it to, end up selling it, LOL!)

So, I thought I will just have this in place, just in case the CMSbyCW takes off commercially. 

Because for now, it is just built out of my own necessity so I can deploy it on the 25+ former WP sites that got corrupted or wiped out. 

There's such a thing as a blessing in disguise. 

Maybe I should start taking screenshots for these things .... 

So the next Module I will be building is the Installation Guide. 

I guess I would do the screenshotting as I am doing that. 

Bang bang. 

All right, back to coding.