Virginia Tech® home

Project request

CALS and VCE Marketing and Communications - Asana requests

Please use this link to submit news story, social media, alumni engagement, website, and design requests to the Marketing and Communications team. If you have any questions, please contact Tom Soladay.

Submit a Marketing & Communications request

Virginia Cooperative Extension Publications - WorkZone requests

Please use this link to submit VCE peer and non-peer publication requests. If you have any questions, please contact Lori Greiner.

Submit a Publications request

Virginia Cooperative Extension web ecosystem stabilization efforts

We are currently working to ensure that the Virginia Cooperative Extension main site, publications site, and local office sites are Title II-compliant by the federally mandated April 2026 deadline.

Bolded bullet points indicate the current work in each domain.

If you have any questions, comments, or concerns regarding this effort, please email Chris Mitchell (cmitch41@vt.edu), Web Manager for CALS/VCE/VAES.

Extension site

DEPLOYED AND OBSERVING...

Publications site

IN PROGRESS...

Local office sites

PROTOTYPING SOLUTION...
  1. Inventorying...
    1. Key pages, components, and features
    2. Third-party and custom code ("custom code")
    3. Current information architecture ("IA", patterns of CMS content and asset hierarchy)
  2. Measuring...
    1. Baseline performance, accessibility, best practices, and SEO of key pages
    2. Key performance indicators ("KPIs") via Google Analytics
  3. Brainstorming and testing high-impact remediations for...
    1. Accessibility
    2. Performance
    3. Author usability
    4. SEO
    5. Coherence
  4. Triaging problem-spaces and potential remediations, optimizing for high-impact, low-disruption fixes at a structural level
  5. Rolling out remediations in triage order
  6. Measuring effects of remediations via DubBot (site-wide) and Lighthouse (page-level)
  1. Inventorying...
    1. Key pages, components, and features
    2. Third-party and custom code ("custom code")
    3. Current information architecture ("IA", patterns of CMS content and asset hierarchy)
  2. Measuring...
    1. Baseline performance, accessibility, best practices, and SEO of key pages
    2. Key performance indicators ("KPIs") via Google Analytics
  3. Brainstorming and testing high-impact remediations for...
    1. Accessibility
    2. Performance
    3. Author usability
    4. SEO
    5. Coherence
  4. Triaging problem-spaces and potential remediations, optimizing for high-impact, low-disruption fixes at a structural level
  5. Rolling out remediations in triage order
  6. Measuring effects of remediations via DubBot (site-wide) and Lighthouse (page-level)
  1. Inventorying...
    1. Key pages, components, and features
    2. Third-party and custom code ("custom code")
    3. Current information architecture ("IA", patterns of CMS content and asset hierarchy)
  2. Measuring...
    1. Baseline performance, accessibility, best practices, and SEO of key pages
    2. Key performance indicators ("KPIs") via Google Analytics
  3. Brainstorming and testing high-impact remediations for...
    1. Accessibility
    2. Performance
    3. Author usability
    4. SEO
    5. Coherence
  4. Spike*: Testing feasibility of unifying local office sites under ext.vt.edu/offices/<office-slug> for SEO and coherence gains.
  5. Triaging problem-spaces and potential remediations, optimizing for high-impact, low-disruption fixes at a structural level
  6. Rolling out remediations in triage order
  7. Measuring effects of remediations via DubBot (site-wide) and Lighthouse (page-level)

* - spike (n): a time-boxed, short-term investigation or prototype used to research, analyze, or reduce uncertainty regarding complex, unknown, or high-risk tasks