WordPress (Classic themes, Gutenberg-compat). Vite. Tailwind v4. Swiper. Bootstrap Icons + Remixicon. ACF Free, CF7. Next.js + Drizzle for Web Apps. Expo + React Native for Mobile Apps. Liveblocks / WebSockets / CRDT for Real-time.
No. No Elementor, Divi, WPBakery, Beaver, Bricks. The theme owns the design; the database owns the content; the editor edits content, not layout.
I support both. The theme works end-to-end with ACF Free + a native repeater fallback. ACF Pro adds nicer admin UX but is not required.
I don’t host. I will recommend hosts (Kinsta, WP Engine, Rocket.net, Pressable) and set up the WordPress side. The contract is between you and the host.
The theme is translation-ready and ships an RTL stylesheet. For multilingual content I integrate with Polylang or WPML — pick one before scope.
I’ll integrate WooCommerce if the engagement requires a shop, with HPOS compatibility and Block-Editor checkout. I do not retrofit the existing Pixy Puala Classic theme for shop UI in v1.
I do headless cutovers as one of the Sprint Catalogue offerings. WP REST + Next.js + WP-Image-CDN. Editorial stays in WordPress; rendering moves to Next.js.
Yes — for post-content composition. The theme’s design system is not Block Editor-driven; it’s Customizer + template hierarchy + meta. Editors compose body content with core blocks.
Sometimes. For content-heavy sites where editors compose pages, FSE is the right answer. For marketing sites with a designed point of view, Classic is. Decision is per project.