Case study url:https://www.drupal.org/node/2507013

The site is live, well-maintained (no broken images, error messages etc.) and has up-to-date content.
Our site is live and well maintained. Drupal core and modules all up to date, and content (blog) is being updated regularly.

The site has a custom theme (can be built off a base theme) and is visually appealing.
The theme is extended from the Bootstrap theme, but designed in-house.

It's an outstanding example of a Drupal site. This means it's pushed the boundaries of performance, design, interaction, customization, or third-party integration.
We have build the site to be extremely fast, secure, interactive and with many custom modules. We believe this is a good example of an excellent Drupal site.

The case study includes a detailed write-up of the project and follows the guidelines above.
I believe I followed all guidelines and it's properly written. Let us know if we need to change anything.

Ideally, the project has contributed back to the Drupal community/project in some way.
We have contributed back by submitting the Pipedrive module, which is currently pending approval https://www.drupal.org/node/2496179.

The site is a positive example for business owners, site builders and developers to learn from.
We believe the case study has a good mix of examples and learning opportunities for both business owners, designers, and developers.

The site is running a currently supported version of Drupal.
The site and all modules are up to date (Drupal 7.x)

Comments

leighcan’s picture

Status: Active » Needs review

Hi there,

I'll be going through the case study issue queue within the next two weeks or so. You can expect feedback from me then.

Thanks for your patience!

-Leigh

Steven Monetti’s picture

Thank you!

leighcan’s picture

Status: Needs review » Needs work

Hi there,

There's some grammar and structure stuff that's a little wacky. If you could have someone on your internal team edit for technical correctness, that would be great.

In terms of content, we're in pretty good shape, though there are a few other changes I'd like to see. For one, I like it when case studies have a structure that runs along the lines of Problem, Solution, Results. The problem lays out why you needed to upgrade your site (poor page load time, not responsive, etc); the Solution discusses what was implemented and how (emphasis on why Drupal was the tool for the job; and the Results section is your show-don't-tell section where the efficacy of the solution is displayed. This could be increased conversions, quicker page load time, happier content editors, reduced overhead... whatever it was that Drupal made better.

The Problem section is ok -- you've got that list of 5 things you needed, which works out well enough. The Solution you've got is pretty great, and gives us a good idea of what you did and why, though personally I think you could expand each of those paragraphs even further. However, I don't see anything about results. You built this excellent site, so let's show off all the ways that it helps you succeed.

Please let me know once you've added results information. I'd prefer not to make grammatical and technical changes myself, but if you don't have someone in-house who can do it, I'll take it on. Just let me know.

Steven Monetti’s picture

Thank you @leighc! I'll have it reviewed by my editor and elaborate more on the sections you mentioned. We'll keep you posted.

leighcan’s picture

Status: Needs work » Closed (won't fix)

Hi there,

I'm going to go ahead and close this issue due to inactivity. Feel free to reopen it once you've made the suggested changes to the case study.

Best,
Leigh