Skip to content

FAQ

THE WINKDOM FAQ / A PLACE TO START

Good questions.
Clear answers.

Understand the tools. Explore the details.
Find a little clarity for what comes next.

From your first page to the technology underneath it, here are the essentials about working with Winkdom.

Explore the answers

01 / GETTING STARTED

First, the
essentials.

A quick introduction to Winkdom and the roles its tools play.

What is Winkdom?

Winkdom is a connected product family for creating websites and running the business around them. It spans content, design, commerce integrations, customer relationships, community, support, and automation.

Builder, Theme, and Docs are the foundations. The wider ecosystem includes tools such as Sites, Forms, CRM, Email, Community, Chat, Support, SEO, Analytics, Auth, Cookies, Affiliate, and Ads. PWA and Flutter app builders are on the roadmap.

Meet the toolkit

Is Winkdom built on WordPress?

This website uses WordPress. Builder publishes native pages, Theme provides the shared site shell and design system, and Docs manages documentation. InstaWP is the primary WordPress cloud direction for the wider ecosystem.

The wider roadmap includes native EmDash ports and migration work, plus a planned Winkdom CMS using Go and PostgreSQL. Availability and compatibility vary by product.

Which tool should I start with?

Start with the part of your project that needs attention:

  • Builder for composing and refining pages.
  • Theme for a consistent identity, navigation, header, and footer.
  • Docs for organizing guides and product knowledge.

These three establish the website experience. The Toolkit page also explains the business plugins, platform directions, and app roadmap.

Find your starting point

Is this website made with Winkdom?

Yes. These pages are authored in Winkdom Builder and presented through the Winkdom site shell. The layouts and illustrations use custom HTML and CSS, with styles that adapt to the site’s light and dark appearances.

The thinking behind Winkdom

02 / BUILDING & DESIGN

Make room for
your identity.

Creative control, responsive layouts, and a consistent experience.

Do I need to write code?

Builder provides visual controls for working with page content and sections. HTML and CSS are available when you want more detailed control over a layout or visual treatment.

The amount of technical work depends on the design and the integrations your project needs.

Can I use my own brand and design?

Yes. Theme provides shared settings for colors, typography, spacing, and the site shell. Builder gives you control over the content and layout of individual pages.

Custom HTML and page-scoped CSS can add distinctive details while keeping the wider site identity consistent.

Explore Winkdom Theme

How do I design for phones and tablets?

Use Builder’s screen-size previews to review the layout as you work. The Winkdom site shell includes responsive navigation, while each page’s content and styles determine how its own sections adapt.

Check long headings, images, spacing, and interactive elements at smaller widths, then review the published page on the devices that matter to your audience.

How does light and dark mode work?

The shared appearance system supplies colors for surfaces, text, borders, and other interface elements. Pages that use those design tokens can adapt with the site’s selected appearance.

Custom styling should account for both modes. You can try the appearance control in this site’s header to see how these pages change.

03 / SPEED & TECHNOLOGY

A little more
understanding.

What happens between the first visit and the next page.

What makes navigation feel more fluid?

The first visit starts with a server-rendered document. On eligible routes, Vue coordinates page transitions while the shared site shell stays in place.

This lets the content change without rebuilding the entire surrounding experience on each supported transition.

Inside the technology

Does every page open without a full reload?

No. That behavior depends on the route and its integrations. Eligible destinations can use Winkdom’s coordinated navigation; other destinations use normal browser navigation.

The aim is to keep navigation appropriate to the content and the tools involved.

What affects a website’s loading speed?

Hosting, page content, images, active plugins, caching, and the visitor’s device and connection all contribute to loading time.

A good architecture is a starting point. Review the actual published site with realistic content and measure the journeys your visitors use.

Explore the approach to speed

Can Winkdom create mobile apps?

Two offerings are planned: a quick PWA solution that builds on the website, and a full Flutter app builder for dedicated mobile applications. Availability and release dates have not been announced.

Read the PWA and Flutter comparison on the Apps page to understand the different approaches.

Explore Winkdom Apps

What is Flutter, and why use it?

Flutter is Google’s open-source framework for building interfaces using Dart. A shared codebase can serve iOS and Android, with mobile release code compiled to native machine code.

It offers detailed control over branded interfaces and access to device APIs through plugins and native integrations. Each platform still needs configuration, testing, and release management.

Why Flutter

What does security mean in this ecosystem?

Security is an ongoing engineering responsibility. The product family includes authentication, consent controls, protected submissions, and scoped integration tools.

The design priorities are server-side authorization, protected credentials, deliberate permissions, updates, and recovery. Actual protection depends on the configured hosting, products, and integrations; no stack makes a site automatically secure.

What technology will Winkdom CMS use?

The planned Winkdom CMS direction uses Go and PostgreSQL, with cloud automation and serverless deployment as architectural goals. EmDash is a separate platform built with TypeScript and Astro.

These are different foundations for different needs. Scaling requires appropriate data access, caching, background processing, infrastructure, and testing; it is not an unlimited-capacity promise.

Explore the platform roadmap

Can I migrate between WordPress, EmDash, and Winkdom CMS?

That is the direction. Native ports and migration tools are being developed and qualified for supported content and product data. Readiness differs by tool and by migration route.

A complete migration must account for content, media, identities, permissions, commerce records, URLs, integrations, and recovery. Confirm exactly what is supported before moving a live site. More platforms may be considered later.

Discuss a migration

Will there be free, open-source editions?

Winkdom.org is planned as the home for the open-source CMS and free plugin editions. The domain and website will be established later.

Licenses, feature boundaries, distribution, and support will be stated for each product. A free edition does not imply that hosting, paid integrations, or every advanced feature is included.

The open-source direction

Is the complete AI site-launch flow available now?

AI-assisted creation is part of the development direction, including a describe, preview, refine, and launch journey. The complete public launch flow is still being qualified.

Existing website editing and individual AI capabilities should be distinguished from a fully released end-to-end creation service. Contact us for current availability.

04 / PLANNING & HELP

Your project.
Your next step.

Find the right information for the setup you have in mind.

Where can I find pricing and licensing details?

For current pricing, licensing, and product availability, email [email protected]. Include the product you are interested in and a short description of your project.

This helps us discuss the details that apply to your setup.

Can I use Winkdom with an existing WordPress site?

Builder supports different WordPress theme arrangements. The right approach depends on your active theme, plugins, and the parts of the site you want Winkdom to handle.

Share your current setup and the outcome you want so compatibility and the implementation approach can be discussed before you make changes.

Discuss your setup

How can I ask for help or share feedback?

Write to [email protected] with the product name, what you are trying to do, and what happened. A relevant public page link can provide useful context.

Keep passwords, API keys, and other credentials out of your message.

THE CONVERSATION CAN CONTINUE

Still curious?
Let’s talk.

A specific project, an unanswered question, or a useful piece of feedback. Tell us what is on your mind.

[email protected]

Secure account access

Welcome back

Sign in to continue without leaving this site.