Project Page: http://drupal.org/sandbox/nguerrero/2385135
Git Link: git clone --branch 7.x-1.x http://git.drupal.org/sandbox/nguerrero/2385135.git
Demo: http://simplytest.me/project/2385135/7.x-1.x

Manual reviews of other projects

Da Vinci

Da Vinci is a theme that has been developed for Drupal 7 with the guidelines of big developers and having like reference 5 points in 1: Separation is Power.

Sass Core

Gemas

Da Vinci is made-up for the following gems, included in the Gemfile.

Looking at our gems, is important to remember the installation and the use of Susy 2.

The other gems will serve us for can realize our work in a faster and obviously comfortable way.

Susy

Susy isn’t a grid system. Susy is a “Grid Framework”. We can not just have one main grid but we

The choice of Susy has been mostly for be a tool for the use of grids. We can not have just a main grid, but can nest between them and also realize our maths, for example, for have different sizes columns, isolate elements, etc.

For the other hand, Susy allow us, liberate of classes like “col-lg-8” inside our HTML.

By not depend on them, our HTML will be cleaner, clear, and we shouldn’t realize too many changes in our templates in the case of want readjust the measures of some element.

More about Susy: http://susy.oddbird.net/

Sass 3

From the 3.3.0 version, Sass give us new functionalities without the need of FireSass or any type of plugin.

For this can work, we need add the following line to our config.rb:

And furthermore, activate the ‘source maps’ in Chrome, log in through Settings > Source in our web inspector.

Settings del Inspector Web (Chrome)

More about Sass: http://sass-lang.com/

Bourbon

Bourbon is another Sass library with its own grid, components and base styles.

For the grid part and like advantage about Bootstrap, its components don’t generate only the CSS when are used; if we don’t call them, we don’t generate any code. This improve our cleanup and performance avoiding have code that we don’t use for the moment. In Bootstrap the components code should be always include, being used or not.

This make that can be easier the use of its components, avoiding have to be including files depending of its use.

More about Bourbon: http://bourbon.io/

Compass

Compass, our Sass library par excellence. In this library there are tons of mixins that can be useful in the diary use. Furthermore, we can use for compile our Sass files in CSS.

More about Compass: http://compass-style.org/

Sassy Buttons

Da Vinci has her own mixins for buttons and Bourbon also includes mixins for realize buttons.

Then,
Why we use Sassy buttons?

Its use is very easy, only generate the CSS of the button if we make a call to the button with “sassy buttons”.

Can be a lot of useful if we want give to our designer some guidelines for create a new button. Or if a backend without previous knowledges of CSS wants to create his own, because exist various formats like reference that can apply with a single line of code and its modification is as easy as possible.

More about Sassy buttons: http://jaredhardy.com/sassy-buttons/

Good practice

For the creation of this subject have followed a set of guidelines, which set below:

The order of folders: Such generic, and Sass own. It is very intuitive for find a particular file by given names.

Ordered and clean code: When we divide our files by category (and using Sass), each file has less lines of code, also avoiding the repetition of classes and styles.

Templates without classes like “col-sm-3”: this point can nested inside “Ordered and clean code”, because this type of classes dirty our HTML.

Documentation: All the folders have a README.txt where we can find information about the type of files that are placed in this directory, and the use of the same. Also, you can find some help, for if you need to write your own code.

Use of Sass in a standard and full way.

Region for content over the sidebar: with our “Preface” region, we can add content over the sidebars.

Performance and accessibility

It is set for won’t generate too much CSS, that can be unnecessary.

By default, and having care with our modifications, Da Vinci is an accessible theme, a quality some complex for a base theme.

Module Extra tools

Styleguide + Styleguide Palette
Jquery
modules extra

Comments

nesta_’s picture

Assigned: nesta_ » Unassigned
Issue summary: View changes
StatusFileSize
new159.49 KB
new219.21 KB
nesta_’s picture

Status: Needs work » Needs review
nesta_’s picture

StatusFileSize
new49.63 KB
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
PA robot’s picture

Status: Needs review » Needs work

There are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxnguerrero2385135git

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

nesta_’s picture

Status: Needs work » Needs review

Fix error :)

nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nileshlohar’s picture

Status: Needs review » Needs work

Automated Review

Solve the issues at: http://pareview.sh/pareview/httpgitdrupalorgsandboxnguerrero2385135git

Manual Review

Individual user account
Yes: Follows
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows mthe guidelines for 3rd party assets/code.
README.txt/README.md
No: Does not follow the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
Looking Okay
nesta_’s picture

Status: Needs work » Needs review

Thank thanks mate, I've solved the Readme format. :)

I'll put it back in I'll need review and solving the warnings so they are at 80 all :)

Thank you very much, I will review your module as soon as I can! thanks you!

nesta_’s picture

Issue tags: +PAreview: review bonus
dimple_chandra’s picture

Hi nguerrero,

Firstly good job, i reviewed your theme and following were my findings:
1) The node edit menu overlaps the right side bar when there are lot of links.

2) The footer overlaps the page content after a certain limit.

3) In the Right side bar, blocks are not having enough space between them.

4) The main menu is little shaky on click.

klausi’s picture

Status: Needs review » Needs work
StatusFileSize
new15.58 KB

Review of the 7.x-1.x branch (commit 45cb252):

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.

manual review:

  1. there is a git branch "7.0" which should be deleted to avoid confusion.
  2. da_vinci_status_messages(): this is a theme override, so doc block should be "Implements theme_status_messages().". Same for da_vinci_breadcrumb() and others.
  3. da_vinci_page_alter(): since you are not altering the page but only adding stuff you should use hook_page_build(), right?
  4. da_vinci_preprocess_html(): using arg() here seems wrong - why do you add page specific classes to the html template? Shouldn't that be the page template?
  5. js/plugins: appears to be 3rd party code. 3rd party code is not generally allowed on Drupal.org and should be deleted. This policy is described in the getting involved handbook. It also appears in the terms and conditions you agreed to when you signed up for Git access, which you may want to re-read, to be sure you're not violating other terms. The Libraries API module is a recommended method for adding 3rd party dependencies without directly including the code on Drupal.org.

The inclusion of the third party libraries is a blocker right now.

nesta_’s picture

dimple_chandra Everything is solved :) Thanks for the review.

Fixed footer with a method of compass that keeps always the footer down even when the page has no content.

The sidebar and tabs have been solved.

Everything is uploaded.

Klausi, an honor and pleasure, I deleted the branch 7.0 and continue solving the points you mention again will pass validation code and once done what I'll need to review :)

Thank you very much to all! has been much time and work and it is short :)

Thank You!

manjit.singh’s picture

Not able to do a git clone :( Is that the git clone link http://git.drupal.org/sandbox/nguerrero/2385135.git ?

It gives a error "unable to access".

nesta_’s picture

Issue summary: View changes
nesta_’s picture

nesta_’s picture

Status: Needs work » Needs review

Klausi hello!

I have solved all the points.
The only problem is that I could not change my alter by hook_page_build ().

The rest have solved everything and again last Coder and 0 errors :)

Thank you very much for the advice and come back to it in need review :)

Thank You!

klausi’s picture

Issue summary: View changes

Removed reviews that did not review the source code.

klausi’s picture

Assigned: Unassigned » sreynen
Status: Needs review » Reviewed & tested by the community
Issue tags: -PAreview: review bonus
StatusFileSize
new8.63 KB

Review of the 7.x-1.x branch (commit 9d07ab4):

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.

manual review:

  • custom.js: @file comment is confusing. What custom output? What does the function do?

But otherwise looks good to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.

Assigning to sreynen as he might have time to take a final look at this.

nesta_’s picture

Klausi, code reviews performed various, but you may not 3 code did, anyway I put some time and reviewed multiple happy :)

I moved the Custom.js da-vinci.js, I added more comments and I changed the opening sentence, if it was a little confusing.

In turn, I created a Custom.js with whipped function and renamed context for a new user can use it.

In the .info I added this js with; and this will be much more usable :)

Thank you very much friend!

nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue summary: View changes
nesta_’s picture

Issue tags: +PAreview: review bonus

Add tag bonus, new code's review in other applications and comments.

Thnx! :)

manjit.singh’s picture

StatusFileSize
new101.61 KB
new46.4 KB
new90.15 KB
new135.27 KB
new110.72 KB

Hi nguerrero, Thanks for the contribution. I have done some manual testing and found some bugs. Please check screenshots for reference.

  • Comments section seems like breaking.
  • Site footer is wrongly positioned, Please check screenshots.
  • Messages are fixed positioned, Please remove that.
  • Sidebar content disappear due to footer position.
manjit.singh’s picture

Status: Reviewed & tested by the community » Needs work
nesta_’s picture

Uhm, thnx @Manjit.Singh I go to Fix your comments.

Thnx for review.

nesta_’s picture

Issue summary: View changes
klausi’s picture

Status: Needs work » Reviewed & tested by the community

@Manjit.Singh: Those look like minor bugs but surely not application blockers, anything else that you found or should this stay RTBC?

nesta_’s picture

@Manjit.Singh a question. Have enabled jquery ?. The Footer requires Jquery, it may look bad for not being activated.

Anyway I will add this check. But I would like you to confirm me you had disabled Jquery.
Thank You!

nesta_’s picture

@Manjit.Singh & @Klausi. I add this task and bug to Issues in Projects

https://www.drupal.org/project/issues/2385135

Thnx friends! :)

manjit.singh’s picture

@klausi Yeah There is no application blockers i found :) Stay it in RTBC.

nesta_’s picture

@Manjit.Singh fix 95% issues :)

https://www.drupal.org/project/issues/2385135

Thnx!

klausi’s picture

Assigned: sreynen » Unassigned
Status: Reviewed & tested by the community » Fixed

No other objections for more than a week, so ...

Thanks for your contribution, nguerrero!

I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.

Here are some recommended readings to help with excellent maintainership:

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks to the dedicated reviewer(s) as well.

manjit.singh’s picture

Thanks for Contribution , nguerrero !!

nesta_’s picture

Thanks @Klausi, @Manjit.Singh and everything reviewer (s) of your time reviewing this project. I learned a lot from you and I will continue on this path.
It is an honor and I hope to meet you someday! :)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.