Website Case Studies should offer the reader a more in depth look at how a website is created. Not just code, but more importantly, the problem, solution and story on how they got there. Some of the points we look for in a Website Case Study include:
Challenges
- Summarize the challenge faced by previous website (or lack thereof)
- State consequences of not correcting issues
- State the benefits of corrective action (monetary, efficiency, etc.)
Strategy
- Summarize the project objective
- Who was involved in planning in both the organization and developer team?
- How were decisions made about what solutions / extensions / services were needed?
- How were particular solutions / extensions / services compared and chosen?
Implementation
- What extensions / services were chosen
- What factors influenced that decision
- Timeframe involved
Lessons Learned
- What was the effect on personnel, workloads, process flow, financials, etc.?
- In hindsight, would a different solution have worked any better or would you have done anything differently?
- Did the solution produce the expected outcome?
- Recommendations for your peers based on the outcome of this case study.
Support files
- At least 2-3 Screenshots including Homepage + 1-3 Sub Pages
- if available: charts, statistics, etc.
If you would like to write an article for the Website Case Study Topic, keep the above information in mind when assessing the Joomla! based website you want to feature. If you know of a great Joomla! website but don't have the time or resources to create an article yourself, you are welcome to contact the editorial staff here at JCM by email at This e-mail address is being protected from spambots. You need JavaScript enabled to view it with as much information as possible about the site.
Social sharing is caring ;)
