This theme contains standards-compliant HTML5 and CSS3 to generate beautiful and accessible web pages. Features include:

  • Fully responsive pages that look great on any size screen.
  • Short, simple, and easily-extensible code.
  • Hand-crafted SVG images for background and logo.
  • Fully accessible webpages that are easy to use with assistive technologies.

Here's a link to the 7.x Sandbox project.

Full git clone command:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/pplantinga/2019173.git

Reviews
https://drupal.org/node/2015447#comment-7554537
https://drupal.org/node/2021711#comment-7554125
https://drupal.org/node/2003740#comment-7544449

CommentFileSizeAuthor
#10 tight-spacing-under-breadcrumb.png67.49 KBAnonymous (not verified)
#3 themage.png56.66 KBalinouman
screenshot.png21.64 KBpplantinga

Comments

PA robot’s picture

Status: Needs review » Needs work

Link to the project page and git clone command are missing in the issue summary, please add them.

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.

pplantinga’s picture

Issue summary: View changes

Add link to sandbox and git

pplantinga’s picture

Status: Needs work » Needs review

Added sandbox project page link and git clone command.

alinouman’s picture

StatusFileSize
new56.66 KB

Its my first review so pardon me if its wrong.Here are some points
1-Info files doesnot have regions define in it if some one have to make new region in it i think so problem will come.
2-On 320x480 your pager layout brokes.Either its drupal system pager or views pager.
Thanks

pplantinga’s picture

Thanks for the review!

I've fixed the pager layout, which was clearly broken.

You're right that not defining regions (just using the default ones) could be somewhat confusing for a new Drupal themer trying to add a region, but I think the documentation does a pretty good job of outlining what needs to be done to add a new region in the .info file. If another reviewer agrees that I should add the regions, I certainly will.

Thanks again.

bogdanru’s picture

Hi,

You should define regions in your info file. Now, if I want to add another region, I will have to define all the default ones too. Otherwise they will not appear.

Cheers.

ronfeathers’s picture

I love that you're building with accessibility in mind! Thank you for that.
One thing - the skip link in your beautiful theme doesn't have an href, so you're relying on JS. Which functionally is probably fine, but it's better to include the href, too. You can use the WebAim toolbar for Firefox to check for things like this.
http://wave.webaim.org/toolbar/
Other than that, it looks super!

~R~

alinouman’s picture

2-On 320x480 your pager layout brokes.Either its drupal system pager or views pager

I can confirm that its working fine now.
+1 for this theme.

pplantinga’s picture

You should define regions in your info file.

I've added default regions and default features for easier theme editing, as per feedback.

the skip link in your beautiful theme doesn't have an href, so you're relying on JS

The reason for the JS is that some browsers (*ahem* webkit *ahem*) don't update focus when activating a skip link, so hitting tab afterwards goes right back to the top of the page. You're right that there should be an href too. If you check again, I think you'll find one there hidden next to the JS.

Thanks, all, for your feedback.

pplantinga’s picture

Issue summary: View changes

include full git clone command

pplantinga’s picture

Issue tags: +PAreview: review bonus

Review bonus

Anonymous’s picture

StatusFileSize
new67.49 KB

Hi pplantinga! Here are some possible improvements below. Overall though nice job!

Tight spacing under breadcrumb
This is purely cosmetic but I figured I would point it out since it looked different in your project screenshot. I attached an image below but it looks like you could add some spacing below the breadcrumb for the sidebar menu. Maybe something like #page-breadcrumb { margin-bottom:16px; }

Anonymous’s picture

Status: Needs review » Needs work
pplantinga’s picture

Status: Needs work » Needs review

Good point. Fixed.

klausi’s picture

Assigned: Unassigned » cubeinspire
Status: Needs review » Reviewed & tested by the community
Issue tags: -PAreview: review bonus

Review of the 7.x-1.x branch:

  • Coder Sniffer has found some issues with your code (please check the Drupal coding standards).
    
    FILE: /home/klausi/pareview_temp/template.php
    --------------------------------------------------------------------------------
    FOUND 1 ERROR(S) AFFECTING 1 LINE(S)
    --------------------------------------------------------------------------------
     16 | ERROR | Inline comments must end in full-stops, exclamation marks, or
        |       | question marks
    --------------------------------------------------------------------------------
    

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. block.tpl.php: the aside tag might not be appropriate for the general block? A block can be in the header, footer, main content area etc. Better override the block template for the specific sidebar regions?

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

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

klausi’s picture

Trying to remove tag again.

pplantinga’s picture

I've fixed the comment that had a standards issue.

As for your other comment about putting the aside only in the sidebar, I was conflicted. While the <aside> tag has generally been used for sidebar content, its definition is vague enough that blocks in the header or footer might apply. Technically it should be evaluated on a case-by-case basis, but since we all know that isn't going to happen, I figured somewhat-semantically-correct tags might be better than divs.

I guess you're right though, if it's in the header or footer, it's already got the semantics. Also this was being applied to main content, which is technically a block so that was clearly not semantic. This is now fixed.

klausi’s picture

Status: Reviewed & tested by the community » Fixed

no objections for more than a week, so ...

Thanks for your contribution, pplantinga!

I updated your account to let you 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 get 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.

Status: Fixed » Closed (fixed)

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

Anonymous’s picture

Issue summary: View changes

Add reviews