Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/tsehang/netbase


https://github.com/tsehang/netbase

Last synced: 6 days ago
JSON representation

Awesome Lists containing this project

README

        

# Netbase

> [DEMO LINK](https://netbase.vercel.app)

#### Technology stack

- **Framework**: [React.js](https://reactjs.org) for build UI, and [Next.js](https://nextjs.org) for production.
- **Typescript**: for better developer experience.
- **UI**: [styled-components](https://styled-components.com)

This project is bootstrapped with [my-frontend-boilerplate](https://github.com/TseHang/frontend-boilerplate).

## Usage

First, install node_modules and run the development server

```bash
yarn # install dependencies
yarn dev # run the development server
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

#### Other commands

Build:

```bash
yarn build
```

Run production:

```bash
yarn start
```

## Time management

| Date | time(mins) | works |
| ----- | ---------- | ------------------------------------------ |
| 10/23 | 15 | read spec / init project |
| 10/23 | 120 | complete all features / functions / layout |
| 10/23 | 40 | improve animation / icons |

## Futhermore...

#### What is my workflow?

In this project:

1. I start from reading specification, thinking what I need to do.
2. Simply draw the draft UI in paper, list the component what I need.
3. Start coding.
4. After finish all requirements on spec, I starting to improve styling and animation, like adding [react-spring](https://www.react-spring.io/docs/hooks/basics).
5. Open Github private repo.
6. Deploy

And here is my real work experience if you want to know:

Before starting, I like to write some thoughts or scope definition first, it is good to help me thinking and entering the situation quickly.

In task management, I prefer using an application like Jira, Asana and Notion to focus on **each task**, including development tasks, issue tasks, improvement tasks and test tasks.

In negotiation, if it is about whole project, which can be discussed in our team communication application, like Slack. If it is about task, just discuss under each task in our task management application.

In development, open Pull Request for each task or task's sub task. Must one of reviewers approved and CI test success, the PR can be merged into master.

Thanks for your reading.