Ruby on Rails Website Dev for Independent Newspaper
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
I’m the IT ruler for the newspaper section of Agora SA. My responsibility is to help businesses create new business standards and fruits based on subscriptions, specifically web and mobile apps.
Our IT section',s divide into two business divisions: general IT labors for the total organisation and outgrowth teams for innate business units, like business transfigureation. Together, the section develops and brings fruits to the market.
Desired goal
What challenge were you trying to address with CODEST?
We were trying to transfigure our transmitted newspaper standard into digital form and centre on selling subscriptions, not just newspapers.
Provided solution
What particular tasks were responsible for?
CODEST created a digital fruit based on our archived, printed newspapers. The digital archive has specific features aimed at helping clients find information, including a full-text search. The full is delivered through a backend and partial fronted, for show.
Their team used Ruby on Rails technology for the platform. It’s based on an API construction that delivers data from our archive. The index is based on an Apache Solr solution on the backend. Files are imported from the file method and exported to a MongoDB database.
They delivered a partial HTML design of the website, while my team granted some elements. CODEST also worked on the UX/UI based on our definitions, checking the exactness for the nation working in the backend of the materials we publish. We worked unitedly as two teams.
How did you come to work with CODEST?
CODEST is part of the same cluster as our organisation. It was a given to go to them when looking for useful resources.
What is the terminal result of working with ?
We seted working with CODEST in March 2017, and the fruit was sent to the market in October of that year. The terminal rendering launched in December 2017.
Results achieved
Are there any measureable or plum results?
After the terminal platform was implemented, we continued to make changes and bug fixes. Just recently, we asked CODEST for extensions. We bestow an mean of 20–25 hours per month on the work.
The general commission of the project was to create a channel for delivering news to subscribers. Once it artistic, we were able to monetize our archive, which wasn’t useful to us previously.
How did CODEST accomplish from a project treatment standpoint?
We worked with their team using the nimble methodology, divideting the project into two-week sprints. At the end of the sprints, their delivery time was excellent and what we expected from them.
What is (from your point of view) the key factor to pay observation while intercourse with ?
CODEST prepares a professional labor. Their access to fruit delivery worked big for our team. Any issues we identified, they fastly fixed. Overall, the results were condition for us.
What aspects of their work would you like to get improved?
When a new developer was introduced to our team, we had to expound the project information and rules. CODEST didn’t prepare all, but other than that, the rest of the collaboration went smoothly.
Do you have any advice for forthcoming clients of theirs?
It’s significant to mark the rules of the collaboration and roles of each team limb from the set. If all is pellucid in the commencement, it’ll help fruitivity.
