Skip to main content
Parsepad
Search tools
Theme

Saved on this device only.

Last updated

Project Cleanup Audit (ToolNexus Web)

I did a full pass across controllers, Razor views, runtime loaders, manifests, and static assets.

Scope I audited

  • Controllers and action results (return View(...), explicit view names)
  • Shared/Admin layouts and partial view usage
  • Tool runtime wiring (tool-runtime.js, runtime loader modules)
  • Tool manifest resolution (App_Data/tool-manifests/*.json + ToolManifestLoader)
  • CSS and JS static references from Razor + manifest loader conventions

Runtime-critical files (kept intact)

These were verified and intentionally left untouched:

  • /wwwroot/js/tool-runtime.js
  • /wwwroot/js/runtime/tool-template-loader.js
  • /wwwroot/js/runtime/tool-lifecycle-adapter.js
  • /wwwroot/js/runtime/tool-execution-normalizer.js
  • Runtime orchestrator / tool execution engine wiring in the runtime JS folder

Razor view classification

USED FILES

  • Controller-backed pages under Views/Home, Views/Tools, Views/Docs, Views/Auth, Views/Changelog, Views/Roadmap, Views/Feedback
  • Shared layouts and core partials (_Layout, _Header, _Footer, _Sidebar, _ToolCard)
  • Admin views and shared admin partials (Areas/Admin/Views/**)
  • Tool plugin partials loaded dynamically from ToolShell (Views/Tools/Plugins/_*Plugin.cshtml)

UNUSED FILES

  • Views/Home/_Hero.cshtml (not referenced by any controller action, parent view, layout, or partial render)

POSSIBLY USED (dynamic references)

  • Views/Tools/Plugins/_*Plugin.cshtml (loaded via dynamic partial name in ToolShell.cshtml)

CSS classification

USED FILES

  • Global UI system CSS linked by _Layout.cshtml
  • Tool shell CSS linked by ToolShell.cshtml
  • Tool CSS selected dynamically by manifest loader (/css/tools/{slug}.css then /css/pages/{slug}.css fallback)

UNUSED FILES

  • Entire backup tree: /wwwroot/css/_experiment_backup/**
    • No references in Razor, controllers, manifests, or runtime loader paths
    • Folder appears to be historical snapshot files

POSSIBLY USED (dynamic references)

  • Per-tool styles under /css/tools and /css/pages because they can be selected by manifest/runtime conventions

JavaScript classification

USED FILES

  • Runtime core scripts and runtime module folder
  • Tool modules resolved by manifests and loader conventions (/js/tools/{slug}.js, .app.js, nested index/main.js patterns)
  • Shared interaction scripts referenced from layouts/pages

POSSIBLY USED (dynamic references)

  • Tool-specific JS modules under /wwwroot/js/tools/** because module paths can be set via manifest JSON or generated conventions

JSON/config classification

USED FILES

  • appsettings*.json (environment/runtime configuration)
  • Tool manifests under App_Data/tool-manifests/*.json (runtime tool registry input)

POSSIBLY USED (deployment/runtime)

  • Environment-specific config files and launch settings not always loaded locally but required by specific host profiles

What was safely removed

  • Views/Home/_Hero.cshtml
  • wwwroot/css/_experiment_backup/ (all contained CSS backups)

Folder-structure outcome

The live app structure already aligns with your requested shape for active paths:

  • /Controllers
  • /Views (including /Views/Shared and /Views/Tools)
  • /wwwroot (/css, /js, /assets)

The removed backup folder reduced clutter without changing runtime paths.