Home Page
The home page acts as the main entry point of the application. It presents the theatre brand, key announcements, recent blog posts, and links to the main sections. A user can quickly move to About, Blog, Contact, or account login.
PROJECT CASE STUDY
Mefisto Theatre is a full theatre web application that combines a public website with user accounts and separate staff and admin areas. Visitors can read theatre information, browse blog content, comment on posts, send messages, and manage a profile. Staff and admin users can manage content, comments, users, roles, and contact messages.
PUBLIC PAGES
This part of the application is available to visitors. A user can learn about the theatre, access the blog, read posts, and send a contact message.
The home page acts as the main entry point of the application. It presents the theatre brand, key announcements, recent blog posts, and links to the main sections. A user can quickly move to About, Blog, Contact, or account login.
The About page describes the theatre, its background, style, and purpose. It works as a brand information page that helps visitors understand what Mefisto Theatre is and what type of content or events it represents.
The blog listing page shows the public list of posts. A user can browse articles, check category, publication date, and view count. The page supports filtering, sorting, and opening a full post.
The single post page displays the full article content. A user can read the post, check related information, view comments, and move to recommended or related posts.
The contact page contains theatre contact details and a message form. A visitor can enter their details, subject, and message. The message is then available inside the staff/admin area where it can be reviewed and handled.
ACCOUNT PAGES
These pages handle user access, profile data, and interaction with content. They allow a standard user to log in, manage account details, and participate in blog activity.
The login screen allows a user to access their account. After login, the system recognises the user role and can direct them to a standard profile, staff dashboard, or admin dashboard.
The registration page is used to create a new user account. After registration, the user can log in, have a profile, and use functions assigned to a standard role.
The user profile page displays account details, avatar, personal information, and membership level. A user can update their information, change the profile image, and maintain basic account details.
A logged-in user can use comments under blog posts. Comments are connected to the user account and can later appear in the staff/admin moderation area.
ADMIN PAGES
The admin area gives full control over the application. Admin users can manage users, roles, content, categories, comments, and messages sent through the contact form.
The admin dashboard shows key system metrics, active users, content activity, and moderation overview. It is the central starting point for full project management.
The user management page allows an admin to browse accounts, edit users, change roles, suspend or delete accounts, and control activity status.
The edit user form allows changes to contact details, membership level, profile information, and account settings. Admin can correct user data without directly editing the database.
The role management panel controls access levels in the application. Admin can create, review, and assign roles to separate standard users, staff users, and administrators.
The blog management panel controls all posts. Admin can review entries, edit content, delete posts, check publication status, and maintain the public blog area.
The categories page allows an admin to add, describe, and remove blog categories. This keeps posts organised by topic and easier for users to filter.
The comments dashboard shows all comments with linked user, post, date, and status. Admin can review user activity and moderate content added under posts.
This section shows comments waiting for a decision. Admin can approve content, remove it, or leave it for later review. The page also handles the empty state when no comments are pending.
The accepted comments view shows content approved for display. Admin can review it again, inspect details, or delete it if the comment no longer meets the rules.
The user messages panel collects messages submitted through the contact form. Admin can check sender details, subject, message content, and decide whether the message requires a reply or deletion.
STAFF PAGES
The staff area focuses on daily operational tasks: checking statistics, creating posts, reviewing comments, checking users, and handling messages.
The staff dashboard shows a quick overview of statistics, latest comments, and recent users. It acts as the starting panel for people managing content and basic site administration.
The posts dashboard shows a table of posts with title, category, author, publication status, date, and view count. Staff can quickly check which posts are published and which need updates.
The create post form allows staff to add a new article. A staff user enters the title, selects a category, sets the publication status, and adds the article content.
This view helps staff maintain the blog day to day. Staff can review existing posts, open them for editing, check content quality, and remove posts if they have the required permissions.
Staff can review comments added by users, check which post they belong to, and support moderation. The view makes it easier to detect content that needs approval or removal.
The staff users view shows a list of accounts, roles, activity status, and basic actions. Staff can quickly find a user and check basic account information.
Staff can check messages sent through the contact form. This view helps handle visitor enquiries, check sender details, and decide whether the case should be escalated to admin.