I would like to ask you to consider promoting our case study (BRIXS Group - An SEO Perspective) to the Featured section.
For this project marketing and technical analyses were made and taken as guidelines for the design and realization of this website.
Being Drupal fans ourselves we decided to write a case study about the project. We feel many people are struggling with the same issues (small site, SEO, SERP and schema.org) and therefor could benefit a lot from the information provided. Even though not every little line of code was described, we did provide links to all sources needed to understand/implement the technologies mentioned and get a good grasp of what needs to be done to make a small business site have a serious chance to do well in search engines.
I hope you come to the same conclusion and therefor promote it to the featured section.
If you have any suggestions/remarks about the case study we are more than happy to listen to them and possible implement them.
As for the title of this issue. When writing/posting the case study and the issue, we overlooked the guidelines for the title and wrote a descriptive title. The case study already has been altered to comply with the guidelines, but there doesn't seem any way available to change the title of this issue. Apologies for the mix up.
with regards,
Jvon3L
PS.
This or next week we'll share a commit that we are preparing for this site. Namely the views 404 port for Drupal 7. It needs to be tested over the next couple of days first though, before we release it.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | brixs-suggestions-3.txt | 3.35 KB | Tezza |
| #4 | brixs-suggestions-2.txt | 2.57 KB | Tezza |
| #2 | brixs-suggestions-1.txt | 2.72 KB | Tezza |
Comments
Comment #0.0
Jvon3L commentedgrammer error fixed.
Comment #0.1
Jvon3L commentedadded some information about an upcoming commit.
Comment #0.2
Jvon3L commentedChange of case study title to confirm with the guidelines.
Comment #0.3
Jvon3L commentedGrammar edit.
Comment #0.4
Jvon3L commentedGrammar edit.
Comment #0.5
Zaka commentedText edit.
Comment #0.6
Zaka commentedAdded some text.
Comment #0.7
Zaka commentedGrammar edit.
Comment #0.8
Zaka commentedText edit.
Comment #0.9
Zaka commentedGrammar edit.
Comment #1
Tezza commentedThat's a very sleek website. My only 'question', really, is the large (and heavy - 100 KB+) image on the homepage. The image(s) do look better than the average stock image, it has to be said, but take up a lot of real estate and push some of the important content below the fold, so to speak. Just wondering what the thought is behind that?
Regardless of the above, +1 from me.
Non-responsive but looks good on my tablet.
Case study contains some great content but needs some grammatical tweaking. I'll work on this through the week and feed back.
Has the PS been resolved (Views 404 port)?
Comment #2
Tezza commentedOk, I've carefully read the case study and have attached something of a rewrite of the first few sections. More will follow.
I struggled to make sense of one or two sentences but I'm hopeful that my attempt will iron out a few creases. Please let me know if I have failed to convey the intended information accurately.
Comment #3
Jvon3L commentedFirst of,
The main image
I agree it takes up a lot of space but that actually has been done for 2 reasons:
For the rest
What has been realized 'till thus far is only fase one of this website. There's already a wish list of 6-7 new custom modules to be made but due to initial budget size we first had to realize a website that generates traffic, business and income before we could continue on to fase 2. Over the next couple of weeks it will become clear what new budget will become available for development and marketing and will we know what more can be done. Though the module mentioned above is first on the wish list and will definitively be realized soon.
The lack of a responsive lay-out (and of a mobile version) also falls under the wish list. It was let go for now due to the same budget reasons but will come in future updates.
As for your grammatical tweaking
All help is very much appreciated. Neither of us is a native English speaker so I'm sure that just about anything you propose will be better than what we can come up with. ;-)
Seriously though, in my opinion the changes you submitted gave it the grammatical "oomph" the case study needed, so I've directly implemented them and am looking forward to the rest of your input.
As for the view 404 port, we've got it running on our server but due to some obscure reasons we haven't been able to port/contribute it successfully. Help is underway though so I'm sure over the next couple of days it will be there.
Comment #4
Tezza commentedThanks for the comprehensive reply. Interesting stuff.
I've attached some further edits. Again, please check them over thoroughly to ensure I'm not misrepresenting your original copy in any way.
I wonder if you might want to add XHTML+RDFa to the top section of Applied methodologies? Or do you think that might conflict with your later argument of using Schema.org markup? I checked your source code - very clean. No way would Drupal spit that out without a lot of effort :) There's no RDFa markup that I could see.
When I get to the section 'what's been left out' I may add a line or two from your previous comment about phase II and responsive. I think that would benefit the reader despite the focus on SEO.
I haven't gone over my corrections/suggestions with a fine-tooth comb so if you spot the odd typo rest assured I'll review the whole thing when it's complete, including the Applied methodologies section which I have skipped over for now.
More to follow.
Comment #5
Jvon3L commentedAgain you've been able to get to the heart of what we tried to say yet in fewer and stronger words. So, besides 1 or 2 puny tweaks, al of your edits have been implemented.
XHTML+RDFa to the top section of Applied methodologies
Preferably not. For this website we left the doctype default, as it comes with a fresh Drupal installation, for no other purpose than to resolve some conflicts with the og# scheme. If this scheme would have been left out it would have sufficed to use XHTML strict. There really is no deeper intention for the rest.
add a line or two from your previous comment
Feel absolutely free to do so.
Out of self protection we left that kind of information out, not because it isn't interesting but if you get us to started about all kinds issues like usability, scalability, design, etc, etc, you'll end up rewriting a bible's worth of info...
And thanks for noticing te stripped HTML. Finally somebody who appreciates it.
Comment #6
Jvon3L commentedAnd one more thing,
As for the responsive version, we're still having internal discussions about implementing it or not. I for one think it isn't needed because of the fact that just about any device/tablet that is coming out on the market will have a retina/HD screen. This implies resolution won't be an issue in the near future.
Besides that, responsive websites only rescale and re-align the content, but unless you use AJAX loading (which is SEO russian roulette), it doesn't lower the download size. Actually, it only increases the size due to extra JS and CSS needed. Which in consequence produces extra load-time, which is a disadvantage for SEO reasons.
On the other hand I do believe very much in mobile versions of websites as they do cut down the download size and only offer you the most important information.
But that's a side note because it's my personal opinion and I know enough developers who disagree with me, even within our own dev. team.
Comment #7
Tezza commentedOf course, with html.php overridden so often I didn't even consider the default in modules/system, even though you mentioned it. D'oh!
I have no doubt many others would appreciate the stripped-back markup. I tapped my monitor thinking it was faulty! I did notice a few empty block-related divs, but I'm guessing these might have been a minor sacrifice for cross-browser design and layout, which, if is the case, I wholeheartedly approve of.
I'm wondering if the Case Study title might be better as something like:
BRIXS Group - An SEO Perspective, or
BRIXS Group - Flexible in work - SEO, or
BRIXS Group - The Case for SEO
If you're open to the idea I'd prefer the first, or maybe you have an idea yourself.
I'll likely finish the run through on Friday.
Just read #6 - As you say, debatable, but the pros and cons that you've laid out would make good content for the case study, if framed correctly.
Comment #8
Jvon3L commentedAs for the empty div's you mentioned. You are spot on. Those are there for design and lay-out purposes, although I can't promise maybe 1 or two in the entire site were overlooked. But than again, 99,9% of all unnecessary HTML elements have been cleaned out of the templates so that final 0,1% we can live with and will be stripped if we ever encounter them.
A case study title as "BRIXS Group - An SEO Perspective" would have our preference as well. It is a more accurate descriptive title and will help people searching for this type of info since the title would contain relevant keywords. But that's something only you moderators can decide since that would imply deviating from the case study guidelines (at least, that's how we understand them). If we get an OK for this I'll happily change it.
Last but not least, you mention the possibility of including my remarks about responsive design.
If you can be so creative as to include them, I'm fine with it as long as it is clear that some parts of my earlier comments are just a point of view of 1 of the developers and that not everything is fact based. I don't want to add misleading information.
Comment #9
kwseldman commentedI have a question: When do you think phase 2 of the site will be completed? And would it be a better idea to hold off on promoting this site to Featured until phase 2 is complete? Or would it still be a good Featured case study as it is right now?
The site looks good. The case study does need a lot more grammatical tweaking. I'd be happy to give it a look over once Tezza has finished his rewrite.
Comment #10
Tezza commentedThanks Kate, that would be appreciated. I'll give you the heads up when I'm done.
Fair question about phase 2. As the case study intentionally focuses on SEO, my personal opinion is 'publish and be damned' (love that quote, even if it's not entirely appropriate here!). Additional info revealed in this issue queue, which I will carefully transfer to the case study, does, I think, give the case study a sense of completeness, even with works outstanding. Just my two cents :)
Comment #11
Jvon3L commentedWhen will phase 2 be complete? Honestly I have no idea. The phase 1 build/release of this website was supposed to be sufficient for 2012. Yet things are moving so fast (in Search engine results and website visits) that, only last wednesday, the entire idea of waiting for next year for updates has been thrown out the window and brought forward to 2012. How much there will be implemented/realized and when exactly has to be determined still since a budget and timeline have yet to be set. Any exact dates mentioned by me right now would be pure speculation.
As for the relevance of phase 2 for this case study, it will only add elements to the site for usability purposes and not SEO. So it will fall outside the scope of this case study. (not saying it wouldn't be interesting reading).
Looking at both your comments I am starting to wonder though if it could be an idea that once phase 2 has been realized, we write a new case study about SEM (search engine marketing) & usability. This could cover lay-out, design, compatibility as well as giving insight into parts of the marketing strategy. What are your thoughts on that? Would it be allright to write a second case study covering the same site only with a different scope?
Comment #12
Tezza commentedA second case study with a different focus would be acceptable, imho.
You could, anyway, upload a second one to the community showcase. If you then think it meets the criteria for promotion, submit the request and we'll review it on its merits.
Comment #13
Tezza commentedOk, the third and final section re-write is in. Just to say again, please check it thoroughly for accuracy.
In the section 'What's been left out', I've included a few paras taken from the issue queue. I think they add some context and informal opinion, but I can see reasons also for not including them. It's your case study so I'll leave the final decision entirely in your own capable hands.
I'm not entirely satisfied with the overall result and I can see some places where improvements can be made, and I already have a few questions to ask. But I'll leave it a day or two and have a proper read over the weekend. I'll likely then make a few final adjustments and ask kwseldman to cast a fresh pair of eyes over it. (in fact, Kate - if you're following this, you can wait until my final pass or please feel free to chip in any time after these latest edits have been applied).
I think "BRIXS Group - An SEO Perspective" is an appropriate title, for reasons given and obvious to all.
Comment #13.0
Tezza commentedText edit.
Comment #14
Zaka commentedThanks a lot - again.
I guess that because you speak English natively you still see room for improvement, because I don't see it. We would have been proud to be able to write it in such a manner. O well, we'll see what you will come up with next. :-)
If you feel more information could/should be added please tell us what you would like to see and we'll write it up or give answers to your questions.
Comment #15
Tezza commentedBefore I put it down for a day or so I just want to be sure I clearly understand your use of 'responsive' and 'mobile' in this queue. I'm reading it as 'responsive design' and (separate) mobile website. If that's correct then I might have muddied the translation a little so I've re-edited the 'what's been left out' section, and rearranged its final paragraph for a slightly better narrative.
Comment #16
Zaka commentedYou're right in reading it as a responsive design (for the actual site) which will have a separate mobile site in the near future.
I agree the case study wasn't completely clear about this with the new edits, so for now I've made some small adjustments, awaiting your input.
Comment #17
Tezza commentedGood edits
Comment #18
Tezza commentedI've re-read the case study and made a few edits. Second pair of eyes still required.
I noticed the words 'Update results' in the 'Project team' section. Does that refer to the screenshots below? if so, probably best to remove it and add a sentence to the body of the case study guiding the reader to those screenshots.
Comment #19
Jvon3L commentedI have no idea when the word 'update' was placed in the 'Project team' section but since it was out of place there, it has been removed.
Thanks again for your input and we hope the 'Second pair of eyes' will agree with what has been done so far. If not, we will keep on editing until everybody is happy.
Comment #20
Anonymous (not verified) commented+1 Great case study, lots of detail and info, looks ok to be featured. Good work!
Comment #21
lisarex commentedDoing a quick review and think that you should remove the full stop at the end of "Varnish vs. stacked cache providers."
I'm not sure about the screenshots showing the various SEO performance / metrics. Maybe someone else can weigh in here. It's difficult to understand the story they're trying to tell without some annotation or explanation. Typically we expect to see screenshots of the Drupal site here.
If you want to keep them, I would suggest cropping them so that it's clear that a) it's not part of your site and b) we can properly the relevant speed/SEO detail and also, add at least one more screenshot from your site.
Comment #22
lisarex commentedTo clarify, I was trying to perhaps create a montage of the relevant crops from the non-Drupal site screenshots? Feel free to tell me that is a dumb idea.
Comment #23
Zaka commentedHi lisarex,
Thanks for your input, but the whole case study is actually related to the SEO part combined with Drupal, which tells about how we applied a technique in order to create a webpage that results in not only fast, but also semantically correct. Most websites tries to climb the search index by purchasing a paid service. Why do you want to spent money one these services where you also can achieve these results just by developing your website SEO correctly? Another thing what we are trying to proof is that even new websites has a chance climb this ladder.
Mmm... we could put another screenshot of Brixsgroep, but since the case study is more scientific than the actual content, I am not sure what additional advantage it would bring to this case study.
Friendly regards,
Zaka
Comment #24
Tezza commentedI removed the period from the heading and added a question mark here: Schema.org isn’t part of Drupal (yet?) - unless schema.org is going to become part of core then I think the question mark is necessary to avoid any misleading inference.
I'm happy enough with the text now. It could be improved, but it reads well enough and is easy to follow.
I think lisarex's view that creating a montage from the 'performance' images to more clearly show the positive SEO results is a valid one. The graphs are reasonably clear but I can barely follow the detail in the GTmetrix, Pingdom, ShowSlow and SiteAlert screenshots.
+1 for RTBC when lisarex is happy with the detail provided by the additional screenshots.
Comment #25
Tezza commentedComment #26
Jvon3L commentedExtra images have been added and all images have been cropped as much as possible and are located under their corresponding header within the 'To measure the effects of technical SEO implementations the following test tools were used' list.
Further cropping of images isn't possible without losing relevant data.
We hope this is more to your liking.
Comment #27
Anonymous (not verified) commented+1, looks good to me, certainly something I'd point my SEO-minded friends to!
Comment #28
lisarex commentedThanks! That looks better that you've identified the screenshot with the service.
+1
Comment #29
Jvon3L commentedThanks for your input folks. Without it the case study wouldn't be the showcase it has become.
Comment #30
tvn commentedPromoted.
Comment #32
Tezza commentedComment #32.0
Tezza commentedGrammar edit.