In this video, Nick and Jim outline their process for designing and developing a web application.
This video doesn't have any notes.
>>Hi, I'm Jim Hoskins, >>and I'm Nick Pettit. 0:00 In this master class, Nick and I will be building a Ruby on Rails application. 0:03 Nick: By the end of this master class series, you should have a pretty good idea 0:06 of how a designer and a developer can work together to build a project. 0:10 [Master Class] [Designer and Developer Workflow] 0:15 Jim: In this project, we'll be working in sprints. 0:20 Each master class will consist of one sprint. 0:22 We'll begin with a meeting to discuss what we want to accomplish, 0:25 which is this meeting right here, and then we'll go off on our separate ways 0:28 and begin working on design and development, and we'll be communicating in between. 0:31 Then at the end, we'll have another meeting where we look back on our work 0:35 and see what worked well, what worked wrong, what we could do better, 0:38 and even start thinking about what we would want to do in our next sprint. 0:41 Nick: So Jim, what are we doing in this sprint, or this project? 0:45 Jim: Well, we'll start with a project. 0:49 We're going to be building a job board, and so we need a gimmick for our job board 0:51 because there's already so many out there. 0:54 Nick: I think we should make a job board for easy jobs, just really easy jobs 0:56 that just anybody can do like ice cream tester or movie watcher. 1:00 Not even a movie reviewer, just somebody that watches movies, that's the job. 1:05 Jim: That would be awesome, I'd definitely be down for that kind of a job board. 1:09 You can never find those. 1:11 Where do you get the job to be an ice cream tester? 1:13 All right, so for this first sprint, rather, we want to probably just get 1:16 a minimal project working, so let's start thinking about what we're going to do 1:21 in this sprint and overall what our goals are in the application. 1:24 Nick: Well, I think for this sprint, we definitely need to have a way to display jobs, 1:29 and we definitely need to have a way to post jobs. 1:34 So, we might have some sort of log in system for people to maybe sign up 1:38 and register and then log in and post a job. 1:43 And then for the other side of things, I don't think we really need a way 1:47 for people viewing the jobs to actually log in. 1:50 I think we can just have the job board, and they can just go to public internet 1:54 and check out these jobs. 1:59 Jim: Okay. So, I guess the main part of our application is the job. 2:01 So, maybe we should take a little bit of time to figure out what it's going to look like 2:06 on the front end, what a job consists of, what somebody looking for a job will see, 2:09 and maybe even what somebody posting a job will see when they go there. 2:13 So, why don't we start off with maybe just what the home page would look like 2:16 for somebody looking for a job. 2:20 Nick: Sure. So, I mean, I think the home page is just going to be a really basic list view, 2:22 like a normal Ruby on Rails list view. 2:26 Or index view, so we have our page here, and we might have maybe a little logo 2:29 up at the top for easy jobs, and then maybe we'll have 2:37 some sort of navigation or log in system. 2:41 Jim: Or we could even have search up there too. 2:44 Nick: Sure. And then, we'll just have a big list of jobs. 2:46 So, each one of these lines will just be sort of like a line listing out a job. 2:51 And then, you can click on each job, and then it will take you to sort of 2:57 a detailed view for that particular job. 3:01 So, what does a job consist of? 3:06 I mean, we're definitely going to have a title for the job at the top. 3:08 Jim: Probably a description maybe just giving some information about the job. 3:14 Nick: Yeah. 3:18 Jim: Why don't we just make it a big sort of text area right now, that way we can have 3:20 sort of more free form. 3:22 Later on maybe we can add fields like key benefits or experience needed. 3:24 We can make it pretty simple by just making it a large text field 3:29 so people can sort of free form, put whatever they want in there. 3:32 So, we'll be using Rails for this. 3:36 We use Rails 3. 3:39 Now, when we're building this, for templating, do you want to use HAML and SASS? 3:41 Nick: I think so, sure. 3:45 Jim: So, HAML and SASS are a different type of templating language that's not 3:47 the default in Rails, but it's what we're used to working with. 3:49 We've worked together on a few projects where we've used it, 3:52 and I think it's worked out pretty well. 3:54 And so for our first sprint, why don't we just work on getting the jobs sorted out. 3:57 The authentication and search functionality, I think that's all going to be later. 4:02 What we want to do now is, why don't we aim to get this list view here, 4:06 and the detail view, and work on styling those. 4:10 And I'll just go ahead and create a basic scaffold for adding information in, 4:14 and then Nick can work on the admin interface, which is logging in, 4:19 registering and posting stuff maybe in a later iteration. 4:23 Nick: That makes sense. 4:26 Jim: So, for SASS control, let's go ahead and use git. 4:28 I'll set up the git repository, and I'll send you the information for it, 4:30 and I'll generate the Rails project and I'll start working on the ,first scaffold 4:33 so you can start working on the use for that. 4:36 Nick: Sure, and then I can go ahead and be wireframing stuff 4:38 while you're building the scaffolding, and then once you have all that done, 4:41 you can pass off the views to me and I can go ahead and style them. 4:44 Jim: All right, I think that sounds like a pretty good first run, let's get to it. 4:46 Nick: Let's do it. 4:48
You need to sign up for Treehouse in order to download course files.Sign up