Categories
Uncategorized

6th report of the term: Sprinting as a developer

This week was busy, and after working this week on the upcoming due assignments throughout the week I later moved some Trello tasks that were brought up in our meeting earlier this week. The upcoming assignment such as the update design document needed some additions, and the Trello tasks changes helped correct our priorities as some tasks were moved from blocked to todo or product backlog. I also found from our group discussions that for Cascading Style Sheets (CSS) styling the best for our project may be Sassy cascading style sheets (SCSS) and tailwind! I also took a look at the CSS file provided by ATF so that we may adapt it to our new theme. This will help me with the new sprint we started this week as I work as a developer role, to fill in some of the lack of style, and so our theme is finally good looking. Moving into next week I will need to complete the header, some CSS styling, and move on to work on the product pages. For the header specifically we need the search function, and some much needed styling. The individual product page implementation is also a big task that may be handled this week. The list page status needs to also be checked on for this week, after those previous items. Next we will definitely need to create dynamic style size, and any cart pages. To move forward with the tasks at a good pace it may be valuable to use the time now to make basic pages, where the page design, and styling is worked on later. Pages such as the cart pages will have us working with new types of objects that may influence our design later as we discuss the design later. For the most part the implementation should be smooth, with nice weather, and with incremental progress.

Categories
Uncategorized

Sprinting as product owner

This week was a busy one as our team worked on creating the alpha prototype, and updated the design document for our ATF project. This was a lot to do and luckily the due date was extended to Wednesday just in the afternoon today the day they were due. This will be helpful for our team since at least one member is without power, and overall it will allow us to piece more things together for the final result. As the product owner for this I thought it may be good if I focused on designs by creating few of them so that we may get them approved for the design, and then code development. This may help the developers with progressing with the code since they can create the new sections once the designs are fully approved. These designs may additionally be helpful for the second task will be an update for the design document, and we will be using the previous document and building on it. The extension additionally will help give time for any additional changes to those new designs. Moving forward for the alpha code task we will need to submit video screencasting it while highlighting our changes. We in the coming weeks will also be building on our css code to get the styles of our design looking good. We are also looking for adaptive design features for our containers as we are finishing some base code for the pages. These next weeks our team will also be looking for all opportunities to make use of liquids features such as with sections or tags. The cart development is something that we will also be working on in the near future, with objects such as the order object that will need to be used appropriately for best coding practices.

Categories
Uncategorized

4th Log of the term: Sprints

From the previous meeting we have made progress on the API question, there was a response from the Shopify team pointing to their documentation, and I took some time to read on it for the answer. It was very informative, and after reading I responded from what I read about for how may implement the api in the future. The documentation discussed the OAuth API usage, so I went to read more on that, and after some additional research on what API access would be provided with OAuth it seemed like the answer for what we need. For my question on what type of API access will we need to pull product information from other store to display on our site it seems we need to use OAuth with a public application for Shopify. This is what I concluded we would need to move forward with presenting products from an individuals store to be viewed on our store, we can still work with our secondary option for listing products from another store, and we for now will leave this feature to later to deal with by replacing it with a link to their Shopify website.

This week we all swapped roles again and for this spring up until the code alpha presentation I will be the product owner. Being the product owner I am tasked with tasks such as consider the product from the owners perspective. Specifically this week I am tasked with creating a design for the product page with the lucid charts service for our liquid theme. This will be the layout for the theme template, and will be implemented next. One thing to consider is that we have section files now for sections such as the header and footer. When a section is placed, the contents of the section file are placed there, and we should use those sections appropriately for the product page to be efficient.

Categories
Uncategorized

First Code Review

This week we have a code review where we have to review what we created for this previous sprint. This previous sprint as scrum master I was tasked with creating the header for the website for both designs being created this week. For this I just built the one that I thought that had the most complexities, for the other version some changes are needed and it may be made with some removals.

For the header this week I reviewed the standard layout of the Shopify “theme.liquid” file (1). This file is the main file that contains most of the theme’s sections starting with the header section that I want to change for this week. For the first header design the plan is to have from left to right to have an ATF logo, name of the farm, farm address, map (2), and navigation bar (3). To do this I need to convert the photo we have to a “.svg” type file that creates a more efficient image with vectors (4). Next I created a “style.css” sheet to be preloaded in the header for the design of the header. This style css file is where the positions and colors for theme’s header are set. This worked at one point, and then somewhere down the line stopped working, and I may address this in our next meeting since I am confident another team member may have some helpful insight.

Next I created a “header.liquid” section file for the header content (5). Looking forward, I would like to connect this header section file with the content variable for the header section, and that is because I have yet to integrate that content variable. This “header.liquid” file is made in conjunction with the “theme.liquid” and in placed in the header with the “{% section ‘header’ %}” section command referencing the class tag. This header is going to carry many settings for across all pages, this is done to organized, and for reducing repetitive code. This new directory for the theme, called sections will allow us to access global objects, with special liquid tags. This header section liquid file may also be created for a section such as the footer.

Last of all, I worked with themekit briefly on my system, by connecting the API, and changing settings to be able to create new themes from my command line.