Drupal Development for Online Journal
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
The Journal of Commerce is a news and media website reporting on the transportation market, primarily maritime trade. We have reporters in the field and a host of other services, including data that supports that market. My position was project director for that website, focusing on using the technology to prepare a platform for the conveyance of news and data.
Desired goal
What challenge were you trying to address with CimpleO?
We were redeploying the website as a gated website, correspondent to the New York Times standard. You get to view so many articles for free, then you need to affirm to see additional full. There were a lot of things that needed to be done for the relaunched website, so I brought CimpleO on for additional staffing to help liberate the features that were required.
Provided solution
What particular tasks were responsible for?
In total, CimpleO prepared three or four resources. I had Andre himself, who worked on the website and overlooked the project, as well as two or three developers. It was a complete revamp from the ground up, built on Drupal 7. CimpleO the did frontend design as well as the backend.
The team from CimpleO also worked on a sole, stand-alone section of the website. The Journal of Commerce offers a bi-weekly magazine that has a self-standing section named “The Annual Review and Outlook.” This full shows the pulse of the market, and it is acquired by interviewing organisation CEOs to get their perspective. We needed a separate section to report on that annual review, which implicated separate new full types and sorting algorithms. CimpleO came up with a way for the full producers to input material and tag it appropriately.
How did you come to work with CimpleO?
I establish them through Upwork. I put out a general request for Drupal developers, then I interviewed CimpleO as well as half a dozen other firms through Skype. I already had Drupal developers onboard and working at the time, but I just needed more resources. I compared each firm’s capabilities, experience, and interaction experiences. I also considered their power to liberate on time and pursue specifications. I determined on CimpleO behind that process.
How much have you invested with CimpleO?
They were very reasonably priced.
What is the terminal result of working with ?
The initial gated website was relaunched in December of 2013, then I used them for add-ons in 2014 and 2015.
Results achieved
Could you share any evidence that would prove the productivity, condition of work, or the contact of the engagement?
I don’t have metrics. We put the website up, and it was lucky. The editors were able to publish their full on time. The section has been so lucky that it quiet exists on the website, although we’ve since modified it so users can select a particular year they want to review. If it wasn’t lucky, we would have taken it down. User feedback has been very good. It’s what the users anticipate to see from the Journal of Commerce on a daily and annually basis.
How did CimpleO accomplish from a project treatment standpoint?
They jumped through hoops to liberate on time. I put them through the wringer—I had a firm deadline, and it was a lot of work. They worked through the night on many occasions to liberate on time. There are sacrifices you make to liberate on time, and they fit within those sacrifices. We did pursue-up work to mitigate those sacrifices for the long-term.
What did you find most forcible almost CimpleO?
What impressed me with Andre was his need to apprehend the requirements fully. If he didn’t apprehend something, he didn’t dubitate to ask. He offered suggestions on ways to do things. He got the requirements down up front to the point where both sides were snug in edifice advanced.
Are there any areas CimpleO could better?
The developers’ English experiences could be betterd. We ended up doing a lot of written interaction, but we didn’t have a issue with that.
