Academia
Produced At: FAAS Architecture
Timeline: June 2025 - September 2025
As part of FAAS Architecture's 2025 rebrand, I was tasked with building a custom GIS web application that could spatialize the firm's projects across Canada, demonstrating the breadth of their work. Rather than adopting an off-the-shelf map plugin, I chose to build the application from scratch, ensuring it matched the rebrand's identity while giving FAAS a tool that could grow with the firm.
As the sole GIS Systems Designer & Analyst, I took ownership of this project end-to-end; proposing available viable technologies, managing and communicating scope and timelines, gathering and migrating content, design, prototyping, application development, and deployment.
See it Live
GIS Product Designer
ScopeProduct Strategy & Management;
UI/UX Design & Prototyping;
GIS Web Application Development
Technologies
Front-End Webflow (with Finsweet)(HTML, CSS);
Mapbox (basemap);
Mapbox GLJS (rendering engine)
Backend
Webflow CMS (database, content hosting);
Webflow API (CMS read access for Mapbox GLJS);
Cloudflare (security)
Production
QGIS (initial geocoding);
Figma (design, prototyping);
Github Desktop;
VSCode
With nearly 300 projects across Canada, the map needs to illustrate both the gravitas and extent of FAAS’ influence in an effective and engaging way.
Panels behave like native apps, with draggable “pull handles” and snapping min-mid-max states for the projects list. A geolocation feature is available for users to easily find FAAS projects in the wild.
The interactive map features a synchronized filtering system driven by each project’s typology-code and status-code. Users can apply single or combined filters to isolate specific work.
Every project’s name, number, location, typology, and status lives in Webflow CMS that can be easily updated anyone on the team without having to touch the code. Documentation has been provided for the team
Error handling has been put in place to defend against user-error when entering records on Webflow.
- Entries with invalid required fields such as latitude, longitude, project name, typology, and status are skipped
- Slugs are unique and required by webflow
- Missing images are allowed