How to Structure your Front End Files - HTML, CSS, and More

First things first: All your user-facing files and angular files are in /client/app/

  1. app.js: defines your app and includes some basic app-wide functions, you probably don’t really need to mess with it unless you’re trying to add more dependencies to your app. We’re not gonna worry about that right now.
  2. app.css: an app-wide stylesheet, you can put styles here if you want but I’d recommend you put them in main/main.css, as these styles are also app-wide.
  3. main/: this folder contains what the user sees first when they load up your site. main.html is the page template, main.js routes the user to main.html when the user goes to the top level directory of your website–that is, http://yourapp.wherever.itis/ with no /other/url/hierarchy. You’ll also learn soon that you can define your app’s /url/heirarchy/fairly/arbitrarily. You won’t really need to edit main.js or main.controller.spec.js, so let’s not worry about those right now. If you look through the main.html file you’ll see it uses ng-repeat to show things in awesomeThings. Where does it get awesomeThings?
  4. main/main.controller.js: all of the javascript functions you want to use to interact directly with the user go here! You’ll put functions here to interact with your API, refresh views for your user, etc. Here, awesomeThings are pulled from your database and added to the local scope so your HTML view can display them! How cool! We’ll get to adding custom objects to your database in a minute.

Great! Now you know how to interact with the user! But what if you want your app to have another page that does something else? Maybe main.html shows the home page, but you want a page that shows a form to add a poll? maybe http://yourapp.wherever.itis/newpage? This is where the yeoman generator comes in handy.


1 Like