TDesk technical documentation
Deploy & verify
Host the templates as static files or deploy them inside an application. Use this checklist before release.
Host the right files
Product showcase: To publish the landing page with all three demos, upload the contents of the CodeCanyon/ folder to a directory on your host, keeping index.html, landing-assets/, front/, admin/, legacy/, prototype/, and documentation/ together. Use index.html as the directory entry point. Open the product landing page.
For static hosting, copy front/, admin/, and documentation/ into the web root. Keep relative links intact; make each folder’s index.html its default document. If using a path prefix such as /support/, verify that nested pages can still reach CSS, fonts, and scripts.
For a real admin app, serve its authenticated routes through the server or gateway. If you add a router, test refreshing a nested route directly. Configure real 403, 404, and 500 HTTP responses before using the admin’s error layouts.
Check the user flows
- Open the portal and admin entry points, then follow the ticket and knowledge base detail links.
- Test at phone and desktop widths. Verify menu scroll, keyboard focus, and dialog close behavior.
- Try empty, invalid, successful, and failed submissions with test data. Verify that live accounts and tickets survive a reload after integration.
- Inspect browser console and network requests. Check filename case, MIME types, and HTTPS before publishing.
- If embedding a live preview, test storage and navigation inside the preview iframe as well as directly.
Troubleshooting
| Symptom | Check |
|---|---|
| No styles or icons | Keep the CSS, font files, and vendor folders in their original relative positions. Check exact filename case. |
| Menus or forms do nothing | Check the page scripts are loaded with defer in the original order and inspect the first console error. |
| Demo changes disappear | Use a stable HTTP origin and allow browser storage. Local demo records are isolated by browser and origin. |
| React page behaves twice | Remove the matching DOM-driven demo script and keep one owner for each control. |
| Reply editor is blank | Verify Jodit CSS and JS load before ticket-editor.js; keep the textarea as a fallback. |
Bundled assets and credits
| Asset | Bundled notice location |
|---|---|
| Bootstrap 5.3.8 | vendor/bootstrap/LICENSE |
| Font Awesome Free 7.3.1 | vendor/fontawesome/LICENSE.txt |
| Simple Line Icons 2.5.5 | vendor/simple-line-icons/LICENSE.txt |
| Plus Jakarta Sans | assets/fonts/plus-jakarta-sans/OFL.txt; the guide copy has assets/OFL.txt. |
| Jodit Community 4.19.10 | front/vendor/jodit/LICENSE.txt |
Keep the included notices with the corresponding assets.