# ReactOS Newsletter 94: Site Migration and Visual Studio Development

DevFeed: [ReactOS Newsletter 94: Site Migration and Visual Studio Development](<https://devfeed.tech/articles/newsletter-94-32960.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/newsletter-94/>)

Published: 2013-02-27T00:00:00Z

Content type: news

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [ReactOS](<https://devfeed.tech/topics/reactos.md>), [migration](<https://devfeed.tech/topics/migration.md>), [CMake](<https://devfeed.tech/topics/cmake.md>), [Drupal](<https://devfeed.tech/topics/drupal.md>), [Visual Studio](<https://devfeed.tech/topics/visual-studio.md>), [jira](<https://devfeed.tech/topics/jira.md>)

Tags: [cmake](<https://devfeed.tech/tags/cmake.md>), [free](<https://devfeed.tech/tags/free.md>), [migration](<https://devfeed.tech/tags/migration.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [visual-studio](<https://devfeed.tech/tags/visual-studio.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

ReactOS Newsletter 94 reports on the project's migration to a Drupal-based site, including problems with missing or incorrect content, translations, permissions, login, and latency. It also describes progress toward developing and building ReactOS in Visual Studio through CMake support.

## Source excerpt

Site Migration The project recently migrated from its old site to one using the Drupal content management system. Work on this migration had been going on in some form for the last year, with a major milestone being the migration from Bugzilla to JIRA. The migration of the site proper however was nowhere as smooth as many people, including myself, desired. One of the root causes for the bumpy migration was my fault actually, when I sent an email claiming that the site's content was at a state where it should not be a blocker to migration.