How sekju/notion-to-wp_fluentcommunity-import works
Project type and purpose
• This is a full-stack single-page application whose purpose is to import content from Notion into a WordPress-based FluentCommunity site.
• Key features: React/TypeScript frontend (Vite), Node.js/Express backend proxy, integration with Notion API and WordPress REST API via a custom WordPress plugin.
File structure
• Top level
• /src – React SPA code (App.tsx, components, services, types, utils)
• /server – Node/Express API (index.js)
• fluent-community-importer.php + functions.php – WordPress plugin code
• Config files (vite.config.ts, tsconfig*.json, postcss.config.js, tailwind.config.js, Procfile, railway.json)
• Patterns
• “frontend vs. backend” separation
• Service layer in src/services (notionApi, wordpressApi, importService)
• Wizard-style UI in src/components/Steps
• Deployment artifacts
• Procfile/railway.json for Railway
• .env.example for secrets
README for additional insights
• Architecture described implicitly:
• Frontend makes API calls to /server
• Server proxies calls to Notion and WordPress APIs
• WordPress plugin extends WP REST endpoints to receive course/lesson payloads
• Dependencies & stack: Node.js 18+, React, Vite, Express, Notion SDK, standard REST calls to WP.