Choose a website starting point or describe the pages, audience and brand you have in mind. Forge builds a public site from that brief, rather than assuming every project is a scanned-product app.
A site can bring together product pages, a contact form, FAQs and other useful content. The agent should fit the design and story to the business instead of repeating one visual formula.
Open a website and it gets its own workspace: the conversation on the left, the real running site on the right. Nothing to install or set up locally.
You can switch the right-hand side from the live app to the code at any time, edit a file directly, and watch the preview update.
There is no separate database to provision, sign-in system to assemble or deployment pipeline to wire together. The site can use the identity, data and services already provided by SmartLinks.
Forge can still build server-side workflows and connect to outside systems. Their credentials stay sealed away from the app, and SmartLinks runs the resulting work for you.
The agent starts with the SmartLinks platform already understood: products and their details, contacts, forms, sign-in, messaging, records and the built-in AI tools.
That means it leads with a solution rather than reading its way around. It won't rebuild something the platform already provides, and it won't invent a capability that doesn't exist.
Need another system in the loop? It can write server-side code that talks to your ERP, CRM or anything else with an API, with the credentials held in a sealed store rather than in the app.
A product page can show details held in SmartLinks, while the team manages those details in Studio. Enquiry forms can connect visitors to contacts and follow-up on the same platform. The agent does not need to build a second product editor just to add a field such as colour.
Your existing commerce, finance or specialist CRM can still do its own job. SmartLinks is the connected layer behind the website, not a demand to replace everything else.
Choose one of your own collections and item types, and the preview runs against the real thing. What you see is what a customer or an operator will see.
An app doesn't live in one place. Forge lets you load each view the way it actually runs — including the operator admin dashboard inside the genuine signed-in SmartLinks console, so sign-in, navigation and theming behave exactly as they will in production.
Every change is saved automatically as you go, so you can look back through what happened and restore any earlier point — no version-control knowledge required.
When you're happy, send a test version to a real SmartLinks account, check it in context, and publish the finished app without assembling your own release process.
The app's main panel inside a SmartLinks page.
A compact tile that summarises the app with a way in.
The app's own full screen, not embedded in anything.
The operator's screen for running the app — settings first, administration after.
A handheld operator screen inside SmartLinks Sidekick.
The app as a tab inside Microsoft Teams, signed in for you.
What search engines and AI assistants are told about the page.
