Procedure Plexel Help     Site written by John Middlemas

Homepage Back Site Contents Map Main Pages Audit Standards Procedure Clickboard Sections Steps Various Emails Toolbar Etc Downloads Reference Download Plexel Page Index A to Z Contact us Plexel Help - Plexel is a free javascript website HTML editor and applications platform. Make global changes with a few clicks. Automatic categories, images, index, and map. Freeware web publishing software. Procedure. Sequence of steps involved in making a website. The procedure for making and auditing a website is listed at the bottom of this page. Regarding the S/MIME secure email certificates, Comodo is a much simpler setup procedure. Originally we thought Comodo could only be used for Internet Explorer, and so we originally suggested people that use Firefox, & SeaMonkey to use the Thawte certificate:- But it seems this isn't the case...Comodo can be put into Internet Explorer, exported and then imported into SeaMonkey. To do, you first setup the certificate in IE, then use the "Export" option to save the certificate (with the private key) to a file and then "Import" that file into SeaMonkey under the certificate section. GOOGLE SUCKS Why? Because they blocked this site without proper reason and after about one year of negotiation still have not given a proper reason nor proper instructions of how to fix any problems Secure Email S/MIME Thawte - Procedure for setup of S/MIME Thawte free personal email certificates and use with SeaMonkey or IE and Outlook. Secure Email S/MIME Comodo - Procedure for setup of S/MIME Comodo free personal email certificates, and use with IE and Outlook. Secure Email Problems Author Training Author Setup Clickboard Sections Return Receipts Adding Videos - Instructions on how to embed videos like the ones found on youtube.

CHOOSE THE DOMAIN NAME ---------------------- Neil or John to pick out usually product based domains from list of purchased domains or new domains to be purchased. Neil emails John with wordtracker popularity of site terms. John approves/disapproves the site. BLUEPRINT STARTED ----------------- Neil or Dan undertakes research & creates blueprint. Neil adds the site to our server, server DNS, and creates a login username and password. Neil prompts John to repoint the domain and sends author name. The blueprint, a list of our related sites, and login username, pwd, and site IP number, are included in the email. John repoints domain, adds it to the Google Adsense account, and emails Neil thereby approving the blueprint and list of related sites. FRAMEWORK STARTED - Neil controls site Notes -------------------------------------------- Neil makes the framework. Neil makes Site Costs page and records domain name, IP number, blueprint author, site author, and framework upload date in it. Neil uploads the framework to the IP number. Neil issues site framework to author and emails Steve attaching framework if author is managed by Steve. BUILDING STARTED - Author controls site Notes --------------------------------------------- Author writes site and prompts Neil for another when nearly built - any queries taken up with Steve or Neil. Neil issues new site and prompts Steve that previous site may soon be built. Steve sends email titled e.g. "limoz.com built" to Neil, John and Paul. Includes instruction for Neil to undertake audit and add site to Plexel Links, and for Paul to Addweb the site. SITE BUILT ---------- Neil adds the site to one of the Links pages and uploads. The description used is normally the homepage summary or most of it. Steve adds the site to Google, Yahoo, MSN search, and authenticates the site using https://siteexplorer.search.yahoo.com/mysites The related sites are all updated with this new site (Clickboard and Links.htm). Steve tells author to zip site using Paste + Zip up website from the site Notes index.html page, and upload the zip. The site is built and someone might need to download it during the audit. This is also added security. The audit may take a while. AUDIT STARTED ------------- Steve proof reads the site for grammar errors and sends Neil a list of corrections needed. Neil undertakes quality audit and sends copy to Steve. Steve forwards audit to author and requests to know when amendments are done. Steve receives notification that audit amendments are done and checks the amendments against audit and refers any errors back to author until complete or passes it back to Neil for additional audit until audit amendments are fully complete. Steve emails John with the final audit url. John may query the audit with Neil, then emails Steve with an "Audit done" email. Steve then instructs author to zip up site and upload again. AUDIT FINISHED - Steve controls site Notes ------------------------------------------ Steve downloads site to his computer and unzips it to C:\ Steve undertakes the following processes, recording action on a master control list:- 1. Change "contact us" to Steve. 2. Run Fit images throughout. 3. Replace Template throughout. 4. Replace Clickboard throughout. 5. Spread Summary throughout. 6. Put in categories throughout. 7. Run broken external links check throughout and correct any errors. 8. Make duplicates throughout [must do this last]. SITE COSTS ---------- Steve utlises the Site Costs page in the site Notes section. He inserts data from author invoices and other places where known. Also inserts the current site maintainer. Steve puts the following into Site Costs:- 1. Date of the built email, see "limoz.com built" above. 2. Results of Google, Yahoo & MSN search submission. 3. Date of receipt of John's "Audit done" email. Steve does List + List A-Z Urls to get number of pages and duplicates and puts them in Site Costs page. Steve informs Neil that site is transfered from author and requests new password and sends incomplete site costs. Neil puts the current date labelled "Site completion date" in Site Costs. Neil sends new password and completed costs to Steve, John and Paul. Steve updates Site Costs page. Steve zips up site and uploads. Steve emails Paul saying that zipped site is ready to be downloaded as backup. Steve informs author that site is successfully completed and instructs author to delete site from computer. SITE COMPLETED -------------- Site written by John Middlemas