Skip to content

Latest commit

 

History

History
42 lines (30 loc) · 3.34 KB

instructions-1-front-end.md

File metadata and controls

42 lines (30 loc) · 3.34 KB
Raw

Front-End Development

Each team must have completed and demo'd the working front-end of their group project by the end of the corresponding Sprint.

Technical requirements

The following requirements outline what must be, must not be, and may be done during the front-end development sprint.

Musts...

  • All front-end code must be generated using React.js.
  • All component definitions must be written as functions, not as classes.
  • All component content must be written using JSX, not only plain Javascript.
  • Front-end screens must be custom-designed to look clean, contemporary, and sharp, not like a wireframe.
  • Any user-generated images that will be displayed by your app must be temporarily mocked with a random image API service, such as Picsum.
  • Front-ends must include all screens in the completed application and should closely match the clickable prototypes created previously, unless the team believes an alternate user experience is beneficial.
  • Ay mismatch between the clickable prototypes and the front-end app code delivered must be explained during the stakeholder demo.
  • Any front-end dynamic functionality, such as buttons that change something on the screen when clicked, or search fields that filter results as they are typed into, must be implemented in the front-end.
  • If your app will eventually have user registration and login functionality, all front-end screens to support this must be created, although they can be non-functional for now.
  • Instructions on how to set up and run the project must be included in the README.md file in version control. It must be possible for anybody to follow the instructions on the README.md to build and run the entire project on their local machines.

May...

  • You may use React Context for sharing state among multiple components.
  • You may use the front-end framework, Tailwind to streamline your CSS styling.
  • You may use mockaroo, picsum and other mocking/faking tools to mock any data that will eventually come from your application's back-end or other external source.

Must nots...

  • You must not any 3rd-party state manager tools, such as Redux or Mobx
  • You must not use next.js or any other server-side rendering framework.
  • You must not use the front-end frameworks Material UI or Bootstrap.
  • You must not hard-code any data in your front-end code that will eventually be provided by your application's back-end or other external source.

Grading

Individuals will be graded, in part, according to...