Question 1

How do I connect a React component to a WordPress post using Kasia?

Accepted Answer

Use the @connectWpPost decorator with the content type and identifier, like @connectWpPost('post', 'slug'). The README provides an example fetching a post by slug, and data becomes available in this.props.kasia.

Question 2

Kasia or WPGraphQL for React WordPress projects?

Accepted Answer

Kasia uses the WordPress REST API and integrates with Redux, ideal for teams already invested in that stack. WPGraphQL offers GraphQL queries, which might be better for complex data fetching with less boilerplate, but requires a different setup.

Question 3

Can Kasia work with Next.js for static site generation?

Accepted Answer

Yes, Kasia supports server-side rendering with preload utilities, but it's primarily designed for dynamic React apps. For static generation, you might need to adapt the SSR features or consider other tools like Gatsby with WordPress.

Question 4

How to add custom WordPress API endpoints to Kasia?

Accepted Answer

Extend Kasia via plugins, which can define custom reducers and sagas. The README shows plugin examples like kasia-plugin-wp-api-menus, or you can create your own by following the plugin API.

Question 5

Does Kasia support WordPress authentication and private content?

Accepted Answer

Kasia relies on node-wpapi, which can handle authentication, but the README doesn't detail it. You'd need to configure wpapi with credentials, and Kasia will pass queries through, but advanced auth scenarios might require custom sagas.

Question 6

What are the performance implications of using Kasia?

Accepted Answer

Normalization reduces duplicate data in the store, but complex queries with embed can increase payload size. Since it uses Redux Sagas, async handling is efficient, but large datasets might impact initial load times without proper caching.

kasia

What is kasia?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions