Skip to content
This repository was archived by the owner on Apr 11, 2022. It is now read-only.
This repository was archived by the owner on Apr 11, 2022. It is now read-only.

[*Critical Feature]: Framework decision for website backend & frontend #81

@tintinkung

Description

@tintinkung

We will eventually have to use a website framework when the project starts to grow and gets out of prototype state.
pro of all framework obiviously is helps organize projects alot, the html and css writing convention will be get alot less issue.
the thing is I dont know how and what framework everyone is experienced at or have some used with it.

heres some framework i research(have nothing with my experience or personal opinion)

Frontend

  • bootstrap (already using)
  • Jquery (already using)
  • TailwindCSS - css extension(better bootstrap)
  • Flutter (use dart coding language so maybe no)

Backend


Node.js

these required nodejs to use (i think)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions