Everything you need to know about templates, customization plans, implementation scope, operational limitations, support policies, and project workflows within the W-Forge system.
W-Forge Studio is a digital studio focused on professional website templates and customization services.
The studio helps clients adapt templates for real business projects through structured customization plans and additional implementation services when needed.
W-Forge focuses on template-based website development instead of fully custom projects from scratch.
This helps keep projects more organized, faster to launch, and more affordable compared to many traditional custom website workflows.
No.
W-Forge mainly works with existing templates and template-based customization.
Fully custom websites, applications, and large custom systems are handled separately as custom development requests.
The studio does not provide:
These types of projects are discussed separately when needed.
Each customization plan includes a specific amount of work.
This helps keep projects clear, organized, and easier to manage for both sides during the implementation process.
It means customization services are organized through clear plans with defined types of work included in each option.
This makes the process easier to understand before the project begins.
Unlimited revisions often make projects difficult to manage and slow down the implementation process.
Instead, customization is organized through structured plans that can always be expanded later if additional work is needed.
An implementation cycle is the amount of work included within a selected customization plan.
Additional customization can always be added later if the project needs further improvements or expansion.
The goal is to keep the project process clear and organized from the beginning.
Instead of endless revision loops, the work is completed within the selected customization scope, with the option to continue expanding the project later if needed.
The system is designed to keep projects more organized by using clear customization plans, structured workflows, and defined implementation scope.
This helps make the process easier to manage throughout the project.
Yes.
The studio works with startups, agencies, solo professionals, service businesses, and other clients looking for professional template-based website solutions.
Yes.
Templates and customization services are available for international clients depending on the project requirements and communication workflow.
Each template includes the website files, layouts, styling, pages, and features shown in the template preview.
The exact contents may vary depending on the template.
Yes.
Templates are sold as standalone digital products and can be used independently without purchasing customization services.
Yes.
Templates are provided in the condition and structure shown in the preview at the time of purchase.
Yes.
Templates can be customized independently or through additional customization services if professional help is needed.
Most templates are designed to be easy to work with, including for users with limited technical experience.
However, some familiarity with website editing platforms may still be helpful.
The platform depends on the specific template and project requirements.
Platform details are provided individually where relevant.
HTML templates do not include built-in CMS functionality by default.
If your project requires dynamic content features such as blogs, collections, databases, or editable content systems, separate CMS integration services are available through optional CMS Extensions.
The studio can recommend suitable CMS platforms and integrate them into the project during the customization process. CMS subscriptions and third-party platform costs are managed separately by the client.
Yes.
Templates may include demo images, graphics, videos, and content used for preview and project presentation purposes.
Licensed assets included with the template can be used as part of your project together with the template itself.
One template purchase includes one license for one final website project.
The same template may be customized and used for one personal project or one client project under a single license.
If the template is used for:
additional licenses are required.
Templates may be freely customized for the licensed project, but they cannot be resold, redistributed, shared, or republished as standalone template products.
Yes.
Templates are designed and structured for responsive behavior across modern desktop, tablet, and mobile devices.
However, final responsiveness may also depend on:
Yes.
Basic multilingual translation can be generated during the multilingual setup process using AI-assisted translation tools as part of the implementation workflow.
If the client prefers custom-written translations, professional localization, or manually prepared language versions, the translated content can also be provided separately by the client.
Additional language editing, advanced localization, or custom translation work may require separate discussion depending on the project requirements.
Templates are built with basic SEO structure in mind, including semantic layout organization and editable metadata fields where supported.
Yes.
You can edit, customize, and adapt the template for your own project after purchase.
If the template is modified incorrectly, some functionality, layouts, responsiveness, animations, integrations, or visual structure may stop working properly.
Professional customization or technical assistance may then be required to restore, rebuild, or restructure the affected parts of the template.
In such cases, additional customization plans or extensions may need to be purchased depending on the amount of required work.
No.
Support does not include troubleshooting or fixing custom modifications made after purchase.
A template bug refers to a problem that exists in the original template before any client modifications are made.
This may include broken layouts, missing functionality, or technical issues present in the original delivered version.
Bug fixes are provided only for the original template structure and functionality in the condition it was delivered.
If the template has been modified, edited, restructured, or affected by third-party code, fixes and corrections are handled through paid customization services.
If third-party code, external scripts, plugins, integrations, or independently added functionality affect the template structure, responsiveness, animations, layouts, or functionality, the original template may stop working correctly.
Such issues are not considered template bugs or original template errors.
Restoring, rebuilding, correcting, or restructuring affected parts of the template may require paid Customization Pro services, additional customization plans, or extensions depending on the amount of required work.
Restoring, rebuilding, correcting, or restructuring affected parts of the template may require paid Customization Pro services, additional customization plans, or extensions depending on the amount of required work.
Free support is provided only for correcting verified bugs or technical errors that exist in the original template source version before any client modifications are made.
Support without paid customization is generally limited to verified template bugs or original technical issues.
No.
Additional implementation help, modifications, integrations, and project improvements are handled through paid customization services.
Once a template is heavily modified, original support eligibility may no longer apply because the project structure has changed from the original delivered version.
Free error correction applies only to the original template version.
Once the template structure has been modified or affected by third-party code, any further fixes or corrections are handled through paid customization services.
Updates may be provided when necessary depending on the template and future improvements.
HTML templates are not directly connected to Webflow updates and are not automatically compatible with Webflow projects by default.
If you need a Webflow version of a template, you can contact the studio with a separate request.
HTML templates are not directly compatible with Webflow projects by default.
If the client purchases an official Webflow version of a template, the project is prepared for normal transfer and usage within the Webflow platform according to the capabilities and transfer rules of Webflow at the time of delivery.
Professional customization and implementation services can be requested separately if needed.
After purchasing a template, describe your project and customization request in the chat on the website.
The studio reviews customization requests and plan selection questions only through the website chat.
Based on your request, the suitable customization plan and required amount of work will be determined for your project.
After that, you can go to the Customization Pro page, choose the recommended plan, and complete the payment.
Once the payment is completed, the customization process can begin.
If the purchase link for a plan is temporarily unavailable, you can join the waiting list. This usually means that all specialists are currently busy. In this case, the studio will contact you within one or two business days.
Before submitting your customization request, please carefully review the requirements for providing project materials for customization.
Professional Customization is a paid service for adapting a template to the needs of a real business project.
This may include layout changes, content integration, visual adjustments, additional sections, CMS integration, multilingual setup, and other implementation work depending on the selected plan.
Customization works with an existing template structure as the foundation of the project.
Full custom development means creating a completely new system, structure, or platform from scratch.
The studio supports many types of template customization, including:
Requests involving:
are discussed separately as custom development requests.
A section is an individual content block or visual block within a page layout.
Examples may include:
Section modification means changing the existing structure, layout, content arrangement, visual composition, functionality, or organization of a section beyond simply replacing the original content while keeping its original placement and structure unchanged.
Section-level customization means customization work applied to individual sections within a page instead of rebuilding the entire project structure from scratch.
Customization plans are organized around the number of sections that can be modified within the project scope.
Different plans allow different levels of section modification.
This approach helps keep projects organized, predictable, and easier to estimate before implementation begins.
It also allows clients to expand their projects progressively without rebuilding everything from scratch.
Yes.
Some section modifications may be simple, while others may involve larger visual or structural changes depending on the project requirements.
No.
Once a section is included in the purchased customization scope, the amount of work performed inside that section is not separately limited and may vary depending on the client’s requested implementation needs within that section.
Each customization plan and extension includes a fixed amount of work.
Once the purchased work volume has been completed, the customization scope is considered finished.
If the client wants to continue expanding, restructuring, improving, or modifying the project after that point, the client may:
The studio performs the requested implementation work for each approved modification point within the purchased customization scope.
If the client later requests repeated rework of the same sections by changing the originally approved conditions, experimenting with alternative versions, repeatedly changing direction, or demanding additional improvements without new implementation justification, such requests may increase the amount of work beyond the originally approved scope.
In such cases, the project may require:
The final decision regarding such additional work is determined individually by the studio team and the responsible implementation specialist.
If the project requires additional work beyond the included scope of the purchased plan, further implementation requires the purchase of additional customization plans or the required extensions.
Yes.
Projects can be expanded at any time through the purchase of additional customization plans and the required extensions depending on the amount and type of work needed.
Customization plans are organized around fixed amounts of work and clearly defined implementation scope.
This helps keep projects understandable, transparent, and easier to manage throughout the customization process for both the client and the studio.
Projects are organized through structured plans, clearly defined implementation scope, and staged customization workflows.
Basic Setup is designed for adapting the template to the client’s content and branding without changing the existing page structure
This may include:
Basic Setup does not include:
These types of work require higher plans or additional extensions.
No.
Basic Setup does not include section modification or restructuring.
The existing template structure remains unchanged.
Basic Setup allows content and visual adaptation within the original template structure.
This may include:
No.
Layout restructuring and section modification are not included in Basic Setup.
Yes.
Basic Setup includes adapting the template to the client’s content, branding, colors, typography, and visual identity within the original structure of the template.
Advanced Customization allows deeper customization of the template structure and visual layout.
This may include:
Advanced Customization allows modification of up to 50% of the sections within the project scope.
Once a section enters the customization process, the required work for that section is performed within the scope of the selected plan.
Each section that requires structural, visual, functional, or layout modification is counted as a modified section within the project scope.
When you contact the website chat to determine the most suitable customization plan for your project, the system analyzes the sections within the purchased template together with the requested project modifications and calculates the required implementation scope automatically.
Based on this analysis, the appropriate customization plan and required extensions are recommended for the project.
For this reason, the studio recommends using the website chat when selecting the required customization plan.
Yes.
Advanced Customization may include significant visual and structural changes within the included section modification scope.
Yes.
Advanced Customization allows partial layout restructuring and section reorganization within the included scope of the plan.
If the required work exceeds the included scope of the plan, further implementation requires the purchase of additional customization plans or the required extensions.
Premium Setup allows full customization of the template structure within the included project scope.
This may include:
No.
Premium Setup includes up to 100% section modification within the project scope, but it does not include unlimited revisions or unlimited ongoing work.
It means all sections within the project scope may be customized, modified, or restructured as part of the implementation process.
Yes.
Premium Setup allows complete transformation of pages within the included project scope.
Premium Setup still works within the limits of the purchased implementation scope.
Backend systems, applications, SaaS platforms, and large custom-coded infrastructures are not included.
Premium Setup does not include:
These requests are handled separately as custom development work.
A project becomes custom development when it requires building completely new systems, advanced backend functionality, standalone platforms, applications, or large custom infrastructures beyond template-based implementation.
Extensions are additional implementation services that expand the customization scope of a project beyond the standard customization plans.
They are used when a project requires additional functionality, infrastructure, languages, pages, integrations, or implementation work not included in the purchased plan.
Extensions help expand projects gradually without requiring a complete rebuild or unnecessary overpayment for work that is not needed.
They also make it easier to calculate and organize additional implementation scope during the customization process.
Yes.
Extensions can be purchased at any stage of the customization process if the client wants to continue expanding, restructuring, improving, or modifying the project beyond the amount of work included in the purchased customization plan or previously purchased extensions.
No.
Many projects can be completed within a standard customization plan without additional extensions.
Extensions are only used when the project requires additional implementation scope or functionality.
CMS Extensions are additional services used to integrate dynamic content systems into a website or template project.
This may include:
No.
HTML templates do not include built-in CMS functionality by default.
CMS functionality is added separately through CMS Extensions during the customization process.
Third-party CMS platforms, subscriptions, hosting services, and related infrastructure costs are paid directly by the client.
The studio can recommend suitable solutions and perform the integration during customization.
Simple CMS Integration includes:
Examples:
Advanced CMS Integration includes:
Premium CMS Integration is intended for large or complex CMS structures requiring advanced dynamic content organization, expanded content architecture, and multi-level CMS implementation within the project structure.
Multilingual Extensions are services used to create multilingual versions of a website or template project.
Yes.
Basic multilingual translation can be generated during the implementation process using AI-assisted translation tools.
Clients may also provide their own translated content if preferred.
However, multilingual implementation still requires additional setup and integration work, including:
For this reason, multilingual projects are handled through separate Multilingual Extensions regardless of whether the translated content is generated during implementation or provided by the client.
If the multilingual system requires CMS integration, the required CMS platform or subscription must be purchased and managed directly by the client before implementation begins.
Includes:
Includes:
Includes:
Page Customization Extensions are used when a client needs additional customization work beyond the limits of the purchased customization plan.
These extensions are intended for deeper customization of existing template pages and existing page structures.
They are typically used when:
Yes.
A project may use different customization levels for different existing pages depending on the required amount of work.
For example, a project may use:
No.
Page Customization Extensions apply only to existing template pages and existing page structures.
Creating completely new pages from scratch is considered separate development work and is discussed individually outside the standard customization system.
Advanced Page Customization is an extension designed for projects where a specific existing page requires deeper customization without upgrading the entire website to the Advanced Customization plan.
Advanced Page Customization includes:
Advanced Page Customization does not include:
Premium Page Customization is an extension designed for projects where a specific existing page requires Premium-level customization without upgrading the entire website to the Premium Brand & Website Setup plan.
Premium Page Customization includes:
Premium Page Customization does not include:
Yes.
Page Customization Extensions may be applied to approved connected page groups listed in the template structure when the same customization logic and implementation structure are used consistently across those related pages.
No.
These extensions apply only to existing template pages and existing template page structures.
Creating completely new pages from scratch is considered separate development work and is discussed individually outside the standard customization system.
Before customization begins, the client must provide all required project materials needed for implementation.
This may include:
No.
The client is responsible for providing the content required for the project unless separate content creation services are discussed individually.
Yes.
Templates may include purchased images, graphics, videos, and presentation materials used as part of the template package.
Clients may continue using these materials within their own projects if desired.
However, because templates may also be purchased by other clients, the uniqueness of included media content may be limited. In some cases, this can affect long-term visual uniqueness and future SEO or brand differentiation.
Clients who prefer stronger uniqueness may replace the included media with their own materials during the customization process.
Yes.
Clients may provide their own:
The client is responsible for the accuracy, legality, ownership, and quality of all provided project materials.
No.
The client is responsible for ensuring they have the legal right to use all provided content, media, branding assets, and materials.
Missing materials may delay the implementation process until the required project assets are provided.
Yes.
Temporary placeholder content may be used during implementation if the final project materials are not yet available.
Yes.
Each language version requires separate translated content unless AI-assisted translation is used during the multilingual implementation process.
Yes.
Basic AI-assisted translation may be used during multilingual implementation depending on the project requirements and selected extensions.
The client is responsible for reviewing and approving all translated content before final publication.
Major content changes after implementation has started may require additional customization plans or extensions depending on the amount of additional work created by those changes.
Yes.
Project materials should be provided in a clear, organized, and implementation-ready format whenever possible.
Basic content organization may be possible during implementation, but heavily unstructured, incomplete, or disorganized materials may require additional customization scope.
Yes.
The client is responsible for providing the final versions of:
Yes.
Downloadable files such as PDFs, brochures, guides, presentations, or documents can be integrated into the project when provided by the client.
The standard customization system does not include:
Such requests are discussed separately outside the standard customization workflow.
No.
Clients are expected to provide their own logo and branding materials unless separate design work is discussed individually.
No.
Customization plans focus on adapting templates for implementation purposes and do not include full branding development.
No.
Marketing strategy, advertising campaigns, SEO consulting, and business strategy services are not included in the standard customization system.
The standard customization system focuses on website implementation and template customization.
Basic website publishing and deployment to standard hosting environments may be possible depending on the project.
However, backend systems, server-side applications, databases, SaaS infrastructure, and complex server architecture are not included in the standard customization system and are discussed separately.
No.
Applications, SaaS platforms, and standalone software systems are outside the standard customization system.
No.
Large custom-coded systems and standalone technical infrastructures are handled separately as custom development work.
Basic third-party integrations may be included within customization plans or extensions when they work within the existing template structure.
Examples may include:
However, integrations requiring:
are treated as separate development work outside the standard customization system.
A project may become a Custom Development Request when it requires:
Creating completely new structures from scratch usually requires separate planning, architecture, design, and development processes beyond standard template customization.
Yes.
However, fully custom page development is treated as separate development work outside the standard customization system and is discussed individually.
Yes.
The studio may decline requests that fall outside the available implementation scope, technical direction, or operational structure of the studio.
Customization plans work within clearly defined implementation scope and measurable amounts of work.
This helps keep projects understandable, transparent, and manageable throughout the implementation process.
Projects are organized through customization plans, extensions, and clearly defined implementation scope.
Additional work beyond the purchased scope requires additional customization plans or extensions.
The implementation process usually follows these steps:
After purchasing a customization plan, the studio contacts the client using the email address provided during the purchase process in order to review the project requirements and confirm whether the purchased plan matches the requested implementation scope.
To avoid mistakes when choosing a customization plan, the studio strongly recommends discussing the project requirements in the website chat before making a purchase.
If the requested implementation scope exceeds the limits of the purchased plan, the project may require:
After the project requirements are reviewed and confirmed, the studio discusses with the client what project materials are available and what can be provided for implementation.
Depending on the project, this may include:
The materials and implementation workflow are discussed individually depending on the structure and requirements of the project.
Once the required materials are received, the implementation process begins.
Projects are evaluated based on:
The required customization plan is determined through the website chat.
During the request process, the system analyzes:
Based on this analysis, the suitable customization plan and required extensions are recommended.
Implementation is usually performed step-by-step according to the approved project scope and purchased customization plan.
Sections included in the customization scope are processed individually based on the required implementation work for each section.
Yes.
However, additional changes beyond the purchased implementation scope require additional customization plans or extensions.
If the client requests additional work after the implementation process has already started, the new work is reviewed separately.
If the requested changes exceed the scope of the purchased customization plan, continuing the project requires:
The implementation process continues only after the additional scope has been reviewed and approved.
Additional requests are evaluated separately based on the required implementation scope.
If additional work exceeds the purchased scope, additional customization plans or extensions are required.
A project is considered completed once the purchased implementation scope and approved customization work have been finished.
Yes.
After the amount of work included in the purchased customization plan or extension has been completed, the customization project is considered finished.
If the client wants additional modifications, restructuring, improvements, or further work after that point, the client must purchase an additional customization plan or extension.
Once the purchased implementation scope has been completed, any further work requires additional customization plans or extensions.
No.
Implementation timelines may vary depending on:
Projects are generally processed according to the current implementation queue, project scope, and active workload at the time of the request.
Templates are purchased through Gumroad using the purchase links provided on the website.
After payment is completed, the purchased digital product becomes available through the Gumroad delivery system.
Payments are processed through Gumroad and its supported payment systems.
Available payment methods may depend on the client’s region and Gumroad’s current payment options.
No.
Digital template purchases are non-refundable after delivery.
Customization plans, extensions, and purchased implementation work are also non-refundable after the implementation process has started.
Digital products are delivered immediately after purchase and cannot be returned in the same way as physical goods.
For this reason, clients are strongly encouraged to review template information and discuss customization requirements before purchasing.
Customization services are purchased through fixed customization plans and extensions.
Payment is required before the purchased customization work begins.
No.
Customization plans, extensions, and template purchases are paid in full before implementation begins.
If the client stops communication, does not provide the required materials, or abandons the project after implementation work has already started, completed work and purchased customization scope remain non-refundable.
The project may continue later through additional discussion and further customization purchases if needed.
The purchased customization plan or extension includes the amount of work approved before implementation begins.
Minor adjustments, simple corrections, and small content updates may be performed during the implementation process if they remain within the purchased customization scope and do not create additional section modifications, restructuring, integrations, or expansion of the approved work volume.
Any new requests that:
are considered additional work that changes the original implementation conditions.
Such requests are reviewed separately by the studio team, after which the client may be offered the purchase of a plan upgrade or additional extensions.
Payments, taxes, invoices, and transaction processing are handled through Gumroad and its payment infrastructure according to the client’s region and applicable payment regulations.
W-Forge primarily works with HTML website templates.
Some projects may also use Webflow versions of templates when such versions are available or requested separately.
No.
HTML templates do not require a Webflow account.
A Webflow account is only required if the client purchases or requests a Webflow version of a template.
No.
Webflow hosting, subscriptions, workspace plans, and related Webflow services are paid separately by the client.
Yes.
HTML templates work independently from Webflow hosting and can be deployed to standard hosting providers and servers.
Templates are structured for modern responsive website performance and standard frontend optimization practices.
However, final performance may also depend on:
Some templates may include animations, transitions, interactive effects, or motion elements depending on the template design and structure.
Yes.
Custom code may be added later depending on the technical structure of the project and the required implementation scope.
More advanced custom functionality may require additional customization plans or extensions.
The studio is not responsible for failures, instability, API changes, subscription problems, platform limitations, or technical issues caused by third-party services or external integrations.
Additional troubleshooting or restructuring caused by third-party systems may require additional customization plans or extensions.
Yes.
Templates are designed for responsive behavior across desktop, tablet, and mobile devices.
Yes.
CMS structures may be expanded later through additional CMS Extensions depending on the required implementation scope.
No.
External scripts, third-party plugins, external code libraries, and independently added integrations are not officially supported by the studio unless they were implemented directly as part of the purchased customization work.
Yes.
Projects may later be migrated, expanded, rebuilt, or transferred depending on the technical structure of the project and the target platform requirements.
Basic accessibility practices may be considered during implementation where reasonably possible within the selected customization scope and template structure.
Free support is limited to verified technical errors that exist in the original template version before any client modifications are made.
Technical support is limited to reviewing and correcting verified problems related to the original template structure or functionality.
A verified template bug is a technical problem that:
No.
Client-made modifications, restructuring, added integrations, custom code, or independently changed template structures are not covered by free error correction.
No.
Troubleshooting custom code, third-party scripts, external integrations, plugins, or independently added functionality is not included in free support.
Free support applies only to the original code, structure, functionality, and technical implementation organically included in the template by the studio as the template author and developer.
Troubleshooting, fixing, or supporting:
is not included in free support and is handled through paid customization services.
No.
Ongoing maintenance, continuous updates, monitoring, administration, or long-term project management are not included after purchase.
Additional fixes, troubleshooting, restructuring, implementation work, and technical corrections are handled through paid customization plans and extensions.
Yes.
Most additional implementation help, technical corrections, restructuring, integrations, project improvements, and post-purchase modifications are handled through the paid Customization Pro system.
Verified bugs or technical errors that exist in the original template source version created by the studio are corrected as soon as reasonably possible during the studio’s working hours based on Spain time.
Emergency fixes are not guaranteed for:
Such work may require paid Customization Pro services, additional customization plans, or extensions depending on the amount of required work.
Support requests are reviewed based on:
A request may be considered custom development when it requires:
Custom requests are reviewed individually based on:
Standard customization plans are designed for structured template customization within predictable implementation scope.
Custom systems, standalone applications, backend platforms, and completely new technical architectures require separate planning and development processes.
Yes.
However, completely new pages created from scratch are considered separate development work outside the standard customization system.
Yes.
However, fully custom systems are reviewed individually and are not included in standard customization plans or extensions.
Standard customization plans and extensions do not include:
Requests involving such systems are treated as separate custom development work.
Standard customization plans and extensions do not include:
Embedding or connecting standard third-party services inside the existing template structure may be possible if they work without rebuilding the project architecture.
Requests involving external application logic, platform infrastructure, or independently managed external systems are treated as separate custom development work.
Yes.
If a project grows beyond the limits of structured template customization, it may later transition into separate custom development work depending on the client’s goals and technical requirements.
Custom development projects are evaluated and priced individually based on:
No.
The studio may decline requests that:
Custom development projects usually require individual evaluation, planning, technical architecture discussion, and separate implementation strategy beyond the standard customization system.