The idea in brief
- A Portable Website gives you a complete site to keep, move, and maintain. A Web Application lets people perform tasks through a browser. A site that presents your business may not need an application platform running behind it.
- You can use a Web Application to create a Portable Website. Its editor, AI tools, and content database can do their work during creation; visitors can then read the finished pages without those systems.
- Choose the services that help your visitors and team. Keep the website files, choose your hosting, and connect applications for accounts, transactions, collaboration, or other tasks your business needs.
1. Do you need a Portable Website or a Web Application?
A manufacturer shows what it can make, its certifications, and its catalog. A consultant explains services and shares case studies; a designer presents a portfolio. Visitors need to understand the offer, evaluate it, and make contact. A trading platform must execute orders, while a collaboration tool must store private work and coordinate live edits. All are used in a browser, but they have different jobs to do.
A Portable Website is a complete website you can retain, move to compatible hosting, and maintain independently of its creator. A Web Application is software used through a browser to carry out tasks, such as editing a document, managing orders, or managing an account. It may run in the browser, use server-side services, or combine both. For a company introduction or service description, the same approved content can usually be shown to every visitor. A change next month does not require that content to be assembled from a database on every visit.
Consider an export company that needs a credible multilingual catalog, with inquiries handled by email. Its website may be essential, while customer accounts, live inventory, and a continuously running content management system (CMS) are unnecessary for its visitors. If the site still depends on an application stack, someone has to operate and maintain that stack. The customer needs the presentation website but also takes on software that its visitors do not use.
| Question | Portable Website | Web Application |
|---|---|---|
| What do you receive? | A complete presentation site that the owner can keep and move | Software that performs tasks or manages workflows through a browser |
| What must keep running? | Compatible hosting for the website files, plus any services you choose to connect | The application’s required code and services; a server-backed application may also need databases, authentication, or APIs |
| What needs ongoing attention? | Content, domain and hosting accounts, assets, and connected services | Those responsibilities plus the application runtime, data, permissions, and integrations it actually uses |
| What makes a handoff possible? | Usable files, documented dependencies, and a deployment procedure | Application code, required data, configuration, services, and operating knowledge |
2. Buying a website can also mean running a Web Application
Website creation and website operation are often sold together. Hosted builders combine an editor, media storage, hosting, and integrations in one service. A conventional CMS can combine an administrative interface, a database, themes, plugins, and server-side rendering. A custom Web Application adds its own code and deployment process. These models are convenient, but the customer may be choosing a way to build a site without realizing that the same choice also determines what must keep running after delivery.
For a team that needs daily editorial approvals or a shop processing orders, those Web Application capabilities can justify their cost. For a presentation site updated a few times a year, the same stack may create work without improving the visit: runtime upgrades, database backups, plugin compatibility checks, security patches, and plans for recovering from an outage. A managed provider can do much of that work, but you still depend on its service and pay for its ongoing operation. Before choosing, establish which functions your team needs, who will operate them, and whether the finished pages need them at all.
Before buying, ask what you will be able to take with you. A login and a paid invoice do not answer that. Does the export contain working pages and media, or just text records? What must still run at the original provider? Can another developer maintain the site without recreating it from screenshots? Check these details before choosing the tool, while you can still compare alternatives.
Self-hosting and open source can provide substantial control. An open-source application may still require a database, a particular runtime, backups, and upgrades. A proprietary authoring tool can produce website files in ordinary formats that other tools can read and edit. Evaluate the delivered website and its dependencies alongside the tool’s license.
3. Use a Web Application to create a Portable Website
A Web Application can be the right creation tool even when the customer’s finished site should be a Portable Website. Extracting information from documents, organizing a catalog, translating copy, choosing a layout, and rendering responsive pages may involve AI models, databases, queues, and build tools. Those systems produce the result. Keeping them available to the author is a separate decision from requiring them every time a visitor reads an About page.
CREATION: WEB APPLICATION
Materials + reviewed content + design + translations
|
v
DELIVERY: PORTABLE WEBSITE
Complete HTML, CSS, JavaScript, and assets
|
v
VISITOR EXPERIENCE
Compatible static hosting -> browser
Optional application services remain separate dependencies.In a prebuilt site, a host serves HTML, CSS, JavaScript, and media that already exist. A dynamic application may instead assemble a response using application code and current data. Both approaches can be useful and can coexist. Choose based on which work must happen for each visitor and which can be done once when the site’s content changes.
A static site can have responsive layouts, navigation, galleries, animation, and language switching, all running in the browser. Its core content is prepared in advance, ready to display when a visitor arrives. You can connect services for live data, user accounts, and messaging. For example, a payment link opens a checkout service that handles the transaction.
4. What a Portable Website must deliver
At LiteSite, a portable website means a complete website you can retain, move to compatible hosting, and maintain independently of LiteSite. Its delivered core pages do not require a LiteSite account, an active LiteSite subscription, or LiteSite's application servers to keep serving their content.
Portable Website describes whether you can keep and move the delivered site. Web Application describes what software does. An application that runs entirely in the browser can also be portable. For a presentation-site owner, the practical choice is often between receiving independent website files and keeping the pages tied to an application platform. The underlying web technologies are established. You can check the delivery against the following requirements:
- Complete: the package includes the generated pages and the files needed to display them.
- Independent: the core pages run on compatible hosting, independently of the original builder.
- Movable: another compatible host can serve the files once its URLs, routing, and required services are configured.
- Maintainable: a developer can inspect and edit the delivered HTML, CSS, JavaScript, and assets using ordinary tools.
- Documented dependencies: for forms, analytics, maps, commerce, and other integrations, you know which provider supplies the service and who is responsible for it.
5. Maintain your Portable Website without an unnecessary application stack
Your finished website stays in your hands. Save a copy of the files and use a hosting account you manage independently. You can archive the site, restore a previous copy, inspect its contents, or hand it to a developer. The same files remain available when you change the tools you use to create your next website.
You can choose a host for your business, change providers, or ask a different developer to update the site. Each new provider starts with the complete website you already own. Your pages, design, and content carry forward when you decide who should host or maintain them.
A Portable Website for presentation can run without an application database or administrative system in production. That means fewer components to patch, back up, and monitor. Your team can focus its maintenance on the content and features customers use, with a developer handling the site’s files and connected services.
Buying the LiteSite website and choosing its hosting are separate decisions. Static hosting can be inexpensive, even free with a suitable plan. You can choose domain, hosting, and maintenance arrangements that fit your business and change them as your needs evolve. A developer can also work directly on the delivered images, fonts, and scripts, and adjust caching with your host to improve page loading.
6. The files LiteSite delivers
LiteSite uses your existing website and supplied materials to prepare content for you to review and create a multilingual website. Inspect the private preview before buying. After purchase, you receive the production package for publication, without the preview watermark or access requirements. Download the complete package to keep, deploy, and share with the developer you choose.
index.html
about.html
content.json
…other included pages
zh-Hans/
index.html
about.html
content.json
…other included pages
assets/
…styles, scripts, images, fonts
robots.txt
sitemap.xml
seo-manifest.json
manifest.json
package-info.json
healthcheck.json
README.md
AGENTS.md
DEVELOPMENT.md
litesite-dev.mjs
litesite-bind-origin.mjsThe HTML documents and assets form the website visitors see. Content JSON snapshots keep a copy of the purchased content for reference, while the generated HTML contains the page content ready for display. The package manifests list the files and record information used to check their integrity. README.md explains the files and the deployment procedure. AGENTS.md gives AI coding agents a short starting point. DEVELOPMENT.md explains the site’s files, design conventions, and interaction patterns, while litesite-dev.mjs provides local preview and checks. The included litesite-bind-origin.mjs tool sets the site’s destination address and prepares a separate directory to upload.
After preparing the destination, a developer can edit the HTML, styles, scripts, and assets directly in the deployment copy, then publish the updated site. Use content.json as a reference for the purchased content and make page changes in the generated website files. Keep the original package unchanged so the tool can verify its integrity and prepare another deployment whenever you choose a new destination.
7. How moving a Portable Website works
Start with the production ZIP and keep an untouched archive. Choose the final HTTPS address and a host that supports the package’s static files and page paths. When deploying through LiteSite to your own Cloudflare account, LiteSite prepares the files for that destination. For a manual move, follow the package’s README.md and use the included litesite-bind-origin.mjs tool.
node litesite-bind-origin.mjs https://example.com/
# Upload the resulting litesite-deployment/ directory.The tool sets public canonical URLs, links to other language versions, Open Graph URLs, and sitemap locations for the chosen destination. It creates a deployment directory and leaves the original files unchanged. Node.js is used for this preparation step; the generated pages do not need a Node.js application server once published. The deployment copy excludes the original package’s README.md and the preparation script.
node litesite-bind-origin.mjs https://USER.github.io/ /REPO/Upload the prepared files and test the website at its actual destination. Check the homepage, a page opened directly by its URL, each language, images, downloads, and external integrations. Check that HTTPS works and that the site uses the preferred domain. Update DNS for the chosen host where needed. When replacing an existing site, set up redirects from changed URLs at the old host so existing links lead visitors to the right pages.
For a project hosted under a path such as /REPO/, use that base path when preparing the files. Place robots.txt at the host root when you control it, since that is where search crawlers look for the host’s crawling instructions. On a shared host, use the provider’s available settings for those instructions. Verify the resulting URLs and page paths on the published site.
8. Connect the services your business needs
A Portable Website can connect visitors to the services your business already uses. Add a contact form for inquiries, a map for directions, a booking service for appointments, or a payment link for purchases. Choose the provider that suits each task and connect it through a link or integration. Your presentation pages stay portable as you add the functions that help customers take the next step.
| Part of the site | How you use it |
|---|---|
| Generated HTML, CSS, JavaScript, and bundled media | Keep the complete files and publish them on compatible hosting |
| Domain, DNS, and HTTPS | Use your chosen address and configure it through your domain and hosting accounts |
| Forms, maps, analytics, booking, and payments | Connect the providers that support your business through their links, accounts, and integrations |
| Ongoing updates | Choose who maintains the content, integrations, accessibility, and published files |
A Portable Website and a Web Application can serve the same business side by side. Keep the company presentation and service pages portable while an application handles accounts, bookings, or orders. Clear links let visitors move from learning about your business to using those services. Your team can choose who manages each part and update the presentation or business application as needed.
9. Put Web Application capabilities to work
A Portable Website suits a company profile, service website, export catalog without online purchasing, campaign microsite, or professional portfolio. These sites primarily present approved information. It is especially useful when content changes periodically, several languages matter, and you want to keep the result or hand it to another developer.
Web Application capabilities are useful for per-user dashboards, live stock availability, order processing, complex subscriptions, or collaborative editing. A large editorial team may also need a CMS for writing and approvals while still generating its public pages ahead of time. Consider separately how your team creates content, what visitors need to do, and which systems must keep running. You can combine a portable presentation site with an application that handles transactions.
Even when you need a Web Application, your developer can build on the website LiteSite generates. They can use its existing pages, design, and content as a starting point, then add user accounts, order workflows, and the backend services your business needs.
- What must change for each visitor, and what is the same approved content for everyone?
- How often does content change, and who is responsible for updating it?
- What exact files and rights are included in delivery?
- Which services would help visitors contact you, book, buy, or use their accounts?
- What files and instructions will let your chosen developer take over the site?
- Who will manage content updates, hosting, and the services you connect?
10. LiteSite is the Web Application. You receive a Portable Website.
LiteSite itself is a Web Application. It provides accounts, AI tools, content editing, translation, and website generation. You can inspect a real preview before buying. What you purchase is a Portable Website: complete files whose core pages can run on compatible hosting without LiteSite’s application servers.
We built LiteSite for customers who need a website to present their business and would otherwise take on an application stack to keep it online. The creation tools can do complex work. Once the site is finished, it should need only the services required by its pages and the functions you choose to include.
Download and keep the files, choose compatible hosting, and decide who will maintain the site. The package includes dependency information and a deployment procedure that another developer can follow.
References and further reading
The documentation below explains the web technologies discussed here. Details about LiteSite describe the website packages it currently delivers, with a representative file list to show their structure.