Jason Knowles
Senior Software Engineer
Showcase of customizable and configurable features from every theme.
This is an example of a “custom” type of theme for my portfolio. All features within each theme are driven by a JSON file, this paragraph among them. I built this portfolio to demonstrate my expertise in multi-tenant platform configuration and accessible design, as I am very interested in full-stack engineering opportunities that extend deep front-end architecture into end-to-end product work.
Classifieds Section Typically Seen in Newspapers
A portfolio widget demonstrating self-classifieds in classic newspaper advertisement form.
Same portfolio, customizable themes
Each theme has its own self-contained JSON configuration, fetched server-side and applied client-side. This modular architecture allows for quick expansion, easy customization, and clean separation of content from code.
Default
Clean modern baseline: neutral palette, sans-serif type.
Newspaper
Editorial broadsheet aesthetic: cream paper, warm ink, masthead red, high-contrast serif type.
Terminal
Classic CRT terminal aesthetic: near-black background, phosphor green text, cyan accents, monospace throughout.
Custom
Every widget enabled. Interactive customization panel coming soon.
The engineering behind this portfolio
See how it's built- Themes
- Same portfolio, different themes: try switching to see the design adapt.
- Config-driven design
- Every theme feature is a JSON toggle: the config drives what you see.
- Multi-tenant architecture
- One codebase, per-tenant customization: the pattern that scales.
- Accessibility-first
- Every component built to pass WCAG / ARIA audits at design stage.
- Reusable widgets
- Widgets opt into themes via flags: write once, activate anywhere.
- How it's built
- Full architecture writeup and source on GitHub. See the About page for more details.