tumblr migrates back end to wordpress
Posted: Wed Jan 08, 2025 4:31 am
The announcement post talks about how once you migrate you hungary phone number will be able to share your work across multiple platforms and build something that works for one and easily port it to the other.
Tumblr and WordPress increasingly… close together (photo WordPress) – sos-wp.it
The easy part , and this is information that we learn from the announcement made by Automattic about the engineers who will help in this titanic undertaking, is that both Tumblr and WordPress are built from PHP but it is clear that there are also a whole series of elements that need to be modified and expanded in their capabilities, so that the two platforms can communicate and exploit one another's work.
The promise is that from the outside, for users therefore, nothing will change . What will change is the most hidden part, the one that allows the structure itself to stand up. With the change, the tools and functions that, once the migration has taken place, will be built for example for WordPress can then be easily integrated into what Tumblr does, while the ideas that could be implemented to make Tumblr grow can more easily be transformed into something to be used also within WordPress.
This isn't the first time such large companies have announced changes of this kind. Among the most striking cases are when Twitter continued to function while part of its back-end was rewritten and updated and when the late Myspace moved to the Microsoft structure. As for this large immigration, there are no dates or a road map.
And this is perhaps the aspect that we can understand most easily, if the company is now looking for engineers to build the gigantic caravan. What is noteworthy, however, is how Automattic apparently intends to continue to keep Tumblr alive, even if the team that worked on the platform within the company was recently reduced to the bare bones while many, among those who were not fired, have moved on to work on other projects.
Having the same architecture could also have the long-term benefit of reducing management costs: If everything runs on the same architecture, there is no need to double the number of people who have to deal with it. A choice that could also help keep afloat a site that, in Automattic's coffers, has already cost several million dollars in lost earnings.
Tumblr and WordPress increasingly… close together (photo WordPress) – sos-wp.it
The easy part , and this is information that we learn from the announcement made by Automattic about the engineers who will help in this titanic undertaking, is that both Tumblr and WordPress are built from PHP but it is clear that there are also a whole series of elements that need to be modified and expanded in their capabilities, so that the two platforms can communicate and exploit one another's work.
The promise is that from the outside, for users therefore, nothing will change . What will change is the most hidden part, the one that allows the structure itself to stand up. With the change, the tools and functions that, once the migration has taken place, will be built for example for WordPress can then be easily integrated into what Tumblr does, while the ideas that could be implemented to make Tumblr grow can more easily be transformed into something to be used also within WordPress.
This isn't the first time such large companies have announced changes of this kind. Among the most striking cases are when Twitter continued to function while part of its back-end was rewritten and updated and when the late Myspace moved to the Microsoft structure. As for this large immigration, there are no dates or a road map.
And this is perhaps the aspect that we can understand most easily, if the company is now looking for engineers to build the gigantic caravan. What is noteworthy, however, is how Automattic apparently intends to continue to keep Tumblr alive, even if the team that worked on the platform within the company was recently reduced to the bare bones while many, among those who were not fired, have moved on to work on other projects.
Having the same architecture could also have the long-term benefit of reducing management costs: If everything runs on the same architecture, there is no need to double the number of people who have to deal with it. A choice that could also help keep afloat a site that, in Automattic's coffers, has already cost several million dollars in lost earnings.