Ultimate portfolio process (part 4)
Hi, there. You're not logged in. So, you must be a visitor. Welcome!
What is this? You are viewing one of our supplemental "Stories." In addition to our core design curriculum, we are constantly building out additional resources. Stories are a collection of real work tasks, design history, UX explorations, and work-throughs. Stories are often off-the-cuff and less concerned with production value.
Introduction
Everything in this series are things we’ve gone over in detail in the course. But we’re learning a lot! So, you might have missed a few “Ah ha!” moments. Hopefully, this can solidify the concepts through all of the various stages – now that you have more perspective.
Let’s break it down…
We suggest you take notes about the thought process. Does this all make sense? and write down any of your questions so you can clear anything up – that doesn’t.
Part 32
Getting the home page moved to JSON.
Part 33
Get the basic pages moved to JSON.
Part 34
Allowing pages to assign their templates via a key in their data. Standard pages and allowing for custom pages?
Part 35
Setting all pages to fall back to a default page template and opt-in to custom templates.
Part 36
Getting the custom templates in place for the resume and goals pages.
Part 37
Hooking up the dynamic project detail links and route.
Part 38
Get module detail page structure in place and put a link to the module detail pages only on the style guide page modules.
Part 39
Functions to add page and template specific classes to the body.
part-40
Different styles for different pages and the power of custom properties. Creating Github Repo.
Part 41
Connecting local and cloud repositories. Putting the files up on a server with FTP.
Part 42
Exercises for Programmers list and detail pages.
Part 43
Responsive layout garden basics.
Did you watch all the videos?
Rad. So, what are you going to do next?
There are some big issues to consider that Derek didn’t go over
What do you think those might be? What are some other patterns we could use? We might just have more to talk through. How do bigger frameworks like Laravel do things? What would a Sr. dev vetting you for an interview process think of this code?