{"schemaVersion":1,"siteOrigin":"https://jeremyfontenot.online","pages":[{"id":"systems-skills","route":"/systems-skills/","outputPath":"systems-skills/index.html","title":"Systems Skills | Jeremy Fontenot","description":"A task-based view of Jeremy Fontenot's professional IT support foundation and demonstrated junior systems administration capability.","eyebrow":"Systems skills","headline":"Practical responsibilities connected to demonstrated capability.","summary":"This route organizes the portfolio by the work a junior administrator performs, then connects each responsibility to professional experience, personal-lab evidence, scope, and limitations.","primaryActions":[{"label":"Review job readiness","href":"/systems-administration.html","style":"primary"},{"label":"Explore Microsoft 365","href":"/microsoft-365/","style":"default"},{"label":"Explore the Home Lab","href":"/home-lab/","style":"default"},{"label":"Inspect evidence","href":"/evidence/","style":"text"}],"sections":[{"id":"identity","eyebrow":"Identity and access","heading":"Support identity records and access paths.","summary":"Professional support experience and lab evidence connect user symptoms to accounts, groups, roles, policies, authentication, and directory services.","cards":[{"code":"IAM","title":"Maintain users and groups","text":"Create or update identity records under procedure, review membership and assigned roles, verify access state, and document changes.","href":"/microsoft-365/","linkLabel":"Review cloud identity capability"},{"code":"AD","title":"Support directory services","text":"Review domain structure, organizational units, users, groups, Group Policy, secure channels, and directory-service indicators.","href":"/home-lab/","linkLabel":"Review Active Directory capability"}]},{"id":"systems","eyebrow":"Systems operations","heading":"Perform routine server, service, and virtualization work.","summary":"The evidence supports bounded administration tasks completed within documented procedures and escalation paths.","cards":[{"code":"SRV","title":"Review server and service state","text":"Inspect roles, services, storage, event summaries, DNS, DHCP, logging, updates, and operational indicators.","href":"/home-lab/","linkLabel":"Review infrastructure capability"},{"code":"VM","title":"Support virtual machines","text":"Maintain inventories, review compute and storage state, inspect guest integration, and follow approved lifecycle procedures.","href":"/home-lab/","linkLabel":"Review virtualization capability"},{"code":"M365","title":"Review cloud administration state","text":"Inspect tenant, identity, license, policy, application, sign-in, audit, and admin-center evidence within assigned permissions.","href":"/microsoft-365/","linkLabel":"Review Microsoft 365 capability"}]},{"id":"operations","eyebrow":"Operational discipline","heading":"Automate, validate, document, and escalate.","summary":"The strongest job-readiness signal is the combination of technical work and safe operating habits.","cards":[{"code":"AUTO","title":"Run repeatable checks","text":"Use PowerShell for inventory, validation, structured export, sanitization, integrity checks, and repository quality.","href":"/projects.html","linkLabel":"Review automation work"},{"code":"BKP","title":"Review backup coverage","text":"Confirm scheduled scope, archive state, storage, supported integrity checks, controlled restore procedures, and cleanup.","href":"/home-lab/","linkLabel":"Review backup capability"},{"code":"DOC","title":"Escalate with evidence","text":"Separate confirmed results from inconclusive or untested conditions and provide observations, scope, commands, and next actions.","href":"/evidence/","linkLabel":"Review the evidence model"}]}],"scopeHeading":"Ready to contribute within established controls.","scopeText":"The portfolio supports junior systems administration and infrastructure support readiness. It does not present personal-lab work as employer work or claim unsupported production ownership."},{"id":"evidence","route":"/evidence/","outputPath":"evidence/index.html","title":"Evidence Architecture | Jeremy Fontenot","description":"A recruiter-friendly guide to how portfolio claims connect to tasks, results, proof, provenance, scope, and limitations.","eyebrow":"Evidence architecture","headline":"The skill comes first. The artifact verifies it.","summary":"This route explains how public claims connect to supporting artifacts without turning raw files into the main portfolio experience.","primaryActions":[{"label":"Open the proof index","href":"/proof.html","style":"primary"},{"label":"Browse the evidence library","href":"/evidence-library/","style":"default"},{"label":"Review evidence status","href":"/dashboard.html","style":"default"},{"label":"Review systems skills","href":"/systems-skills/","style":"text"}],"sections":[{"id":"sequence","eyebrow":"Presentation sequence","heading":"Five questions guide every proof relationship.","summary":"Recruiter-facing pages explain relevance before exposing raw artifacts.","cards":[{"code":"01","title":"Skill","text":"What technical capability is being demonstrated?","href":"/systems-skills/","linkLabel":"Review systems skills"},{"code":"02","title":"Task","text":"What administrative or troubleshooting work was performed?","href":"/projects.html","linkLabel":"Review technical work"},{"code":"03","title":"Result","text":"What was directly validated, configured, documented, inconclusive, or not tested?","href":"/dashboard.html","linkLabel":"Review status relationships"},{"code":"04","title":"Proof","text":"Which public artifact, manifest, screenshot, export, script output, or report supports the claim?","href":"/proof.html","linkLabel":"Open the proof index"},{"code":"05","title":"Scope","text":"What environment, access boundary, limitation, and unsupported conclusion must remain visible?","href":"/systems-administration.html#boundaries","linkLabel":"Review readiness boundaries"}]},{"id":"routes","eyebrow":"Evidence routes","heading":"Existing proof surfaces remain available.","summary":"The architecture foundation adds a stable hub without replacing the established proof, dashboard, library, or case-study routes.","cards":[{"code":"MAP","title":"Claim-to-artifact proof","text":"Primary recruiter-facing proof relationships and limitations.","href":"/proof.html","linkLabel":"Open Proof"},{"code":"LIB","title":"Evidence library","text":"Public artifacts, generated pages, preserved exports, manifests, and supporting records.","href":"/evidence-library/","linkLabel":"Browse the library"},{"code":"STA","title":"Evidence status","text":"Relationships among validated, tested, configured, documented, inconclusive, and not-tested results.","href":"/dashboard.html","linkLabel":"Open the dashboard"},{"code":"LAB","title":"Home Lab case study","text":"System context, technical work, validation outcomes, and limitations.","href":"/on-prem-home-lab.html","linkLabel":"Open the case study"}]},{"id":"contract","eyebrow":"Catalog contract","heading":"Every migrated record will carry provenance and boundaries.","summary":"Later evidence phases must use the repository schema and migration contract rather than inventing new field sets.","cards":[{"code":"SRC","title":"Source provenance","text":"Source repository, original path, source commit, integrity identifier, and collection context.","href":"/evidence/#contract","linkLabel":"Read the architecture contract"},{"code":"REL","title":"Claim relationship","text":"Skill, task, result, supported claim, proof route, scope, and limitation.","href":"/evidence/#contract","linkLabel":"Review relationship rules"},{"code":"PUB","title":"Publication classification","text":"Public original, sanitized derivative, metadata-only record, or source-reference-only entry.","href":"/evidence/#contract","linkLabel":"Review publication rules"}]}],"scopeHeading":"Preservation without overstatement.","scopeText":"Original artifacts remain preserved. Public presentation can use generated pages, summaries, or sanitized derivatives, but the source record and claim boundary must remain traceable."}]}