Sunday, September 27, 2026
HomeJavaScriptHow Reviewey Constructed Its Admin and Member Screens With Aurelia 2

How Reviewey Constructed Its Admin and Member Screens With Aurelia 2


Reviewey
, an Australian overview platform, runs on a mixture of WordPress and a
customized software stack constructed round a set of providers, after which reaches for Aurelia 2 the second a
person logs in. Each administrative and member-facing display behind the login is constructed with
Aurelia 2.

It’s a good instance of how Aurelia 2 matches an issue that numerous groups even have: a working
website that you do not need to rebuild, and a set of screens that want actual software behaviour.

What Reviewey does

Reviewey.com.au
is a two-way overview platform. Companies can overview
prospects, and prospects can overview companies, and each overview is tied to an actual job, an actual quote
or an actual bill. There are not any nameless drive-by scores. If there was no job, there isn’t a overview.

Companies get rated on high quality of labor, punctuality, communication, professionalism and value.
Clients get a Reviewey Passport rating throughout timeliness of cost, communication, respect, website
readiness and follow-through, so a enterprise can measurement up a job earlier than quoting on it.

That issues right here, as a result of it describes the a part of the product that wanted an actual front-end
framework. Dashboards, passport scores, overview request flows and analytics are software screens,
not advertising and marketing pages.

The constraint: the prevailing stack stays

Reviewey’s public pages, the advertising and marketing website, the how-it-works content material, the weblog, run on WordPress.
Behind that sits a customized software layer made up of a number of impartial providers that deal with the
product itself. That entire stack works, it ranks, and the crew had little interest in throwing it away
to chase a full rewrite right into a single web page app.

The requirement was narrower and extra sincere than most framework choices: the logged-in
expertise wanted wealthy, interactive performance, however the remainder of the platform wanted to maintain
working precisely because it does at present. No matter framework went in needed to sit on prime of the prevailing stack
with out forcing a change to how every thing behind it’s constructed or deployed.

That is the state of affairs Aurelia has all the time dealt with nicely. You possibly can mount it on a single ingredient inside an
current web page, let it personal the interactive a part of the display, and depart every thing round it alone.
The backend retains doing its job the best way it already does. The admin and member screens develop into
Aurelia 2 apps that hydrate into the pages the platform serves.

Why Aurelia 2

The crew has been clear about what drew them to Aurelia 2. A couple of issues stood out.

It’s developer pleasant. Aurelia 2’s templates are shut to straightforward HTML, its conventions are
predictable, and its dependency injection and binding system keep out of your approach. For a crew
delivery a gentle stream of admin screens, that consistency is price quite a bit. There may be much less framework
ceremony per characteristic, which suggests extra time spent on the precise overview and passport logic.

It really works with the prevailing stack as a substitute of in opposition to it. Aurelia 2 didn’t ask Reviewey to undertake
a brand new server mannequin or a bespoke construct pipeline for the entire platform. It slotted into what was
already operating. The interactive screens are Aurelia, the remainder of the stack is unchanged, and so they
coexist cleanly. For a small crew, not having to re-platform was a characteristic in itself.

It provides wealthy performance with out altering how every thing works. This was the deciding level.
Reviewey wanted dashboards, stay passport scoring and interactive overview flows, the sort of
behaviour that genuinely wants a element framework, nevertheless it wanted all of that with out rewriting
the elements of the app that have been already wonderful. Aurelia 2 allow them to add functionality surgically. The
login screens acquired an improve. The remainder of the platform didn’t have to maneuver.

React was on the desk

React was evaluated. It’s the apparent default, and it will have carried out the job. The rationale Reviewey
didn’t decide it got here down to suit, not functionality.

For a product the place the framework solely owns the logged-in screens and sits on prime of an current
stack, React introduced extra bloat and extra tooling than the issue known as for. The construct setup, the
bigger dependency floor and the encircling ecosystem choices you are likely to inherit with React
have been overhead Reviewey didn’t wish to carry for what’s, structurally, a set of admin panels on prime
of an current platform.

The deeper difficulty is that React by itself is a view library, and something past gentle sprinkles
turns into assembling your individual fake framework. You decide a state administration library, then a router,
then one thing for kinds and validation, then a method to speak to your providers, then a styling
methodology, and on it goes. Each a kind of is a choice, a dependency and a factor to maintain
present. That’s determination fatigue earlier than a single characteristic ships. Reviewey doesn’t have a big
crew, so the applied sciences throughout the stack have been chosen for his or her leanness, and a framework that
fingers you a router, dependency injection, binding and conventions within the field matches that much better
than a pile of decisions you need to make and preserve your self.

Aurelia 2 gave them the wealthy interactivity with a lighter footprint and a smaller tooling burden.
The crew might embed it the place it was wanted, preserve the prevailing stack intact, and never tackle a
bigger frontend equipment than the screens justified. Identical consequence on the screens that mattered,
much less weight all over the place else.

What this appears to be like like in observe

The break up is clear:

  • Public and content material pages: served by the prevailing stack, unchanged. Advertising, the
    how-it-works pages, the weblog, enterprise profiles and search engine optimisation content material keep the place they’re and preserve
    rating.
  • Logged-in admin and member screens: Aurelia 2. Dashboards, profile and enquiry analytics,
    overview request flows and passport scoring.

The boundary between the prevailing platform and Aurelia 2 maps nearly precisely to the boundary between
content material and software. That isn’t an accident. It’s the structure you get if you let every
instrument do the half it’s good at, fairly than forcing one to do every thing.

Why it’s a good match for this sort of product

Loads of groups are in Reviewey’s place. They’ve an actual platform that’s doing its job, and a
rising set of screens which have outgrown jQuery and web page reloads. The intuition to rewrite the entire
factor right into a single web page app is dear and dangerous, and it often isn’t needed.

Aurelia 2 is a powerful reply to that actual scenario. It’s progressive, you may undertake it display by
display. It’s standard, so a small crew can keep productive with out a big frontend
specialisation. And it’s snug residing alongside an current backend fairly than demanding to
personal your complete stack.

Reviewey wanted wealthy performance on its logged-in screens with out disturbing the remainder of a working
product, and that’s exactly the form of downside Aurelia 2 was constructed to resolve.

You possibly can see the platform at
reviewey.com.au
.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments