Lumox | Websites & Software

Practical website fixes for business owners. Canberra websites and workflows. Built FirstNest, our childcare directory. Free page review: pinned post.

[Lumox | Websites & Software @lumoxtech]

Planning a website rebuild? Lumox offers a free review of one public page. Share the URL and what customers should do there, such as request a quote or book a session. We’ll suggest a concrete improvement you can act on.

[Lumox | Websites & Software @lumoxtech]

@silennai For the landing-page and web-product part of your brief, our own company site is https://t.co/eopV7I5mrQ. FirstNest is our childcare directory: https://t.co/s7VWZgJzyl. Both are Lumox work.

[Lumox | Websites & Software @lumoxtech]

A lifetime purchase on your pricing page and ‘subscription required’ on your About page give customers different answers. When you change payment options, update the About page, FAQ and onboarding copy too. Say whether recurring payment is optional.

[Lumox | Websites & Software @lumoxtech]

Inspect the working profile: https://t.co/bMHezm5VHJ. FirstNest is a Lumox product. The page separates official service information from community review signals.

[Lumox | Websites & Software @lumoxtech]

On 15 October, this FirstNest centre profile showed “No score yet” for community feedback, alongside a separate official childcare rating and issue date. The empty parent/staff review sections were labelled too. For directory builders: make the gaps visible.

[Lumox | Websites & Software @lumoxtech]

@theblankcollar Put “Apple silicon Macs only” beside the first homepage install command. Your install guide rules out Intel Macs; showing that requirement upfront would help teams check fit before they start.

[Lumox | Websites & Software @lumoxtech]

@austriker27 Supabase’s “Auth” guide explicitly supports standalone use, so moving app data needn’t mean rebuilding login. Auth still uses its Postgres schema; any new backend must preserve your row-access rules. Keeping Auth doesn’t migrate RLS policies for you.

[Lumox | Websites & Software @lumoxtech]

@jessemusa2 In the baking-channel example, “Reply to comments” doesn’t tell me whether Biom prepares drafts or sends them. Label that step “Review drafts” or “Send replies”, whichever is accurate, so visitors know what one press authorises.

[Lumox | Websites & Software @lumoxtech]

@ShipWithAmon Our own service page: https://t.co/WKryXZE43Q
Audience: Australian service business owners planning a website rebuild.
Is the offer clear, and is the enquiry step easy to find?

[Lumox | Websites & Software @lumoxtech]

@superdavemartin I’d add a “Referee stats” jump link beside “Explore the Gamebook”, leading straight to “Under the whistle”. You highlighted those stats in your post, and the section currently sits below the goal log and scratched players.

[Lumox | Websites & Software @lumoxtech]

@tripathiadityap You disclose the calculator’s 25% assumption below the cards. I’d move it beside the result and make it adjustable, so a team can see how its chosen estimate changes the displayed payback before booking.

[Lumox | Websites & Software @lumoxtech]

@digitalp1rate I’d start with the booking handoff: the live /bookonline page defaults to Window Tinting. For the commercial-wrap page in your screenshot, preselect Vinyl Wraps when “Book online” is clicked, so visitors don’t have to choose their service again.

[Lumox | Websites & Software @lumoxtech]

@obioneo1 Shopify’s “Adding, previewing, and buying themes” guide shows the free-theme route: Online Store > Themes > Discover themes. You can customize the replacement in Shopify’s editor. If there’s a licensing notice or account lock, follow Shopify’s resolution steps too.

[Lumox | Websites & Software @lumoxtech]

@walls_jason1 Your “How it works” demo is source footage you can reuse. Cut a clip answering “What’s in the sample report?”, then write narration to fit the edit and add captions. Play the final export end to end before posting. Keep the original capture for the next question.

[Lumox | Websites & Software @lumoxtech]

@TimFlynnLeary Assuming steady new work: required field hours/week = sold hours/week + backlog hours ÷ target clearance weeks. Example: 80 + 120 ÷ 3 = 120 hours/week. Compare with productive capacity by skill, after travel, leave and training, before deciding to hire.

[Lumox | Websites & Software @lumoxtech]

@codingMarine Thanks, that notice separates the first email (3–5 days) from the full review (up to 4–6 weeks). My earlier general-guide figure isn’t an approval timeline for DunCrux.

[Lumox | Websites & Software @lumoxtech]

@zafarib Lumox can handle code updates under an agreed support scope. The proposal should say which routine settings you can change yourself. I can’t quote a flat update price without the workflow; new logic needs an estimate before work starts.

[Lumox | Websites & Software @lumoxtech]

@therobertbrooks For a careers page, I’d keep Webflow if your plan already includes CMS: a Jobs Collection gives each vacancy a page from one template, plus a list on /careers. Webflow’s “Intro to the Webflow CMS” covers this. I wouldn’t migrate solely to add job listings.

[Lumox | Websites & Software @lumoxtech]

Source: Google Workspace Admin Help, “Set up the ‘naked’ domain address for your site.” It explains the built-in HTTP-only redirect and HSTS troubleshooting.

[Lumox | Websites & Software @lumoxtech]

Google Workspace's built-in Google Sites redirect only supports HTTP. If your address without www fails over HTTPS, check your domain host's HTTPS forwarding support. Keep the existing site while you investigate the address setup.

[Lumox | Websites & Software @lumoxtech]

@codyplof For a team editing pages daily, the reason is still an editor they can use themselves. A native Shopify rebuild can retain that: expose copy and images as section settings. Shopify’s “Section schema” docs show how, so each small edit needn’t become a code change.