India
ProjectsNovember 3, 2023

Indus premium properties, a private listings portal

image
A second, separate site for Indus Real Estate's premium listings. Access is restricted to registered users. The main Indus site is built to be found. Search rankings, indexable listing pages, fast first paint for people arriving from Google. This one is built not to be. Owners of high-value properties often do not want their address, interior photographs and asking price publicly indexed, and buyers at that level are introduced by an agent rather than arriving from a search result. So the requirements invert: registration ahead of any listing detail, nothing indexable, and no public entry point into the inventory. Building the two as one site with a permission flag would have been a mistake. The caching, the rendering strategy and the metadata all want to be different, and a single codebase serving both intentions tends to leak the private half into the public one eventually. Because there is no search traffic to optimise for, the interface could be slower and heavier in the places where that buys something: larger photography, more space, fewer listings on screen at once. The result is closer to a brochure than to a search tool, which suits both the inventory and the audience. Next.js on the front with PHP and Node.js behind it over SQL, sharing the property data model with the main site.

Screens

Indus premium properties, a private listings portal screen 2
Indus premium properties, a private listings portal screen 3
Indus premium properties, a private listings portal screen 4
Indus premium properties, a private listings portal screen 5
Indus premium properties, a private listings portal screen 6
Indus premium properties, a private listings portal screen 7
Indus premium properties, a private listings portal screen 8
Indus premium properties, a private listings portal screen 9
Indus premium properties, a private listings portal screen 10
Indus premium properties, a private listings portal screen 11

Related projects

bouncer, CI gates that let anyone contribute

bouncer, CI gates that let anyone contribute

Five checks that sit at the door of your main branch, written as pure functions so the same modules run in CI, in a Cloudflare Worker, on Railway and in the browser. Pointed at a real 1,209 file repository it went from 45 blocking findings to 13, all 13 genuine.
estate, a linter for your repositories

estate, a linter for your repositories

Checks every repository you own against declarative rules and exits non-zero, so the problems nobody notices for months fail a build instead. One Go binary, no dependencies, no dashboard.