/
OLD CSESoc Website

OLD CSESoc Website

Owned by Gordon Zhong (Unlicensed)
Last updated: May 27, 2021 by Matthew Rossouw (Unlicensed)
3 min read

Description

For a long time, the CSESOC Website has been a central place for our members to acquire information related to their studies and careers. Unfortunately, as we enter a new decade, it has become clear that the website needs to be updated to meet the new standards of design, security and functionality that we have come to expect of professional websites. While many teams in the past have attempted to recreate and rebrand the website, often problems have arose as blockers to progress. We hope current and future teams working on the CSESOC website can build on the progress of previous teams and continue to add the functionality. This will to transform the website into a viable product that the society can utilise to spread brand awareness and create a vibrant social, technical and professional environment for our members.

Vision

Over the years, there have been many suggestions towards the functionality of the website. As we look into future years, we hope to implement many of those and come up with new and exciting ways to utilise the website. The vision for current teams is to have three main requirements completed which are considered MVP. These requirements are:

  1. Bring across functionality and resources from the old website - This entails all the information that was found on the previous website being relocated onto the new website with an updated design and format. The format this time should be much more intuitive and the design fit with current design patterns and trends.

  2. Content Syndication - Due to the declining usefulness of the current website, subcommittees have used different mediums to organise and share content and events. The new website will not replace any of the utility that these tools provide but simply centralise information for those who seek it. This increases the utility of the website for all users but especially those who are new to CSESOC or are discovering what it is possible to do with us. An extended feature of this is to have the content that is made on the website syndicated across to other platforms as well which brings us onto the last requirement.

  3. Content Management System - To fully realise the potential of what our website can do, a CMS will be implemented. This is to give current subcommittees a way to add, edit and delete posts that are relevant to the wider community. It will also provide an opportunity for new portfolios in CSESOC to have a starting point to share content and make an eventual move to a different medium if need be. The hope for future teams is for them to implement these viable new functionalities as required and not have the need for portfolios to use other mediums.

Some ideas that future teams may look into include:

  • Payment system

  • Voting and polling capabilities

Current State

For anything architecture related, go here: Architectural Guide.

As of 1st August 2020:

  • Back-end code for Content Syndication epic story completed. Removal of back-end and frontend code that is not used any more in preparation for CMS epic story.

  • Testing for back-end code written and up to date for back end logic. Testing for frontend has started to be retroactively fitted.

  • Pages are still being implemented but the main focus is the landing page pure layout implementation for internal showcase.

  • Finalised style-sheet with pure layout for all pages completed.

  • Scheduled for a design guideline document and simplification of completed wireframes in accordance to the three design aspects we have chosen.

Previous States

As of the 1st May 2020:

  • All back-end code is written in Golang. This includes starting the server, API endpoints and DB logic.

  • MongoDB is used as the database.

  • API endpoints relating to posts, login and category(grouping post) and sponsors have been coded but not being used in deployment. A check needs to occur that APIs are complete and not buggy before using in deployment. Current API documentation here: https://gawdn.com/api-docs/

  • All APIs are not prefixed which needs to change.

  • The current design follows the layout shown here: https://www.figma.com/file/0QBn4fwAupXBd3CCsFLBsRoS/site-%231?node-id=0%3A1

  • Vue is statically served. The current website has:

    • A landing page that serves a Facebook events API. All other features on the landing page are placeholders for information as features are added.

    • A header and a footer with relevant information.

    • A hamburger style sidebar navigation that navigates to either template pages or are not in use.

GitHub: https://github.com/csesoc/csesoc.unsw.edu.au

 

Related content