-- What was the decisive factor for adopting HeartCore?
We weighed several different products before we decided to switch to HeartCore. HeartCore was the one which meets our requirements and has abundant track records here and abroad. Also, they provide continuous functional enhancement and steady support, so I found it very reliable for future use as well.
Additionally in terms of SEO, HeartCore has a sitemap XML generator, which can help us to get better rankings in the search engine results. Also LPO (Landing Page Optimization) feature was one of the decisive factors.
-- Did you have any requests to Heartcore, Inc. for the implementation?
Yes we asked for some customization that are really required for our website management. It could be difficult for a general package software to address such requests, but Heartcore, Inc. gave us flexible support to meet our needs.
"We were looking for a CMS which allows local staffs to use the administration system in their own languages." (Ms. Akino)
-- How did you used to manage website contents before implementing HeartCore?
We had been using another CMS before for scheduled publishing and partial content management, but had to update pages manually by creating static content in the local environment and uploading it to the web server through FTP.
-- Why did you decide to adopt a new CMS?
It had been a long time since we had implemented the prior CMS, so we wanted to catch up with the latest technology to improve efficiency of the website administrative task by replacing it with new technology CMS.
-- What were your requirements for choosing a CMS?
We chose a CMS based on its "basic functions and usability" as well as "a balanced functionality, costs and future potential" and also"multi-language support". Details are as follows.
Requirement 1) Basic functions and usability
The members who engage in web content production are not only specified specialists, so we needed an easy-to-use CMS which also enables to have approval workflows with ease.
Requirement 2) A balanced functionality, costs and future potential
Even with a large-scale and expensive CMS, it will be a waste of money if it is too hard to handle. A low-cost CMS is not an option either if it is poor in functions. We needed to find a one with a balance among functions, costs, future potential and reliability.
Requirement 3) Multi-language support
We were looking for a CMS which allows local staff to use the administration menus and pages in their own languages in addition to publishing contents in multiple languages. Also, multi-domain support was essential as well.