Default Site Setup
Learn what default files, folders and assets to expect in your Aggie UX Cascade site.
When you first open your new Aggie UX Cascade site, there will be several default pieces of content included in your site.
Note: Depending on your access level, you may not see all default folders, pages and blocks.
Default System Level Folders
Default system level folders’ names start with an underscore (i.e., _example). These folders hold various files and assets that make your site work or give you an organized place to store assets.
Each folder has specific configurations that determine whether or not assets within the folder are indexed or published.
_archive
Configuration: not indexed and not published
This folder is a good place to store content that you may need to reference or republish later.
_assets
Configuration: indexed and published
This folder contains the CSS, JavaScript and other assets required to make the Aggie UX display appropriately.
CAUTION: do not touch the contents of this folder; they are required to make the templates work correctly.
_cascade
Configuration: not indexed and not published
This folder contains all of the Cascade administration assets, such as blocks, formats and templates, required to make the Aggie UX templates work.
CAUTION: do not touch the contents of this folder; they are required to make the templates work correctly.
_custom-content-blocks
Configuration: indexed and not published
Inside this folder, you’ll find several folders that organize the custom content blocks. Custom content blocks allow you to edit all reusable content throughout your site in one place.
Some of these blocks are content that can be added to pages; others are blocks that control functionality on your site.
_custom-content-blocks > content blocks
Configuration: not indexed and not published
Use the content-blocks folder as a place to store any reusable content blocks that you create for your site.
_custom-content-blocks > events-news
Configuration: not indexed and not published
Use the events-news folder as a place to store any calendar or news feeds used on your site. By default, there are three sample feeds you can use in this folder:
- LiveWhale Calendar Feed RSS – No Repeated Events: Pulls a feed of featured events from the university calendar on calendar.tamu.edu and hides repeated events
- LiveWhale Calendar Feed RSS – Repeated Events: Pulls a feed of featured events from the university calendar on calendar.tamu.edu and shows repeated events
- Stories News RSS Feed: Pulls a feed of news and story posts from stories.tamu.edu
_custom-content-blocks > google-tags
Configuration: not indexed and not published
The google-tags folder stores blocks that allow you to set up Google site search, Google Tag Manager and Google Analytics 4.
Learn how to set up Google Analytics and search
_custom-content-blocks > header-and-footer-scripts
Configuration: indexed and published
The header-and-footer-scripts folder stores blocks that allow you to insert up to five scripts to appear in the footer or header block on every page.
_custom-content-blocks > site-alerts
Configuration: indexed and published
The site-alerts folder stores blocks that allow you to have sitewide alerts, either using the Aggie UX alert banner component with content controlled on the site or display Code Maroon university emergency alerts.
Learn how to turn on sitewide alerts
_custom-content-blocks > site-information
Configuration: not indexed and not published
The site-information folder stores a Site Information block, which contains site details such as the owner and classification. It also acts as a hub for accessing blocks that control site settings.
_example-content
Configuration: not indexed and not published
The _example-content folder contains a small demo site build that shows what a college site could look like using Aggie UX templates and components. You can refer to the content in this folder for inspiration when building your site or delete it if you don’t need it.
_external-site-links
Configuration: not indexed and not published
This folder is where we recommend you store external link assets for your site.
Keeping all of the external link assets in one place can make them easier to find when you’re editing your site.
_files
Configuration: indexed and published
This folder is where we recommend you store your various media files, including images and documents.
Keeping media files in one place can make them easier to find when you’re editing your site. For complex sites, you may even want to add additional nested folders to help organize your files even further.
_json-data
Configuration: indexed and published
This folder contains the files used for dynamic components, including news, profiles, and the searchable/sortable table.
Please do not touch anything in this folder unless you are editing content for the searchable/sortable table component.
_menu
Configuration: not indexed and not published
This folder contains all of the necessary blocks to edit your site’s navigation and footer.
Learn how to edit your site’s navigation
Learn how to edit your site’s footer
_test
Configuration: not indexed and not published
This folder provides a place to build out test pages to test functionality or build out new pages before moving them into the production area of the site.
By default, the _test folder has the indexing and publishing configure settings turned off, so anything you make in this folder won’t accidentally get published to your live website, even when republishing your whole site.
Default Pages
These pages come with each site and are essential to enabling core website functions.
Warning:
Do not delete, rename or move any of these pages as they are essential for core functionality.
404
The 404 page, found in the error folder, is the page browsers return when it can’t find a file based on the input URL. You can edit the content on the 404 page, but do not rename the page or folder it is in.
Search
The search page enables on-site search, powered by Google Programmable search engine.
Sitemap
The sitemap allows search engines to crawl your site and make them available as search results.
Your sitemap is automatically configured to update as you create, move, rename and delete pages.
Invalidate Cache
The invalidate cache page is an internal tool developed to enable you to invalidate the cache for your entire site, or a specific page or folder. This forces our caching servers around the globe to load the new file, which can be helpful when an urgent change (like an emergency alert) has been added to your site and you need everyone to see the change immediately.
Note: this tool should only be used when urgency demands it; each use of the tool costs money and wipes the cache of your site, meaning the caching servers will redownload all assets (e.g., web pages, CSS, JS, images, PDFs, etc.) to view your site.
Rewrite Rules
The rewrite rules page is an internal tool developed to enable you to add redirect rules for your site. This is important when you move a published page to a new location or change its file name. A redirect will take visitors to the new location instead of showing them a 404 page and it asks search engines to update their results with the new address.
Index (home page)
The index page at the root of the site is your home page.