Skip to content
All work

Group build · 2021

(dot)Logix

A group build for a fictional web-development studio: a scroll-driven Bootstrap front end with a full-screen sidebar menu, a preloader and SASS partials compiled into one stylesheet.

Role
Front-end and motion
Stack
HTMLSASSBootstrap 5jQuerySwiper
Live
dot-logix.vercel.app
Source
GitHub
The (dot)Logix studio home page

01What the build involved

01

A studio site with a big entrance

The page opens on a loader, then hands over to a layout that animates in as you scroll: services, demos, articles, blogs, careers and contact, with a Swiper slider and a full-screen sidebar menu instead of a conventional navbar. Open and close are two small functions that set the sidebar width, which is either exactly right or a mess — there was no in-between, and that made it a good place to learn where CSS transitions earn their keep.

02

Twelve partials, one file to link

The styles are SASS partials — navbar, sidebar, services, demos, blogs, articles, careers, contact, footer, loader, about and a video slider — compiled down to compiled-style.css, the only stylesheet the page loads. Splitting source by section and shipping one file is the habit I still use: the browser never waits on twelve requests, and the file you edit is still small.

03

The portfolio beside the studio

A separate portfolio folder went in alongside the agency site — profile, about and contact pages with their own stylesheet and photography — because a design studio that cannot show work is not convincing. There is also a folder of abandoned pages, kept rather than deleted. The site itself is fictional; the practice of building the thing the page claims to be was not.

02What it left behind

Outcome

A fictional studio site at dot-logix.vercel.app with a scroll-driven entrance, a proposal panel that slides over the page and twelve SASS partials compiled into one stylesheet — the build where CSS transitions and a single linked file stopped being abstract advice.

Another pass

Both the loader and the full-screen menu stand between a visitor and the content, and I would not make that trade twice: the loader goes, and the menu keeps a visible close control instead of relying on the same corner button that opened it. I would also compile the SASS in a real pipeline, with source maps, rather than through an editor plugin.

03Inside the product

The entrance is a full-bleed video slide behind the wordmark, with the “Request a Proposal” control pinned to the bottom-left corner instead of a conventional navbar.
That corner control slides a panel over the page — the enquiry form lives inside the navigation rather than on a separate contact page.

Click any screenshot to view it full size

Next case study

Chainlink

A blockchain forum and social app — my first Laravel and Vue build: questions, replies, categories, likes and notifications in MySQL, with replies updating live over Pusher.