Hi everyone, I haven’t worked on my website in a while and would now like to update some features. Unfortunately, the tutorials I’ve found online are hopelessly outdated.
Custom Styles for Subdomains: I’d like to give my subdomains a custom design. Specifically, I want to assign subdomain its own fonts and color scheme. What’s the cleanest and most efficient way to implement this today?
Not 100% sure but I think there is no such feature. I think you need to do it manually element by element.
Hi Nicole, just to clarify: are your subdomains separate Sitejet website projects, each published to its own subdomain?
If they are separate projects, wouldn’t each one have its own Design settings, where you can define its fonts, colors and other global styles independently? In that case you shouldn’t need to style everything element by element.
Or are you referring to multiple subdomains/pages that are managed within the same Sitejet project? If so, that’s a different case and custom CSS may be the cleaner solution.
Is it now possible to assign a separate project to a subdomain?
As far as I know,
I can convert a subpage into a subdomain in the site panel,
and then it would be within a project;
if it were now possible to assign a project to a subdomain, that would indeed solve the problem.
That is technically not possible because a domain can only be existent once in our system.
Any examples of outdated help articles about your issue?
What you want to do is rather a fringe case - that is a crucial insight for how to proceed.
You are able to set custome fonts, custom colours and even custom code and custom CSS classes (if needed) and use them on the subdomain. I guess it depends on how many fonts and colors you have already set on the main page… as especially the custom colors are limited to 5 (in addition to the 4 main ones).
With custom fonts, there is no limit. 
If you like, please raise a feature request to give more custom color fields (or even a completely separate style set)
Hey @Kalisperakichris congrats on the “Guidance Counsellor” 
Thank you for your reply. I believe there might be a slight misunderstanding regarding what I am trying to achieve technically.
1. Regarding the domain / subdomain issue:
I do not intend to duplicate the domain. My goal is to set up a genuine subdomain (e.g., ://my-domain.com) as an independent instance or a completely separate project. If your system cannot treat a subdomain as an independent project with its own unique style settings, that is precisely where the issue lies.
2. Why the design breaks during copying:
I have already built the case study as a completely finished, separate project with its own custom fonts and colors within your system. The issue arises when I try to copy this finished project over to the subdomain. Instead of keeping its original styling, the layout completely breaks—likely because the system forces the copied content to inherit the global styles or color limits of the main website.
3. Regarding the “special case” and help articles:
I am quite surprised by the suggestion that wanting a different design on a subdomain is considered a rare or special case. In web design, subdomains are standard practice for hosting landing pages, online shops, or separate portfolios (like case studies) that need to be visually independent of the main website.
If I have to be a CSS expert just to keep my already created design intact when moving it to a subdomain, the primary benefit of using a website builder is lost. Submitting a feature request for more color fields does not help me right now, as I need to get this project online immediately.
My specific question for you:
How can I copy my already finished, separate project into this subdomain without losing its unique fonts, colors, and styling? Is there a way to disconnect the subdomain entirely so it does not inherit anything from the main site?
Hey Nicole,
Thanks for your reply.
I did not mention a duplication of the domain. I explained that a domain can only exist once in the system. For a subdomain to exist, the main domain needs to be set up in the domain manager. Therefore, there is only one CMS connected to the domain. No matter if you use the main domain or “just” the subdomain. Most modern website builders use this infrastructure.
And for your case, I see the issue if you want to have completely separate style settings. However, there have been cases, where users used correct code, the global design settings and CSS classes to realize that.
Actually, you describe “when” the design breaks. I understand that you build this on a separate page and then try to copy the code over to the legacy page? Am I correct?
Would you be able to provide us with the Website ID and screenshots/screencasts of the breaks and the copy? If you do not like to share it here, please open a ticket and copy the community post link as well, so I can connect these
Our support is also in German, in case you prefer it.
Regarding the “special case”. Well, in the past 5 years we just had maybe four to five questions about this / reports about this issue (including yours). I am sorry to be so direct, but …
… but that is not standard practice in webdesign. It is correct, that subdomains are used to solve “technical challenges” like for shops, blogs, apps, or localized content etc.
While creating a completely visually distinct case study is a great idea, treating a subdomain as a totally disconnected visual canvas is actually counter to modern UX and security best practices. From a cybersecurity and user-trust perspective, suddenly changing design systems on a subdomain triggers immediate red flags for modern web users. Even domain registrars and cybersecurity organizations explicitly advise against big changes in the design on subdomain.
That is not the direct reason why Sitejet is set up like it is, but a good argument for how our system is designed.
About your specific question: If you send me a ticket with the details (as well as a screencast to see how you do it) I can ask my colleagues to give some hints and some ideas. But please be advised that we have a very limited support for code / third party code and the likes.
But I think, maybe I can help you better, when I see the project/websites 