Not one CMS
WordPress, Shopify, WooCommerce, Webflow, Wix, Tilda, headless CMS or own logic - the tool is chosen after the task.
Scale under the budget
For a small budget, we reduce the volume and complexity, not the quality of the basic adaptive, forms and technical launch.
Transfer to owner
In advance we determine that the client will edit himself: pages, products, prices, blog, menu or only contact data.
On which platforms can you make a site?
WordPress and WooCommerce
For business sites, blogs, catalogs and stores where the owner familiar admin, edited pages, menus and products are required. Possible custom WordPress theme without binding to a ready-made template.
Shopify
For e-commerce, when the priority is to quickly launch a store, manage products, payments, orders and a ready ecosystem of integrations.
Webflow, Wix or Tilda
For a presentation site or landing page that the team plans to rebuild frequently in the visual editor. I take into account the limitations of tariffs and paid functions before starting work.
Headless or custom CMS
For an atypical content structure, several publication channels or a separate frontend. Admin and public site can work as independent parts.
HTML, CSS and JavaScript
For fast static sites without unnecessary administration. This format works well when content changes infrequently and code control and minimal dependencies are important.
React, Vue and API
For web applications, personal accounts, calculators, catalogs with logic, user roles and integrations with external services.
Which platform is suitable for a specific task?
Choose a platform based on features, editing frequency, support budget, and development plan, not name popularity.
| Task | Possible format | When appropriate |
|---|---|---|
| Landing or business card site | Static Build, Webflow, Wix, Tilda | Small structure, quick launch, simple changes |
| Corporate website | WordPress, headless CMS, custom CMS | Many pages, services, news or editors |
| Online store | Shopify, WooCommerce, custom | Goods, payments, orders, warehouse integration |
| Web application | React/Vue and backend/API | Authorization, roles, calculations, cabinets, automation |
Can I choose a solution for different budgets?
Yes. The volume of pages, the level of customization and the number of integrations change under the budget, but not the basic functionality of the site.
- Compact launch. One or several key pages, ready-made content, simple form and minimal number of external services.
- Full business website. Custom structure, separate services, CMS, forms, basic SEO, responsive and transfer to owner.
- Complex product. Personal accounts, API, roles, payments, automation, exchange with CRM/ERP or atypical administrative part.
I will determine the exact format later brief. If the function is not needed for launch, it can be moved to the next stage, rather than overloading the first version.
Does promotion depend on the name of the CMS?
The CMS name itself does not guarantee positions. Crawlability, speed, mobile version, metadata, structure and useful content are important.
On WordPress, Shopify, Webflow or a custom site, you can make a high-quality technical base. The difference lies in the freedom of customization, the cost of support and the limitations of the platform. Before starting, I check the title, description, canonical, sitemap, robots.txt, Open Graph, favicon, internal links and the relevant schema. This is described in more detail on the page SEO optimization.
Will the client be able to manage it himself site?
Yes, if an admin is needed
Editable fields, pages, products and menus agree to the development so that the owner receives exactly the tools with which will be used.
Designer is not always easier
The visual editor gives you freedom, but a complex page still requires an understanding of grid, responsive, typography and component states.
Possible migration
Before migration, I check URL, content, forms, integrations and SEO data to avoid missing important pages and set up redirects.
Access belongs to the owner
After launch, the client receives a domain, hosting, CMS, files and agreed instructions. Paid tariffs and licenses are issued to his account.