https://github.com/fostimus/pyxis

Less than 2 day design and code, in collaboration with GA's UXDI students. I was partnered with 2 design students, who used Figma to put together a stellar design for the problem statement given to us. I took the design and brought it to life in Express.js and EJS, using Bootstrap for animations and styling.
https://github.com/fostimus/pyxis

bootstrap4 ejs expressjs figma

Last synced: about 1 month ago
JSON representation

Less than 2 day design and code, in collaboration with GA's UXDI students. I was partnered with 2 design students, who used Figma to put together a stellar design for the problem statement given to us. I took the design and brought it to life in Express.js and EJS, using Bootstrap for animations and styling.

• Host: GitHub
• URL: https://github.com/fostimus/pyxis
• Owner: fostimus
• Created: 2020-11-23T21:52:33.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2020-11-26T04:46:02.000Z (about 4 years ago)
• Last Synced: 2024-10-14T19:11:19.105Z (3 months ago)
• Topics: bootstrap4, ejs, expressjs, figma
• Language: HTML
• Homepage:
• Size: 11.1 MB
• Stars: 0
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Pyxis Restaurant News

As part of the GA Software Engineering Immersive course, we worked directly with UX/UI students on a 2 day "Collabathon". Our client was "Pyxis" Restaurant News, and the designers I worked with did an incredible job to create a professional design with limited requirements--all on a tight deadline. The design can be found [here](https://www.figma.com/file/oqw8qhJZUHkxpoQKFa2nLH/Restaurant-News-Website-Copy?node-id=0%3A1).

# Developer Considerations & Lessons Learned

The process of working with designers was an unparalleled learning experience. I've worked with clients to do enterprise software development in the past, but this was unique in that the requirements for the software were fluid and subject to change at any given moment.

While this is not completely realistic in a "regular" software development team, this certainly happens with front end development and it was nice to experience that. Besides the overall experience, some learning highlights:

1.  Finalize the data models, but focus on providing a visual prototype

2.  Utilize design tools (Figma) for relevant information

3.  Develop mobile first

## Finalize the data models, but focus on providing a visual prototype

I learned early on in my career the importance of an accurate data model upfront. It drives many, many requirements and allows for a clearer direction when developing.

While we nailed down what the User would look like early, I took too much time developing the backend. In an environment where a visual MVP is needed ASAP, developing the backend is not required. Especially when working directly with designers, the critical feedback loop is interrupted if developers get bogged down in the details of unnecessary server logic.

##