Showing posts with label teamwork. Show all posts
Showing posts with label teamwork. Show all posts

Thursday, 17 September 2015

Week 8: SASS how-to

Initial set-up

  1. Download the source files from Bootstrap 
  2. Unzip them into the folder where you will be using them (in our case, I have set-up a 'SASS' folder in our git repo)
  3. Follow the instructions on tooling set-up on Bootstrap (repeated below)
    1. Download and install Node.js
    2. Using the command line (Terminal, iTerm, Powershell, what-have-you), install Grunt with npm install -g grunt-cli
    3. After a quick refresher in command line, navigate to the Bootstrap folder that you unzipped (for us: 'SASS' as above).  OK, so now you're using the command line and you're in the Bootstrap folder.  If you type ls it should look similar to this:

    4. Install the local dependencies listed in package.json by running npm install
    5. Next up is Ruby.  If you are on a mac, you should have it already installed but can check by typing ruby -v into the command line.  If you need to download or update there is info here and here.  But, if you need to install on Windows, we ran into a few problems and used this tutorial from Forward HQ to sort it out.
    6. Almost there! Two-parter for Bundler: 1) install in the command line by running gem install bundler and then 2) run bundle (for all the Ruby dependencies you will need).
  4. Last step, install SCSS Lint by running gem install scss_lint
Phew, you still with me?  You may (or hopefully not) have any errors.  You may need to prefix the command line with sudo (I know, I know, lots of people say you shouldn't), or might get other random errors (google is your friend), but hopefully you have the things installed.  Now for the fun part :)

Using SASS

In your Bootstrap folder (for our team 'SASS') is a folder called 'scss' which is filled with many, many .scss files.  Being Bootstrap, it is all fairly logically named so it shouldn't be too hard to find any CSS you need to change.  '_variables.scss' has all the colours and typography (amongst other things), etc, etc. Have a look at the SASS documentation for how to use variables, nesting, other syntaxy-things.

Once you've changed the things you need to, how do you get it to be a CSS (and JS) file to use on the website?  Back to the command line!

To compile the CSS/JS files:
  1. Using command line, navigate to the bootstrap folder we were working in before.  You may still be there :)  (I'm a broken record but "For our team it is the 'SASS' folder")
  2. run grunt dist and fingers crossed, 0 errors!
For our purposes, that's about it but there is more info on grunt commands in the Bootstrap documentation.

Notes for team

  • No need to copy/paste files or folders, the CSS and JS import links are now up to date!
  • Remember: sync git, make changes, sync git
  • The Bootstrap 4 documentation has lots of great info, start with Layout, Content, Components
  • Bootstrap also has a slack channel - a great place to go for help!


Week 8: Prep for Part B

Our team met this week to discuss the division of tasks ahead of Part B being due next week.  Part of my task list was having a look at the header again and styling.  We decided as a group not to pursue web components at this time.  There are some cross-browser issues and ultimately it came down to time available vs core functionality we need to do first.  Web components hasn't been ruled out, just put in the 'nice to have' basket.

Part of the feedback we got from the paper prototype we tested last week was to make all our header/nav the same across all pages.  While updating the header (and taking it out of its own HTML import), I had a look at the bootstrap framework we were using  the material design theme.  I decided to ditch the theme in an effort to make the design more our own and instead build on vanilla Bootstrap.

I had a look into the newly released Bootstrap 4 and thought this would be a good option, but it is only available as source files (not pre-compiled code), which means setting up SASS for our project.

Today in our workshop I went through how to set-up SASS with my team and how to edit and compile.  In my next post I will document the how-tos for our team to refer back to if necessary.

I also wrote a set of success criteria for our Part B report based on the interactions we want our users to have with our web app.  We will discuss these as a group next week.

Tuesday, 8 September 2015

Week 7: Experiences with paper prototype

For the paper prototype this week, we split our group into two groups.  Two people (Felix and Rena) conducted the paper prototype session with classmates (results posted on our blog) and Lyndon and I tested the paper prototypes for the other groups.

Our paper-prototype

We had paper mock-ups of all the main screens in our app, including pop-ups, and a list of tasks we wanted users to complete.  These tasks were designed to test navigation, whether the path needed to complete tasks was clear, and whether the layout of individual elements of complex pages (e.g. the working panel) had a logical layout that made sense to users.

Other groups

It was interesting to see how the other concepts were progressing, but more interesting to observe other prototyping practice and procedure.

A great example was pinboards.  They used a digital version of the paper prototype - it had the same level of interactivity as the paper version but was able to record user's inputs digitally.  Their session was reminiscent of the Digital Prototyping subject many of us are also doing this semester.  They had clear objectives of what they wanted to test (i.e. what questions is the prototype trying to answer) and followed up with a user questionnaire to help quantify and record their results.  They also took the session seriously, they used a script and addressed testers as potential users rather than classmates (i.e. more formally).

There were elements of concepts from some of the other groups that I really struggled understanding, but that is part fo the process of testing, helping to clarify concepts and how users will interact with the project.

Even though I didn't run the paper prototyping session for our group, it was still a worthwhile experience to act as a user for other groups.

Sunday, 6 September 2015

Week 6: Experiences in the Poster & Pitch

Concept, project and design process  

Documentation

Writing up part A document was fairly similar to project documentation I have written for projects at work.  While it seems like a lot of writing and a lot of work, it is an important skill with workplace application.  It is also important because it clarifies a lot of the detail of our project and outlines our plan for how we will turn our concept into an application.

Design thinking

Design thinking last semester taught us a lot of different processes and design techniques.  They were all clearly prescribed and written into our assessment criteria.  The criteria for this project doesn't have the same level of detail and I found myself thinking back to those pieces of assessment as a guideline.  I imagine my design thinking toolbox will get easier to remember the more I use it.

The brief

Student briefs are generally comprised of two elements, the 'client' needs and the assessment needs. One of the problems we have already come across (as detailed in a previous post) is which APIs we will need to use to complete the project.  The 'client' needs is to highlight an area of Trove, the assessment needs is to learn how to use API calls (in particular the Trove API).  It was good to find out that there was a little room to move so that the 'client' need still came first.

Feedback

I did a quick write-up of the feedback we received from our Part A presentation on our team blog. We also went over the feedback in more detail in our Part A document.  The piece of feedback that stood out most to me was around help.  Our intention for our concept was never to provide training but for it to be a tool students could use to practice html skills and in the process learn about web standards and practice validation.  It hadn't occurred to me to provide help information or how our users would go about getting help if they were stuck.  There were many suggestions from class including a discussion board, chat or links.

I recently did the AngularJS track in Codeacademy and really liked the way they did help.  One problem with chat (and other types of help) is that it requires staffing or moderation.  The way codeacademy approach is to leverage existing methods of getting code help and incorporating it in context (i.e. where the student needs it). Here are some screen shots.







Even though they use other services to provide the help, they still guide the user there with questions. This is a much better approach than just providing links or a discussion board.  While we can put together information on tags and tag depreciation to get users started, if they are looking for more in-depth help, Stack Overflow would be the best source for this.  The other benefit of this is familiarising users with standard help channels for code that they can use in future for other coding problems.


Other teams

Seeing other teams progress was good inspiration.  It was interesting to see how they had divided the team responsibilities and how technical their projects will be.  I know there will be quite a lot of learning ahead of me to be able to complete the project but I found it encouraging listening to other teams proposals and how they are approaching the different components.  The other concepts were also interesting to see, especially the shipwreck one (Atlantis).  Early Australian shipwrecks was the individual concept I presented and I'm really interested to see how another team will pursue and change the idea. Seeing it progress to a more complete interface from the wireframes I presented was great.

My process

Completing the part A presentation and documentation has reiterated to me the importance of planning in design thinking techniques to a project.  It would be easy to plan a project considering only the end product and the technical needs (i.e. how am I going to make this).  But it is important to plan in time for research, testing and feedback.  I know that there are a lot of design resources (like the d.school) but I also think it might be good for me to keep a record of the different techniques I've used to add to as I progress.

Wednesday, 26 August 2015

Week 5: Trove API limitations

We met today (meeting minutes to follow) to refine our concept and discuss our research so far.

There is an initial problem that we are currently working through regarding the brief requirement of using the Trove API.  During our research we discovered that the trove API does not provide access to the websites listed on the trove website.  We can however, use the Wayback Time-machine API (that Trove refers to) to get this information.

A closer read of what the Trove API can and can't access says:
"Search Trove newspaper articles, lists and works. (Works are made up of “versions”. They can be books, images, maps, music, sound, video, archives, journal articles…) Archived websites, people and organisations have not been included at this point."

We also looked at the search function of the API, and the 'search all' does not include archived websites:
"Search across the records in Trove. The same records you search from the Trove homepage, excluding archived websites, people and organisations."

We are in the process of discussing solutions with our tutors and course coordinator and have contact Trove to see if there is any support or workarounds for accessing archived websites.

Our current suggested fix is to organise the websites accessed via categories (e.g. sport, arts, education, government...) and to illustrate the categories (background, button?) with trove images (related to the category but not the actual websites) which are pulled using the trove API.

We would still need to use the Wayback Time-machine API to get the website details to validate but at least we are not by passing Trove altogether.

One of the risks we discussed today was having to make design decisions based solely on checking off a box in the brief and not on what would make the best product that suits our user needs.  While for the most part these two considerations are not opposites and inform decisions in consort, we are hoping that this problem is not the case of the former.

The core part of the brief that we are answering is to:
"highlight, reveal, [or] focus the content available through Trove ... something that goes beyond the simple search paradigm that they currently have and that sheds light on rarely visited corners of Trove."

We believe our concept definitely does that.  Stay tuned for more concept updates.

UPDATE: The course coordinator emailed back straight away with an OK to go ahead with our proposed suggestions.  We also chatted more with our tutor at the workshop and with the course coordinator after Friday's lecture.

(Originally posted on our team blog: Restoring the web)

Saturday, 22 August 2015

Week 4: Forming Teams

After presenting our concepts, everyone voted on their top 3 preferences for concept/group.  During the following workshop session, we finalised our groups.  Even though my Shipwreck concept received enough votes, I chose to work on another concept:  Restoring the web.  I really liked the problem that it solved.  I will be going into more detail in the near future as our team refines the concept, but here is a brief overview:

Project Description

Restoring the Web is a web-based learning environment aimed at teaching high school students basic web design skills.


Week 3: Teamwork

Teamwork reflections after completing the teamwork module http://teamworkinaction.ceit.uq.edu.au

While there were a few good points, most of it seemed like common sense.  It was good to be reminded of teamwork best practice before beginning teamwork though.  And as also, open and clear communication is the key to interacting successfully with fellow humans.

Major Concerns & how to avoid them

At the outset I don't have many specific concerns about our group.  We put together our team charter quite quickly and agreed on how we would communicate, what behaviour is expected and how we will handle group conflict.

The main concern I have about any group work (at least in the student context) is people not pulling their weight.  I expect people to say what they mean and mean what they say (and expect the same of myself).  If you think there might be a problem when we're assigning tasks, speak up, if something comes up and you might not be able to complete in time (and it does for everyone at some point or another), speak up.  One way to help that is to ask the question at group meetings (is everyone OK with their tasks, is it too much, too little) and make sure we are checking in with each other regularly.

The other concern I have (which reflects my previous experience) is the inclination of the team leader/coordinator to take charge and how that affects group dynamics.  In previous group work, sometimes the person leading the discussions appears to have more ownership of the concept which can stall group progress if that person misses a meeting.  One way to avoid this is to share the responsibility of leading group meeting and minute taking.

How you think you can be a good team member?

Good communication, practice what I preach (say what you mean and mean what you say), and encourage other to speak up.