Project Title: Campus Events and Entertainment Center
This is the architecture of the frontend, which was designed at the beginning of the project. The architecture shows the logic of the page-routing and the most important components of each page. The frontend is separated into user-end and admin-end.
The admin-end is to manage the authority of the users, delete events or posts. The user-end is to show the events and posts. For the users with the authority to create events, they can create events using the user-end.
In the user-end, once the user logs in, the users can see the events and posts at the main page. They can click the events or search for the events they are interested in. For the detail page of an event, the users can see the information of the event, apply for the event, leave comments, and see the related posts. By clicking the posts on the event detail page, search for posts, click the posts on the main page, or go to the post square, the users can view the posts and leave comments. They can also write posts and link the posts to an event. Back to the main page, the users can edit their profile, see the events they have collected, and see the posts they have written. If the users have the authority to create events, they can turn to the event management page to create events, see the events they have created, and see the people who have applied for the events.
Our comments are divided into event comments and replies. Replies can be made to both event comments and other replies. Ultimately, the comment section will form a hierarchy, with each event comment being a section, under which there is a series of replies.
Our events are not divided into many classes. Instead, we abstract the different stages that may occur in the lifecycle of various events and they can be freely combined. Currently, the only stage we have is enrollment.
There are many ways to enroll, such as free enrollment with quota restrictions and enrollment with registration form review, etc. At the same time, various registration methods may also have common subsequent stages, such as seat selection.
Each of our enrollment entity classes corresponds to a unique event entity class and is responsible for saving the enrollment information of that event.
We divide all users into administrators and users. Their functions do not intersect. Administrators can only enter the management page, while users can only enter the user interface. The user's permission system allows each permission to be separately authorized by the administrator, such as creating activities, posting comments, etc.
This page is to show the detailed information of an event. The basic information part on the top-left corner shows the basic information including the title, time, score, and so on. The body part shows the description of the event, along with the poster of the event. The comment block is under the body part. On the right panel, There are the information of the event holder, and a list of the posts related to this event.
This is the card to show the brief information of an event. The card includes the poster of the event and some basic information. The card is used in the main page and the search page.
in event page, we can evaluate the event and creat various events.The featrue "Effort lessly Organize a variety of activities"
This is the massage page, which take the message page of Bilibili as a reference. The leftest panel is to choose the types of the message. The middle panel for type 'chat' is to show the name list of the users who have chatted with the current user. The right panel is to show the chat history of the selected user.
This is the comment block, which take the comment block of Bilibili as a reference. The comment block is structured as a two-level hierarchy. The first level is the comments of the event or the post, and the second level is the discussions under a certain comment. The comment block is used in the event detail page and the post detail page.
The chat system and the comment block implement the feature "Connect with Friends and Extend Invitations".
On the main page of PostSquare, in addition to the header and aside, there is a sub-header, thumbnail cards for various posts, a carousel for popular or recommended posts, global notifications, and more.
In the sub-header, there are various commonly used buttons along with a search box for finding posts of interest. The thumbnail images of posts provide the title, image, and some content of the post, along with shortcuts for liking, bookmarking, sharing, and the corresponding number of users who have taken these actions. Clicking on the other parts will pop up a window to enter the detailed content page of the post. The carousel can showcase popular posts or events and provide a way to navigate to them. Global notifications facilitate notifications for campus-level activities or announcements from administrators.
For now, Post Square and Post Detail have implemented feature "Share Activity Content and Experiences Through Posts".
in main Page and search page, users can discover Activities of interest which is one of our feature.