# IET Support Center Website Review - Project Plan & Timeline # 1. Project Overview & Objectives ... # 2. Scope of Work ## A. UX Design & Review The TeamDynamix (TDX) client portal layout will undergo a rigorous usability review to optimize navigation, search layout, and information hierarchy. - **Existing Design Review**: Map out and analyze current page hierarchy, widget placement, user navigation paths, and drop-off points across support.stedwards.edu. > [!note] Web Design in TDX > In order to avoid unnecessary confusion and improve training efforts for students taking on tasks related to styling articles, service pages, and more, I believe it would be best to include some explanation for unusual and seemingly arbitrary methods for styling pages with `CSS`. > > Styling our support portal using the provided admin's "**Styling**" page is extremely limited, as you can see in the screenshot below. > > ![[Pasted image 20260903145955.png]] > > Achieving the looks we want for articles and other pages is simply impossible using the provided TDAdmin Styling page. > > However, if you were to **Edit** a KB article using the included web-editor, and click on `Source` to reveal the code underlying what's displayed on the page, you'll notice some peculiarities: > > - Inline `style="..."` attributes on individual elements everywhere > - **Zero** `<style>...</style>` blocks *anywhere* > - **Zero** external stylesheets being linked in > > **NOTE**: it's much easier to paste the `Source` code into your favorite text editor (I'm using Zed in the screenshot) that includes syntax highlighting, as opposed to trying to edit code in the web editor. > > ![[Pasted image 20260903154836.png]] > > # **Vs.** > > ![[Pasted image 20260903154644.png]] > > This is because `<style>` blocks, importing external stylesheets, and a number of other properties, codeblocks, and more are simply **disallowed**. When you write content into that text editor, it's stored as raw `HTML` and rendered back out to every visitor who views the page. As you might be able to guess, however, this presents a potentially enormous security risk: someone could write some code to be processed and rendered to the site by the server, and, *woops*, turns out that code was malicious and now you have a bad actor on the server hosting your entire support portal. > > To prevent this from happening, TDX runs all the source code of the content you just created through a server-side sanitizer. That sanitizer checks every HTML tag, every HTML attribute, and every CSS property used against an **allowlist**, and anything not on that list is silently stripped before the page renders. > > This is why you might edit an article, see something render correctly in the editor, save it, and then find it's gone (or altered) on the live page — the editor doesn't enforce the same rules as the final render. > > Given that `<style>` blocks are permanently off the table, the *only* way to apply CSS to an element is directly on that element, via its `style="..."` attribute. For an authoritative source on the allowlists, check out the article [TDX: Sanitization and HTML Content Allowlists](https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/Article/48230/Sanitization-and-HTML-Content-Allowlists). > > TDAdmin's also have the ability to add HTML elements and attributes, CSS properties, Iframe sources, and script sources to HTML allowlists. However, some are permanently disallowed. If you are unsure, or think that adding something might be useful, contact any of the admin and let them know. - **Layout & Formats Design**: Develop ~~responsive wireframes and high-fidelity~~ mockups for updated portal homepages, catalog landing pages, and article display formats. Focus on digital accessibility ~~(WCAG 2.1 AA compliance), modern grid layouts~~, and visual clarity within acceptable code standards for TeamDynamix. - [Sanitization and HTML Content Allowlists (TDX)](https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/Article/48230/Sanitization-and-HTML-Content-Allowlists#Understanding%20HTML%20Sanitization) - **A/B Testing & Feedback**: Organize structured A/B testing sessions with representative user cohorts (students, faculty, and staff) using live prototypes to empirically validate changes before full deployment. ## B. Knowledge Base (KB) Article Audit A systematic overhaul of existing content will address findings from preliminary audits (e.g., redundant links, broken URLs, and duplicate titles such as multiple variations of "MFA”). - **Propose Standard Article** **Types**: Establish four core article types: - **How-To**: Step-by-step technical guides for routine tasks (e.g., Setting up MFA, activating accounts, connecting to campus Wi-Fi). - **Position**: Explanatory or advisory content explaining strategic rationale (e.g., Explaining Security Keys and Identity Protection standards). - **Procedure**: Structured operational workflows (e.g., onboarding new employees, submitting software acquisition requests). - **Policy**: Formal university or divisional IT policies (e.g., Technology Selection Policy, Data Privacy Standards). - **Industry Standards & Templates**: Incorporate Knowledge-Centered Service (KCS) and IT Service Management (ITSM) standards to build reusable templates for each article type. - **Implementation & Clean-Up**: Apply standardized templates to high-traffic articles, eliminate duplicate entries, archive obsolete documentation (e.g., retired MFA tools), and correct broken links. - **Search and Efficiency Optimization**: Refine indexing attributes, tags, and metadata within TeamDynamix to enhance search accuracy within both the internal portal and main university search queries. --- # HTML Version for KB