A polished front door
for HotelSchedule Maker.
Five responsive pages. Approved branding. Actual training screenshots.
A separate website that leaves your scheduling system alone.
What you received
| Page | Purpose |
|---|---|
| Home | Overview, scheduling benefits, real product screens, department examples, and a visual workflow. |
| Features | 25 feature explanations, category controls, scheduling rules, printing, and 12 seasonal-artwork previews. |
| How it works | Six illustrated steps from employee setup to published schedules, plus a practice-week procedure. |
| Mobile & team | Four layout previews, roles, English/Spanish messaging, installation, and alert expectations. |
| Help & FAQs | 28 searchable questions and links to the existing authenticated How-To Center. |
This is a static HTML/CSS/JavaScript website. It has no live employee database, login form, submission endpoint, service worker, or dependency installation.
Preview before uploading
Extract the ZIP on your computer, open the website folder, and double-click index.html. Keep the other files and the complete assets folder beside it. Browse all five pages and test the layout/FAQ controls.
The separate downloadable Information Website Preview.html embeds the same pages and images into one file. It is for review, not deployment. The preview does not sign in to or alter your system.
1. Set the application links
Open Website-Settings.html from the extracted package on your own computer. It prepares a public site-config.js file.
- Confirm the existing application's HTTPS folder address. The starting example is
https://smalltownsoft.com/comfortinn/, taken from the address in your application screenshot. Verify that it is still correct. - Leave Support email blank, or enter a public email address to show an email link. No email address or contact form was invented.
- Optionally enter the final information website URL after choosing where to host it.
- Select Download site-config.js and save it over the file with that name inside
website.
Alternatively edit website/site-config.js in a text editor. Never put passwords, API keys, database credentials, or recovery keys in this public file.
2. Upload to a new website folder
- In cPanel File Manager, create a new, separate folder, such as
public_html/hotelschedule/. A new domain's empty document root is also suitable. - Upload the contents of the package's website folder into that new folder. Preserve the folder structure below.
- Open the new folder's HTTPS address. For that example on smalltownsoft.com, it would be
https://smalltownsoft.com/hotelschedule/. This is an example destination, not a site deployed for you. - Test Features, How it works, Mobile & team, Help & FAQs, and the Open scheduler links.
public_html/
comfortinn/ Existing application - leave unchanged
hotelschedule/ New information website
index.html
features.html
how-it-works.html
mobile.html
help.html
site-config.js
assets/
site.css
site.js
images/Do not upload the root guide, source notes, tests, or local settings generator as part of the public site. Only the contents of website/ need to go online. No WordPress plugin, PHP installation, database, cron job, or npm build is required for this information site.
3. Check the finished website
- Confirm the approved navy/gold/silver logo appears on desktop and mobile.
- Open each screenshot to enlarge it; use Escape or Close to dismiss it.
- Filter the Features page, switch all four mobile layout previews, and choose several monthly artwork previews.
- Search Help for school, clear, and translation. Confirm categories and individual answers work.
- Click Open scheduler and confirm it opens your existing sign-in. Check the installation-page link and authenticated How-To link.
- Check a real iPhone and Android device. Their local browser behavior was not exercised in this build.
What is deliberately separate
The site presents scheduling features based on supplied application documentation. It does not change staff accounts, rules, schedules, logos inside the application, translation settings, device registration, or notification behavior.
The recurring notification-handler warning remains a separate application issue. This website does not repair it or claim that phone notifications are now verified.
Screenshots are from the actual application using fictional training records. Some earlier layout previews are labeled. The two small explanatory examples are labeled illustrations, not live data or verified translation results.
No customer testimonials, user counts, hotel-chain endorsements, prices, or paid plans are invented. The complete owner-only guide and application credentials are not published on the information site.
Editing and maintenance
Edit the HTML files for text, assets/site.css for appearance, and site-config.js for app/support links. Replace public branding images deliberately; changing a text setting cannot alter the lettering already drawn inside an image.
The site uses system fonts, local images, and plain JavaScript. No external fonts, analytics, paid design libraries, or cookie-tracking scripts are installed. Your hosting provider may retain ordinary access logs.
Each page includes its own title, description, language, heading structure, and image alternatives. Enter a final site URL for optional canonical metadata. Search indexing and rankings are not guaranteed.
Validation boundary
Responsive layouts and interactive controls were tested using Chromium with the actual website files. A test-only resource bridge was needed because direct browser navigation was restricted; local HTTP file delivery was checked separately. No application/database behavior was simulated or modified by the website.
Read VALIDATION.json for the recorded checks. Live deployment, existing account sign-in, native Safari/Firefox, physical phones, notification delivery, translation, and production indexing remain unverified.