Anthony Costanzo, LT, Boston College

2011 NFL Draft – Colts Round 1

Filed in SportsTags: Colts, Draft, Indiana, Indianapolis, NFL
Anthony Costanzo, LT, Boston College

Anthony Costanzo, LT, Boston College

With the 22nd overall pick in the 2011 NFL Draft, the Indianapolis Colts take:

Anthony Costanzo, LT, Boston College


  • HT: 6'7 / WT: 311 / 40: 5.23


After a surprising number of teams selected quarterbacks in the first round, Costanzo became the "Best Player Available'", falling to the Colts at the #22 pick. Costanzo, rated by many as one of the top 2 or 3 left tackles in this year's draft, appears ready to step into a starting role as an NFL left tackle, which would fill a glaring upgrade need for the Colts. Costanzo is clearly a value pick, and may prove to be a steal.


Draft Analysis:


    The selection of Castonzo shows that Bill Polian was serious about upgrading the protection of Peyton Manning. The Boston College star enters the league with a ton of experience and is one of the most technically sound players at the position. He gives the Colts a potential starter as a left or right tackle and some flexibility in configuring a rebuilt offensive line.

  • Yahoo Sports

    The Colts' offensive line faltered last season and made Peyton Manning's job as challenging as ever. Castonzo can plug in at left tackle and protect Manning's blind side from Day 1. He's a smart, versatile, technically sound pass protector who could stand to improve his core base strength.

  • ESPN

    What he brings: A smart, instinctive and polished player, Castonzo has the technique and maturity to step in and play right away. His lateral mobility is just average but he does a good job sinking his hips and using his hands when he can get into position. He's not a road-grader as a run blocker but does a good job getting on the edge and covering defenders to create running lanes, which works well with Indy's zone blocking scheme.

    How he fits: Offensive tackle may have been the No. 1 need and he is an excellent fit as an intelligent player in a very sophisticated offense. Even though the Colts get a lot of publicity for not giving up a lot of sacks, much of it is due to Peyton Manning's quick release and not their pass protection.

  • Fox Sports

    Castonzo could be an immediate starter and he showed a lot of versatility by playing three different offensive line positions at the Senior Bowl. This is a smart kid and the Colts definitely have an need on the offensive line.

    The Colts were very lucky to be able to select the talented Castonzo because he was projected to go off the board much earlier in the first round. He’ll be expected to start as a rookie at left tackle.

Scouting Reports

  • Draft Board Insider (Rank: #14 Overall / #3 OT)

    Castonzo is a very smart player with very good awareness and instincts. He's a very sound technical blocker and while he isn't always the most athletic or powerful guy on the field, rarely is he caught out of position or beat on a play because he didn't do his job or follow his assignment. In terms of a resume' you can't discount a guy who's a four year starter at both left and right tackle.

  • (Grade: 8.0)

    Strengths: Castonzo possesses ideal height for the tackle position and has great feet. A highly-productive and extremely durable performer with over 50 starts in his college career. Smart, tough player and a hard worker. Huge, long frame coupled with impressive mobility allows him to shut down speed rushers. Puts himself in good position while run blocking. Comfortable and productive in space.

    Weaknesses:: Must improve his bulk and playing strength (both upper and lower body). Can be beat by a strong bull rush or violent pass rushing moves. Can get caught dipping his head in pass protection. Does not push people off the line of scrimmage in the running game.

  • (Grade: 3.05 - First-Year Contributor)

    Positives: Tall, relatively athletic tackle prospect who comes with a high upside. Keeps his feet moving throughout the action, displays better than average footwork off the edge, and is effective in pass protection. Moves well about the field, easily slides out, and fights hard to finish blocks. Adjusts to defenders, blocks with good lean, and easily holds the point. Shows good quickness, stays square, and is an effective position blocker who seals opponents from the action. Turns defenders off the line run blocking and uses his long arms to push opponents from their angle of attack. Makes good use of angles, keeps his head on a swivel, and works well with teammates.

    Negatives: Just average blocking in motion. Must improve his blocking balance. Overextends into blocks, adversely affecting his ability to finish the play.

    Analysis: Castonzo has been a terrific tackle on the college level and offers the size, athleticism, and blocking fundamentals to eventually start at the next level. He should be given a chance at the all-important left tackle position before any consideration is given to moving him to the right side.

  • Mocking The Draft (Rank: #4 OT)

    Castonzo is much better as a pass blocker than run blocker at this point of his development. He can use his natural abilities – agility, quickness, length – to his advantage to wall off defenders. Does really well moving his hands in and out to knock defenders back. Possesses a wide, smooth kick slide to the outside. Castonzo is quick enough to work his power slide to stop inside rushers. Will get fooled at times by stunting defenders.

  • National Football Post (Grade: 6.9 - B - Dirty Starting Caliber)

    The size, length and natural athleticism is there, but he needs more time to mature physically. I don't think he's a guy who you can pencil in as a starter on the left side from day one, but with some time he has the skill set to eventually develop into a serviceable starting left tackle in the NFL. However, as of now, isn't an elite offensive tackle prospect by any stretch in my book.

  • Draft Countdown (Rating: 4 Stars / Projection: 1st Round)

    Strengths: Ideal size with a large frame, long arms and big hands, Very good athleticism, quickness, agility and balance, Shows relatively nimble feet to slide laterally and mirror, Displays the ability to recover and adjust in action, Effective run blocker who generates sufficient movement, Polished technician who understands positioning / angles, Able to stun with initial punch and uses hands well overall, Mobile with range to work in space and get to second level, Extraordinarily smart with great instincts and awareness, Competitive, aggressive and active with a terrific motor, Mature and a fiery leader with an outstanding work ethic, Durable with a ton of experience against top competition

    Weaknesses: Still developing in terms of weight / strength, Is not overly stout at the point of attack, Narrow base and struggles to anchor / sustain, Isn't a powerful, road grading run blocker, Can be inconsistent with knee bend / leverage, Had some trouble with elite speed off the edge

  • Fox Sports

    Scouts love his feel for the game and smarts, qualities that are no surprise since he was a Rhodes Scholar nominee as a biochemistry major. Castonzo is also considered very disciplined, perhaps from his time playing football at Fork Union Military Academy in Virginia. He rates high in athleticism, size and versatility since he can fit in well at either tackle slot. Castonzo is a solid bet to be drafted in the top 15 and could be the top offensive lineman taken.

  • FFToolbox (Rank: #19 in Top 100)

    At 6-7 and 308 pounds Castonzo certainly has the size to play in the NFL. He could have left a year early, but the extra year at Boston College saw him add quite a bit of needed weight. The pundits have already been paying close attention to Castonzo since he was on the radar last year and his year bulking up at BC should move him up into the late first round or the second round.

  • WalterFootball (Rank: #2 OT / Projection: Top 20)

    Castonzo uses finesse and technique to his advantage. His upside is in adding a few pounds and more strength. This would make him a better run blocker and more able to slow down powerful NFL rushers.

  • NFL Draft Geek (Rank: #5 OT / Tier: 2)

    He does a good job walling his defender off, blocking into the second level, and opening up holes for the back to run through. He has great height and long arms, and uses his arms well to guide his defender where he wants them to go when run blocking. His pass protection is a real cause for concern from me though, he is not very agile, he plays way too high, which allows defenders to get underneath him, and he is not very strong as of now.

Good Friday Tornado Track

St. Louis Good Friday 2011 Tornado

Filed in PersonalTags: Missouri, Saint Louis, Tornado, Weather

The St. Louis Good Friday tornado ended up being a rather close call for us. The storm track is in red; our location is in yellow:

Good Friday Tornado Track

St. Louis Good Friday Tornado, 22 April 2011

Unlike the 2010 Saint Ann tornado, this one did major damage in the area. Thankfully for us, though, the worst thing we suffered was a 12-hour power outage.

A Guide to Reviewing Themes for the WordPress Theme Repository

Filed in Web DevelopmentTags: Theme Review, Themes, tutorials, WordPress

Thanks in large part to Justin Tadlock's recent blog post, in which he solicited more people to get involved with the WordPress Theme Review Team (WPTRT), we have seen a fantastic, huge influx of new volunteers. Many of these new volunteers have had questions about how to perform a Theme review. Hopefully this guide will help answer those questions.

Getting Started

Test Environment Setup

First things first: review How to Join WPTRT.

WordPress Setup

Ensure that a few WordPress settings are modified in order to facilitate the Theme Unit Tests:

  • Settings -> General: set the Site Title to something fairly long, and set the Tagline to something even longer. These settings will facilitate testing how the Theme handles these values.
  • Settings -> Reading: set "Blog pages show at most" to 5. This setting will ensure that index/archive pagination is triggered.
  • Settings -> Discussion: enable Threaded Comments, at least 3 levels deep. This setting will facilitate testing of Theme comment list styling.
  • Settings -> Discussion: enable Break comments into pages, and set 5 comments per page. This setting will facilitate testing of Theme paginating link markup/styling.
  • Settings -> Media: ensure that no values are set for max width or height of Embedded media. This setting will facilitate testing of the Theme $content_width setting/implementation.
  • Settings -> Permalinks: ensure that a non-default permalink setting is selected, e.g. "Month and name". This setting will facilitate stepping through the Theme Unit Tests.

Next, create at least two Custom Menus:

  • Long Menu: all included Pages
  • Short Menu: a menu of 2-3 Pages

Now, you're ready to be assigned a ticket! Read on for the detailed review process.

Policy Requirements

The first area to review involves some policy requirements, rather than code quality. I verify these before I ever download or install the Theme, by reviewing the appropriate template files using the "SVN" link in the Trac ticket.


  • Review the header tags in style.css. Ensure that the License: and LicenseURI: header tags exist, that the indicated license is GPL-compatible, and that the indicated URI is a valid, full-text license.
  • Review the Theme files for bundled fonts or icon sets; if included, verify that the licenses for these bundled resources are GPL-compatible, and explicitly declared by the Theme, either in style.css, readme.txt, or somewhere similarly appropriate.
  • Review other template files, such as footer.php, to ensure that there are no inline comments regarding use restriction, such as prohibiting changing the footer, or requiring a credit link, etc.

Credit Links

  • Review the header tags in style.css. Ensure that Theme URI and Author URI, if used, are valid and appropriate.
  • Review the indicated URLs. Ensure that the sites are appropriate, that they do not sell or promote non-GPL WordPress Themes, and that any license or terms and conditions information does not include non-GPL-compatible content.
  • Review footer.php, sidebar.php, etc. and ensure that the Theme does not include any other inappropriate hard-coded links (sponsor links, SEO links, spam links, etc.). Ensure that all public-facing copyright notices indicate the site name, rather than the Theme name or developer.
  • Review functions.php and ensure that the Theme does not hook in any other inappropriate links or copyright notices.

Theme Name

  • Verify that the Theme name meets naming convention requirements.


  • Verify that screenshot.png is sized appropriately.

Theme Check

Next, install the Theme, and before activating, run Theme Check. Note any Warning or Required notices in the Trac ticket. (Note: for any Theme uploaded since late March 2011, Theme  Check should return no such notices, as they should all be caught by the Theme uploader script. If you notice any, please email the Theme-Reviewers mail list, and indicate what notices you observed.)

You are welcome to note Recommended or Info notices in the Trac ticket, but I generally don't. These notices are more for your reference, as you continue to review the Theme.

For Recommended notices regarding Theme functionality (Post Formats, Post Thumbnails, Navigation Menus, etc.), verify that the Theme does not use a custom implementation. If the Theme does use a custom implementation, note in the Trac ticket that the Theme is required to support the core implementation of the functionality.

Step through each Info notice, and review the Theme template files to determine if the notice is applicable. For example: verify appropriate use of include() vs. get_template_part(); verify appropriateness of hard-coded links; etc.

Code Quality

Now, the review enters the bulk of the requirements in the Theme Review guidelines.


Review header.php, and verify:

  • All appropriate document head guidelines (valid doctype declaration, properly formed tags (html, head, meta, etc.)
  • Feed links are not hard-coded into the document head
  • No CSS files other than style.css are hard-coded into the document head. (These files must either be enqueued and hooked in appropriately, or added using IE conditional tags.)
  • No scripts or script file links are hard-coded into the document head. (These must be enqueued and hooked in appropriately.)
  • No unnecessary meta tags (WordPress generator tag, SEO meta tags, copyright meta tags, etc.) are hard-coded into the document head.
  • The wp_head() template tag is placed immediately before the closing HTML head tag.


Review footer.php, and verify:

  • No scripts or script file links are hard-coded into the footer. (These must be enqueued and hooked in appropriately.)
  • The wp_footer() template tag is placed immediately before the closing HTML body tag.


Review functions.php, and verify:

  • All custom Theme functions, constants, classes, global variables, and options are prefixed with theme-slug (or an appropriate variant).
  • Theme Settings are implemented properly:
    • Theme options are added to the database via a single options array, rather than separately
    • Settings page added via add_theme_page() rather than add_menu_page()
    • Settings page capability is edit_theme_options, rather than admin, manage_options, edit_themes, etc.
    • All untrusted data are sanitized/validated upon input into the database, and escaped upon output
    • If the Theme is not using the Settings API:
      • Nonce-checking is performed explicitly
      • $_POST, $_GET, and $_REQUEST data are sanitized/validated upon input into the database, and escaped upon output
  • No core WordPress functions introduced prior to one previous, major WordPress release are wrapped in function_exists() conditionals.


Verify that all tags listed in the Tags: header tag are appropriate, and that all claimed functionality is included in the Theme.

Theme Template Files

Note which hierarchical template files are used (e.g. single.php, page.php, archive.php, date.php, author.php, category.php, tag.php, taxonomy.php, 404.php, home.php, front-page.php, and search.php), so that you will know which of these to verify when performing the Theme Unit Tests, later.

Review Theme template file names, and ensure that any hierarchical template file name variants (e.g. page-foo.php, category-foo.php, etc.) are included in the Theme documentation, with an explanation for their use.

File Includes

Review Theme template files, make note of any uses of include() or require() and ensure that such use is valid. Verify that:

  • All headers are included via get_header()
  • All footers are included via get_footer()
  • All comments templates are included via comments_template()
  • All sidebars are included using get_sidebar()
  • All template part files are included via get_template_part()
  • Any search form markup is included via get_search_form()
  • Any login form markup is included via wp_login_form()

Theme Unit Tests

Now the review moves on primarily to the requirements in the Theme Unit Tests.

Theme Activation Tests

  • Activate the Theme, and open the site in your browser. Verfiy that Debogger returns no PHP errors, warnings, or notices for index.php.
  • Via Dashboard -> Tools -> Deprecated Calls, verify that Log Deprecated Notices does not return any deprecated function calls or other notices.
    • Note: check the Deprecated Calls log one final time when you complete the review, after you switch back to your default Theme. Sometimes, some notices get thrown when the Theme is deactivated.
  • If the Theme includes a Custom Theme Settings:
    • Load the Settings page, and verify that Debogger returns no PHP errors, warnings, or notices.
    • Save current/default settings, and again verify that Debogger returns no PHP errors, warnings, or notices.
    • Test each Theme Option in turn, and verify that each option can be updated, that the setting is applied properly in the Theme, and that Debogger returns no PHP errors, warnings, or notices.
    • If the Theme Settings page includes a "Reset Defaults" button, reset defaults, and verify that default settings are applied, and that Debogger returns no PHP errors, warnings, or notices.
  • If the Theme supports Custom Image Headers, select a custom header, and verify that it is applied/displayed properly
  • If the Theme supports Custom Backgrounds, select a custom background image or color, and verify that it is applied/displayed properly
  • If the Theme supports Custom Nav Menus:
    • Verify that the default/fallback output renders properly
    • Apply the Short Menu to each theme_location, and verify that the menu renders properly
    • Apply the Long Menu to each theme_location, and verify that the menu renders properly, without breaking the site/menu layout
    • If the Theme has a limitation on number of list items in any theme_location, ensure that such limitation is documented in readme.txt
  • If the Theme adds Custom Widgets, verify that all custom Widgets function as intended, generate no PHP errors, are secure, etc.
  • If the Theme supports Custom Editor Style, verify that the Post editor content renders reasonably similar to the site output
  • If the Theme requires any custom settings or setup, ensure that setup instructions are documented in readme.txt

General Tests

Run the W3C HTML/CSS validator on the Readability Test post (to ensure minimal WordPress-caused validation errors), and note any egregious validation errors, such as:

  • Malformed or improperly closed tags, that cause the page layout to break
  • An exceptional number of HTML or CSS errors

View the site index page, and verify:

  • The screenshot, as seen in the Trac ticket, is a "reasonable facsimile" of the default view of the site
  • The Site Title and Tagline, if displayed, do not break the page layout

Template Page Tests

  • For all included template-hierarchy index pages (index.php, home.php, archive.php, date.php, author.php, category.php, tag.php), verify requirements, as specified.
  • If the Theme includes either a front-page.php or a home.php template file, go to Dashboard -> Settings -> Reading, and set the Front Page to display a Static Page (use any existing Page), and set the Blog Posts index to another Static Page (e.g. "Lorem Ipsum"). Verify requirements, as specified.
  • Trigger the Theme's 404.php page by navigating to a non-existent Page slug (e.g. www.domain.tld/sit-amet). Verify requirements, as specified.
  • Trigger the Theme's search.php page by performing a search (e.g. "lorem ipsum"). Verify requirements, as specified.

Blog Posts Index Page Tests

Return to the Blog Posts index page. Step through the Blog Posts Index Page tests.

Individual Unit Tests

Step through each Blog Post and Static Page, verifying all requirements, as specified. Each unit test should be fairly self-explanatory.

Finishing the Review

At this point, the review is thorough and complete. Summarize your comments in the Trac ticket and close the ticket with the appropriate resolution (or propose a suggested resolution, if you do not have appropriate rights to close the ticket).