Creating a new sub-site in Tridion
We will need to assist you with some of the steps below, but you can begin the process below. Please follow sections 1 & 2, and then submit a MNIT Service Hub ticket to us when you get to section 3.
Looking for help? Submit a Support Ticket and we will assist.
This optional header box, called a Toggle Box, can be used for highlighting whatever content you would like. This is a rich-text field, so you can add links, images, bullets, etc.
You can edit it through the Header component on your website.
We will need to assist you with some of the steps below, but you can begin the process below. Please follow sections 1 & 2, and then submit a MNIT Service Hub ticket to us when you get to section 3.
To begin, you'll need to create a folder for your subsite where the Header, Footer, Navigation, and Head Tag will reside.
Please submit a MNIT Mall Website Service Request ticket when you get to this section and include the name/location of the structure group created in Step 1. The MNIT Enterprise Web Team will take care of the remaining steps.
Every site has a site template - a file that instructions the system which components to use for the site's header, footer, head tag, site name, and navigation (top and left menus).
For your new sub-site, you'll need to make two LESS files - one for the Custom file and one for the Variables file.
Your sub-site requires its own CSS page within the CSS structure group for your site.
Publish the following items:
Sub-sites are notoriously tricky to create and a lot of things can go wrong. Below are some common problems encountered during the creation process, and how you can fix them.
If the structure group or page fails when you publish it, the most likely reason is because the URLs in the Site Template Keyword are incorrect. The URLs are case-sensitive and also must contain the correct path for all components. Here are some things to inspect:
Once you've fixed any issues or typos, try publishing your structure group again (and don't forget to uncheck the "Republish only" box!).
If it continues to fail, and you cannot find any incorrect paths or typos anywhere, check to see if your subsite name has a number (or numbers) in it. There are certain fields that fail when numbers are used. To resolve this, see the instructions under "The CSS fails to publish" for replacing the numbers in the building blocks for your sub-site.
If it still continues to fail, check your Site Head Tag template building block. It needs to be connected to a component template, AND the name of the component template MUST match the name of the template building block.
If this happens, you'll see your content displayed on a white background, but it will have no styling applied (everything will be left justified and images may be huge). If you go to the CSS file directly in your browser, you may see a message that says "Images Not FoundImages Not Found."
This happens when the subsite cannot locate the CSS file. To resolve this, make sure you have set up the LESS files as instructed above.
Once you have confirmed that the LESS files were established properly, the next thing to rule out is having numbers in your subsite name. If your subsite name contains a number, the system cannot handle this. You will need to go back and change all numbers to words (like "20" to "twenty") in the following places:
Once you've updated these, republish the core-yoursubsite.css file. Then open your subsite's structure group properties and check to make sure the site template is now showing the revised keyword in the Site Template field. Finally, republish your structure group (unchecking the "Republish Only" box). Your CSS should publish after making these changes.
This happens when the respective URL path for the component is wrong in the site template. We just need to track down the right component, update the site template with the correct URL, and republish the structure group.
Once you've successfully published everything, and built out your site, if you ever need to make changes to your site template you will also need to republish the structure group you created in step 1. Doing so will republish everything on your site, so be cautious of this before publishing. Consider publishing at the end of the day (when the queue is less full) and also make sure there isn't any content that will accidentally be pushed live before you're ready.