search

billiedemott / spoutlets.com

Wireframes for various projects
0 stars 0 forks source link

Clarify workflow between front and back end #87

Open deltanovember opened 12 years ago

deltanovember commented 12 years ago

Can you document how you wish the workflow to occur. Does Dmitriy work directly with .ejs? Or do you wish to do merges between HTML and EJS? If EJS, there is a slightly different directory syntax for accessing static files due to Node/Express. Basically public is made invisible e.g.

/stylesheets/bootstrap.css

not

../public/stylesheets/bootstrap.css

Will this be a problem? Should be able to use symlinks to fix

deltanovember commented 12 years ago

Another issue there is a lot of common code in the HTML that should be moved into a common header file. This is so any changes can be made once instead of seven or eight times. Is this going to affect Dmitriy things from a design perspective?

akshatpradhan commented 12 years ago
  1. D will work directly with .ejs, but you'll have to move all the HTML into their respective layouts.
  2. getting rid of public is great. In fact, using connect-assets, it would become assets/stylesheets. However, using connect-assets makes me think we don't need bootstrap.css. When I deploy this to production, we can have .css files being generated on-the-fly, so that all D has to do is work with .less files
  3. That common HTML code needs to be split into proper layouts. D can still make modifications to that.