I have this script and I want to make a new design for it. Also I want a mobile edition for it.

I would like the design to be similar to couponcodes.com - light blue/gray colors - black text. Would like the mobile site to use the same color scheme. So I want the template to be integrated in the script ( in a .zip file ), with option in the Admin, so that I can change from the actual template to the new one. This way if I install the script ( the .zip file) on any domain I would have the 2 templates available.

I also want to know how can I add the template on an existing domain - you might have to do it.

Dani AI

Generated

A practical, low-risk way to deliver what asked for is to make the site themeable and mobile-first rather than building two separate codebases. That keeps maintenance small and ensures the mobile edition uses the same color variables and assets. Treat ’s observation about “random” markup as a gating issue: if the HTML and CSS are not modular, plan time to refactor before theming. ’s suggestion to start from a lightweight starter template is useful — use a small, well-structured base to avoid carrying legacy layout problems into the new theme.

Minimum viable implementation (ordered): audit the codebase and identify template entry points; extract presentation into a theme folder structure (templates, css, images, manifest); use CSS custom properties for the color palette so switching themes only changes variables; build an installer that accepts a theme .zip, validates a simple manifest, unpacks to /themes/, and registers the theme in a settings table; add an admin UI to upload/activate themes and a safe fallback to the default theme. A tiny manifest example:

{
  "name": "BlueGray",
  "version": "1.0.0",
  "author": "@aditd",
  "colors": {
    "primary": "#4aa3e0",
    "muted": "#f4f6f8",
    "text": "#111111"
  },
  "breakpoints": { "mobile": "480px", "tablet": "768px" }
}

To add a theme on an existing domain: create a full file + DB backup, deploy to a staging URL (subdomain or local copy), upload the theme zip via admin or SFTP, run the installer, check permissions and caching, then smoke-test core flows (pages, search, coupon redemption, payment/test gateways). Only push to production after the staging pass.

Troubleshooting notes and cautions: watch for inline styles and high-specificity selectors that override variables; ensure the meta viewport tag is present; clear server and CDN caches after activation; prefer responsive grids to separate mobile templates to cut future effort. Budget-wise, a clean codebase + a single responsive theme can be done quickly; if significant HTML refactoring is required, expect more time and cost than a simple skin.

Recommended Answers

All 4 Replies

Member Avatar for Member #120589

you might have to do it

How much?

Under 250$

Member Avatar for Member #120589

That's a pretty big project. You have all the underlying code (HTML [pages], javascript, databases, payment gateway scripts and server-side script) and just want the template design?

I'm just saying this since the underlying CSS and markup seems a bit 'random'. In addition, to change this to mobile-friendly would probably mean making it responsive as opposed to creating two different versions of the same site. Is the markup set in stone, or can it be changed?

has some good starter templates that are light grey by default. The css in the pages is easily changed to incorperate light blue. You'll have to change them in include mobile friendly code yourself though. hope this helps

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.