--Originally published at A project being made

This week I finally get to change some things on the front-end using the framework. The team decided it to clean the repository due to the big amount of collisions we where having. We finally integrate our templates to the working project that has the connection with firebase. Itzel and David work on writting the connection of the database to some of the code parts on the rest of the components.

Hopefully our project can look different for our next sprint presentation.

--Originally published at A project being made

Week 9 (March 13 – 18) is here, but I feel a little behind. The project is almost ready to be highly tested. These days my team will be building the back-end, so that our static information could be dinamically changed.

My work for this week:

• To finish the implementation in bootstrap of the main component.
• To help to adapt the rest of the components templates with firebase data.
• Get information of how the products will be virtually stored.

--Originally published at A project being made

A learning curve can be easily identify as a representation in graph form of the rate of learning something over time. Why is important to consider this? Well, most of the time (if not, every time) when you start a group project there will be different skills and tool knowledge. The need for an established standard of work or framework will make people to start on a learning curve. This one will be different for each participant. In my case, I learn this week that mine seem more like this:

My first attempt to add a simple bootstrap carousel inside a Angular component was an abundant failure. I try hard to simple paste some tested code, but nothing seem to work. To start working on a trial Angular project from scratch looks to be my option; and although I really want to understand the whole process of this framework, time is rushing and effectiveness is the way to go this time.

--Originally published at A project being made

Week 6 (Febraury 27 – March 4) has already began, and the pending tasks are shouting for a lot of attention. Sara is efficiently rushing with her project responsibility, and this week I have to be at the same pace. We will adding some functionalities to the static components we have so at the end we could do some proper testing.

My work for this week:

• Make the home page slider work
• Make the catalog collapse work
• Improve home page design

--Originally published at A project being made

This week I had some struggle with the framework change, and my time administration. I went out this weekend so I had to rush my work load for just three days. I wrongly thought that my knowledge in css and web design will be exact the same applying it on the Angular components, but I get slightly frustrated. The thing is that I’m in the start of the learning curve and although I wan t to really comprehend why things work different on it, the time is short and the pending tasks are stacking at a dangerous speed.

--Originally published at A project being made

Week 6 (Febraury 20 – 25) is meant for a main goal: to make the project a functional single piece. My teammates and I will work on a different Angular component, and we will find a way to test that. We already saw some ideas for user web testing, but I need to search more about it. Also I have to read more about the Angular framework, so I can understand better the big picture. I will use this post as a checklist of this week.

Things that need to get done

• • Main component template
  • Catalog component template
  • Checkout component template
  • User component

--Originally published at A project being made

So, we have had our second sprint review, and what we learned from this week is the importance of plan the framework of what are we are going to modify for future develop.

Each of us work on our respective functionalities, but it was difficult to merge the project so it could work in one single piece. Specifically on trying to merge the html templates to the angular app.

Solution?
Angular Components. Components are the main way we build and specify elements and logic on the page, through both custom elements and attributes that add functionality to our existing components.

Naturally this will be the main objective for next week, and to try to have all the structure of the front-end together.

--Originally published at A project being made

Week 5 (Febraury 13 – 18) is already starting, and the project seems to be going slower than we would like to. We hadnt used the trello table for a while, but our goal for this week is very clear: to have something to present this friday.

What are we going to present on friday?

Hopefully, a fully integrated empty project on Angular. Also the proper design of the home page and a fuctional login and register in firebase.