This was the first group project completed while being a trainee web developer with TechNative academy.
We decided to allocate a page to each other. And split each page into multiple sections, which we called components. Each component got it’s own ticket on a trello board.
- Index - Chloe
- About - Conrad
- Products - Seb
We decided to do this to allow each other a chance of working on HTML, CSS and JS. As well as reduce any conflicts in Git. This was our method until day 3, when we realised the index page required a lot of work. So we each took a section and improved it, based on each other's and Pete's feedback. We layed some HTML boilerplate and a some Global CSS on the first day.
- We used trello to create a ticket system.
- We made pull requests and put the link in slack, as well as updated the tickets.
- Each morning we had a stand up talked about what to do, and kept up to date with each other throughout the day in slack.
- In our PR we tried to include screenshots to show each other our changes.
- We communicated well
- Improvement with Git workflow as project progressed.
- Good working on a page each
- Workload felt equally distributed, played to each others strengths and interests
- Chance to play around with everything we’ve learned so far
- Failing forward, improving through failure
- Prettier formatting
- All of us accidentally committing to main
- Using global CSS selectors in individual page CSS
- Spending enough time considering mobile-first design to start.
- Had some git conflicts
- Configure prettier before writing any code
- Mobile-first
- Create more modular CSS, avoid having a large global.css file
- Potentially a live call during busier spells to quickly discuss issues
- Utilise JS classes for products instead of hard-coding into html
- Modular CSS can be a better choice
- Spend more time planning / mobile-first / organising file structure before starting coding
- Spend less time on optional items and make sure to complete essential items first
- Trello is useful (If you don’t forget about it)
- Git workflow isn’t so bad once you get used to it
Day 1
On the first day, we were all in person. We were given a brief and a figma page with the website desgin. Our task was to create our own company and use the provided design to create our website! So the first day included figuring out how were going to approach the task, where we came to the conclusion that we would split the 3 pages between us. We split the design into multiple sections we coined compartments, then layed the boiler plate HTML. We also created the global CSS file and put in the variables.
Day 2
- Footer
- Hero
- Responsive design
- JS
- Figure out the content (e.g images, text)
- Finish by Friday
- Conrad - 66.66%
- Seb - confident but maybe not after js
- Chloe - 90%
- Conrad - 100% for min requirement
- Seb - 100% for min requirement
- Chloe - 100% for min requirement
- Conrad - "I don't like the trello board"
- Seb - "can be frustrating but will get used to it"
- Chloe - "Conrad is mean to me about the bananas :("
- Lots about git workflow
- logistics is 2/3rd of the work!
- Responsive design is hard
- Excited for tomorrow!!!
- Excited for JS
- Tired :(
