marioricalde/ava-pattern

Arrangement for View Assets Pattern

ava-pattern's Issues

Use Cases

We need to complete the use cases; some of them are incomplete due to mexican lack of fluency with english. <3

Need convention examples for /javascripts/

Need convention examples for /javascripts/

Rename scripts to javascripts

Scripts is too general.

• DHH voted for javascripts.
• It matches Rails convention.
• It's better than js

Assumptions on Asset Manager

As of now with AVA Pattern we've been making some assumptions on the javascripts and stylesheets directories, most of them are related to the fact that to really get benefits from AVA Pattern you need to have a Asset Manager to merge files into one and to minify them accordingly.

Do you think this is bad?

Somehow I think that these assumptions are a good practice that everyone should be including on their developing environments. Having one HUGE file or multiple files invoked from the main HTML document is not a good practice.

Thoughts?

Directory Structure

Currently with the directory structure we have there's no easy way to implement "vendor" libraries, that is any third party related portion of code that needs to be included inside our project.

Lets clarify, on front-end engineering a vendor script something that you're going to use that you didn't write.

I think we can add vendor directories inside the correct sections according to what it's specified on the AVA Pattern.

• It sticks to what AVA Pattern specified.

• You're not creating extra directories, so you know where to find what you want.

• It's rails compatible.

  /stylesheets/
    libs/                     # This should be compressed into style.css
      vendor/                 # CSS Files related to a vendor library.
        package1/
      _sass-partial.scss
    style.css
    handheld.css
  /images/
    vendor/                   # Images related to a vendor library.
      package1/
  /javascripts/
    tests/
    libs/                     # Your Libraries.
      /vendor/
        package1/             # For more than one file.
    plugins.js
    script.js
  

Of course, here we're asuming you're using compass/coffeescript or something similar to sprockets to package all your js/css files into single file versions. I think we need to clarify this on the documentation; even though we're framework and language agnostic, we need to point out that many of the features AVA provides need to be coupled with a asset packager or the amount of http requests may become unberable.