Estate Agent Listings By Status Profile Block for Solid

Edit LISTINGS at the top: each has a title, a neighbourhood, a status, a price, beds, baths, area, a listed day and the kind of drawing. HOODS names the chips and STATUSES the tabs. Counts, the value of the shown listings and the Showing line are worked out from the list, so nothing is typed twice. In your app swap the drawing for the listing's photograph.

As soon as you choose, because it is a menu you operate and the status line says what happened: Sorted, price low to high. The list never re-orders on its own. Newest first uses the listed day, and equal prices keep their order.

The visible cards sit in the same grid cell as an unseen copy of the longest list, five active listings, so every tab and filter fits in it. The empty state is a fixed height. On a phone the cards are rows with the picture beside the words.

It builds a text file in the browser with one line per shown listing: title, neighbourhood, price, rooms, area and status. Nothing is sent. The status line says how many were saved. To export for real, replace the helper with a call to your own endpoint.

The tabs, the chips and the menu are named, each tab's count is part of its name, and each list is labelled by its status. The cards' drawings are hidden from assistive technology because the facts are in the text. The status line is a polite live region present from the start.

The tabs share the width, the chips scroll sideways, the cards are single rows and the foot stays pinned to the bottom of the screen. From the small breakpoint the cards are two across with the picture on top, and three across from the medium one. Prices keep their order in a right-to-left layout.