Replace all mock data with real backend integration
- Add database tables for email configs, settings, and activity logs - Create backend endpoints for dashboard stats, analytics, archives, email config, and settings - Create frontend service layer (admin, archive, email, settings services) - Update AdminDashboard to use real statistics and activity data - Update AnalyticsPage to fetch real analytics from backend - Update ArchivesPage with pagination and real archive operations - Update EmailConfigPage to manage real SMTP config and templates - Remove all mock data and replace with API calls throughout admin interface 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
This commit is contained in:
@@ -1,12 +1,16 @@
|
||||
const express = require('express');
|
||||
const router = express.Router();
|
||||
|
||||
// This route handles admin endpoints that are different from events
|
||||
// For now, just export an empty router as events.js handles most admin functionality
|
||||
// Import sub-routers
|
||||
const dashboardRoutes = require('./adminDashboard');
|
||||
const archiveRoutes = require('./adminArchives');
|
||||
const emailRoutes = require('./adminEmail');
|
||||
const settingsRoutes = require('./adminSettings');
|
||||
|
||||
// Admin dashboard data could go here
|
||||
router.get('/dashboard', async (req, res) => {
|
||||
res.json({ message: 'Admin dashboard endpoint' });
|
||||
});
|
||||
// Mount sub-routers
|
||||
router.use('/dashboard', dashboardRoutes);
|
||||
router.use('/archives', archiveRoutes);
|
||||
router.use('/email', emailRoutes);
|
||||
router.use('/settings', settingsRoutes);
|
||||
|
||||
module.exports = router;
|
||||
Reference in New Issue
Block a user