This is the frontend of CSSEC Website, it uses Next.js as its server-side React JS Framework. Material-UI for its layout. Also, Wordpress for its dynamic data and posts. Lastly, Google Calendar to keep track of events withint the CSSEC.

• Learn how to deploy Next.js to netlify

Javascript is the most commonly used language for web applications. Basic understanding of the core functionalities of Javascript (async/await, Promises, etc.) is required for web development.

• Next.js
• React.js
• Material UI
• Wordpress REST API
  • wpapi
• Google Calendar API
  • googleapis

First, clone this project.

Second, download dependencies

npm install

Third, run on Development Server

npm run dev
# or
yarn dev

Fourth, open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

Since, this framework uses Next.js the route followed the folder structure of pages. In Next.js, a page is a React Component exported from a .js, .jsx, .ts, or .tsx file in the pages directory. Each page is associated with a route based on its file name, as long as it is in pages folder.

• Example, if you create a file in pages folder about.js, then it is accessible through /about

const About = () => {
    return <div>About</div>;
};

export default About;

To learn more about Next.js routing, check the Next.js pages documentation.

Next.js supports pages with dynamic routes. For example, if you create a file called pages/posts/[id].js, then it will be accessible at posts/1, posts/2, etc.

If you want to add a route to the Navigation Bar just go to navigation/routes.js. It consist of an array in which you can add by adding another object.

The project follows a modularized folder structure on top of the provided structure by Next.js.

├── components
│   ├── accss
│   │   └── ... components for the accss page
│   ├── events
│   │   └── ... components for the events page
│   ├── general
│   │   └── footer.js
│   │   └── header.js
│   │   └── ... components for the every page
│   ├── home
│   │   └── ... components for the home page
│   ├── it-week
│   │   └── ... components for the IT Week page
│   ├── news
│   │   └── ... components for the news page
│   └── theme.js
├── data
│   └── ... data to be used in the site that doesn't need backend.
├── navigation
│   ├── navbar.js
│   ├── navburger.js
│   └── routes.js
├── pages
│   └── ... pages following the Next.js folder structure
├── utils
│   ├── constants.js
│   ├── google.js
│   └── wordpress.js

• The 'components' folder contains the modularized components that the pages on the 'pages' folder use. It also contains the components for the header, footer, and the theme for Material UI.
• The 'data' folder contains data in Javascript object form to be used by components.
• The 'navigation' folder contains the components for the navigation menu (both web and mobile) and the explicit list of routes.
  • nav.js - web navigation menu
  • nav-burger.js - mobile navigation menu
  • routes.js - list of routes
• The 'pages' folder contains the pages of the project.
• The 'utils' folder contains external APIs, constants and generators, such as the backend Wordpress URL, for the project.

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

Only pull request if there's seem a minor issue that you can resolve. For major changes, please open an issue first to discuss what you would like to change.

• Ateneo de Davao Research in Information Systems and Software Engineering Lab (ARISEn Lab)
• Computer Studies Executive Council (2020-2021)

MIT