themefic-team/tourfic

1. Tourfic is a WordPress plugin, so the runtime boundary is WordPress/PHP first, with browser-side CSS/JS shipped as plugin assets. The main entrypoints are tourfic.php, autoloader.php, and the classes under inc/.

2. The core domain is built around multiple travel product types: hotel, tour, apartment, car rental, and room. Each type has its own CPT, pricing, availability, and taxonomies in inc/Classes/* and inc/Admin/TF_Options/taxonomies/*.

3. Content editing and site setup live in the admin layer. inc/Admin/TF_Options provides the plugin’s metabox/settings framework, while tf-*-metabox.php, setup wizard, demo importer, notices, dashboard widgets, and menu/icon settings define how travel inventory is configured in wp-admin.

4. Frontend rendering is template-driven. The templates/ tree contains archive/single/search/wishlist pages, and inc/App/Templates/Components/* breaks those pages into reusable UI sections such as gallery, booking form, map, reviews, amenities, itinerary, and related content.

5. Data flow on the frontend is mostly: WordPress content + custom fields + availability/pricing logic -> template component -> rendered archive/single/search page. The repository keeps the presentation layer separate from the domain logic, so template files stay thin and domain classes compute the bookable state.

6. Search and discovery are a major subsystem. Shortcodes in inc/App/Shortcodes and widgets in inc/App/Widgets expose listings, filters, destination/brand/location blocks, review sliders, wishlist, and search forms to both native WordPress pages and page builders.

7. Booking, enquiry, and email handling form the transactional layer. Availability/pricing classes for each product type feed booking forms and backend booking screens, while inc/Admin/Booking_Details, inc/Admin/Backend_Booking, inc/Admin/Enquiry, and inc/Admin/Emails manage booking records, admin-side details, enquiry capture, and booking notifications/confirmation/cancellation emails.

8. There is a dedicated REST API boundary in inc/Classes/REST_API. Routes for bookings, enquiries, users, and each product type suggest the plugin supports JavaScript-driven interactions and external integrations beyond normal page requests.

9. WooCommerce is an optional commerce integration layer. inc/Classes/Woocommerce and inc/functions/woocommerce/* adapt hotel/car/tour/apartment bookings into WooCommerce products/orders and handle tax/VAT concerns.

10. Page-builder and template-builder support is a distinct extension layer. Elementor widgets live under inc/App/Widgets/Elementor, and Bricks/Elementor demo template JSON files under assets/demo/ show that listing and single-page layouts can be imported or composed outside the core PHP templates.

11. Static assets are split by admin vs app vs product type. The source styles live in sass/, compiled CSS/JS is under assets/, and frontend dependencies include libraries such as Leaflet, Flatpickr, Select2, Slick, Chart.js, Fancybox, and validation/notification utilities.

12. The repository also includes security regression tests in tests/security, indicating the plugin has been hardened around booking counts, REST authorization, SQL injection, and review/enquiry surfaces. Internationalization is supported via lang/ and wpml-config.xml.

13. From an architecture diagram perspective, the key boundaries are: WordPress admin configuration, domain/CPT and availability logic, frontend templates/widgets/shortcodes, transactional booking/enquiry/email flows, REST API integrations, and optional WooCommerce/page-builder integrations.