automatic html page creation

This is a very simple project if you know what you are doing. NOTE: I had another coder do this and he got 90% of the way there, then he flaked out and I refused to deal with him anymore. If you are a serious bidder, I will give you the code he came up with and explain how it needs to be tweaked in order to work the way I want it to work. This project is very similar to the way a blog is organized with new content posted and automatic creation of an archive and corresponding navigation. We want this script to be able to add new pages to the website using a list of keywords we specify and update the navigation on the main page of the site (or any other page where we include the navigation) using an ssi include. We want to be able to specify the number of page links will appear on the main page of the site in the ssi navigation. ***** They should appear newest to oldest on the navigation. We want the keywords used to create the pages to rotate. Meaning, we enter in a list of keywords, the script cycles through them then starts over at the beginning. We want the script to add 3-5 new pages a day (randomly decided by the program) at a random time each day. cont'd in "deliverables" section ## Deliverables These pages will be standard, vanilla html page (NOT php) based on a template we specify. All we want the script to do is create the html pages based on a template we specify… our template will then automatically pull in the content. The file names for those pages should be a combination of the keyword + date the page was created [login to view URL] (NOT 19-4-05) As we add pages, we want hyper-links to those pages to appear on the main page of the site in the ssi include. As new pages are created by the script, and old ones move down the list. We also want an “archive?? created automatically that will list the last 30 pages created with a hyperlink and date created (with the keyword + date as the hyperlinked text) that links to the individual pages. As the main archive page reaches 30 links, it will then start on a new page (linked to the old page(s)). This is very similar to the way an archive for a blog is organized. The archive pages created should have the name archive+[login to view URL] created Example: [login to view URL] VERY IMPORTANT: The archives should list *newest to oldest!* This means the archive pages will have to be regenerated every day with the new 3-5 page listings added at the top until it hits the 30 mark, then it becomes its own static page (as named above) and the archive page starts over with the next 3-5 links per day until it gets to 30 and the cycle repeats itself. The navigation for the archive sections should be set up so that each archive page links to the one before and after it to create a “chain?? of pages. All of the archive pages that are created should be regular html pages (NOT php pages) and the main archive page should never change its name (example: always named [login to view URL]), though we can specify the name of the file. ********* Must include a complete installation package and instructions for a standard server... I should only have to upload the files, change a couple of permissions and the program does the rest! ********** This INCLUDES setting up the chron job! ********* NO work will be accepted without the installation package 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform standard c-panel server