{"id":25426827,"url":"https://github.com/microsoft/react-native-devblog","last_synced_at":"2025-10-31T16:30:27.109Z","repository":{"id":65976118,"uuid":"566058948","full_name":"microsoft/react-native-devblog","owner":"microsoft","description":"Repository hosting the markdown files for the React Native dev blog","archived":false,"fork":false,"pushed_at":"2025-01-31T18:12:43.000Z","size":39571,"stargazers_count":9,"open_issues_count":0,"forks_count":3,"subscribers_count":6,"default_branch":"main","last_synced_at":"2025-02-16T10:18:31.365Z","etag":null,"topics":["articles","blog","react-native","react-native-macos","react-native-windows"],"latest_commit_sha":null,"homepage":"https://devblogs.microsoft.com/react-native/","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/microsoft.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":"SECURITY.md","support":"SUPPORT.md","governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-11-14T22:07:39.000Z","updated_at":"2025-01-31T18:12:46.000Z","dependencies_parsed_at":"2024-07-15T21:44:08.535Z","dependency_job_id":null,"html_url":"https://github.com/microsoft/react-native-devblog","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Freact-native-devblog","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Freact-native-devblog/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Freact-native-devblog/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Freact-native-devblog/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/microsoft","download_url":"https://codeload.github.com/microsoft/react-native-devblog/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":239214054,"owners_count":19601077,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["articles","blog","react-native","react-native-macos","react-native-windows"],"created_at":"2025-02-17T00:22:45.838Z","updated_at":"2025-10-31T16:30:27.060Z","avatar_url":"https://github.com/microsoft.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# React Native devblog\n\nThis **public** repository serves as the backbone of the official [React Native DevBlog](https://devblogs.microsoft.com/react-native/).\n\nThe editorial team is currently composed by [Steven Moyes](https://github.com/stmoy) and [Lorenzo Sciandra](https://github.com/kelset).\n\n## Writing guide\n\nThe general flow for contributing content to the devblog is, briefly:\n\n    1. Idea gets pitched\n    2. Idea gets approved\n    3. Draft gets made\n    4. Draft gets approved\n    5. Draft gets published\n\nLet's dive a bit more into each step:\n\n### 1. Pitching an idea for content for the devblog\n\nWe want to empower everyone at Microsoft to be able to create content for the React Native DevBlog; in order to do so, we have prepared an issue template for [pitching ideas and proposing content](https://github.com/microsoft/react-native-devblog/issues/new?assignees=\u0026labels=pitch\u0026template=pitch-idea.yml\u0026title=%5BPitch%5D%3A+) that the author would like to work on.\n\nFirst time authors **need** to pitch their idea via this method. Recurring authors can jump directly to step #3 if they feel their proposal is solid, but we'd suggest to still go first via an issue for pitching.\n\nPlease remember that since this repository is public, all the information you will be sharing in your pitch should be shareable with the general public! If there are aspects of your idea that you might want to pre-discuss privately first, reach out to the editorial team.\n\n### 2. Idea gets approved\n\nOnce the editorial team has been able to review the idea and approve it, the author will be added to the [RNDevBlog Writers](https://github.com/orgs/microsoft/teams/rndevblog-writers) GitHub team.\n\nThe author will also be asked to join the [Wordpress Instance](https://devblogs.microsoft.com/react-native/wp-admin/users.php) and setup their author profile over there; the username in Wordpress is needed for the author metadata field (see in the next section).\n\n### 3. Draft gets made\n\nOnce the author has got write access to the repository, they will git clone it and create a branch similar to `\u003cauthor-alias\u003e/\u003cblogpost-title\u003e`.\n\nIn it, they will make a new markdown file named something like `\u003ctentative-date-YY-MM-DD\u003e-\u003ctitle\u003e.md` and copy over this template:\n\n```md\n---\npost_title: \"post title\"\nauthor1: the-author-wordpress-username\npost_slug: same-as-filename\npost_date: same-as-filename-YY-MM-DD 12:00:00\ncategories: react-native // don't change the category\ntags: // add one or more tags, try reusing existing ones\nsummary: // one of two phrases that will preview the content\n---\n\n// the actual content goes here\n\n---\n\nIf you’re interested in getting started with React Native for Windows, check out our website at [aka.ms/reactnative](https://microsoft.github.io/react-native-windows/).\n\nYou can also follow us on X [@ReactNativeMSFT](https://twitter.com/reactnativemsft) to keep up to date on news, feature roadmaps, and more.\n```\n\nThey can then work on the markdown file, adding their content and modifying the metadata accordingly.\n\nIf they need to add assets like images, put them in the `assets` folder; if there's more than one piece of media, please make a dedicated subfolder under `assets/\u003cblogpost-file-title\u003e`.\n\nIf needed, a custom featured image can be added under `assets/featured-images/\u003cblogpost-file-title\u003e`. More indications around featured images will be added ASAP.\n\n### 4. Draft gets approved\n\nOnce the author is ready to have their content reviewed, they can push up the branch and open a PR. At this point, the editorial team will review it and decide a publishing date with the author (so that the markdown file can have the right timestamp where needed).\n\nOnce it's approved, congrats! It's almost ready to be published: the PR will get merged, and with the help of the editorial team the tool syncing the GH-\u003eWP content will be triggered (it might require a one-commit-one-file follow up commit in main branch).\n\n### 5. Draft gets published\n\nOnce the draft reaches WordPress, it will only put it as a draft; the editorial team will need to go into the WP dashboard, \"all posts\" sections, select the new post (it will have a \"- DRAFT\" appended to the title), click on Edit, set the right date, then hit publish.\n\nAfter publication, the content will be broadcasted accordingly on whichever social medias have been agreeded (if any).\n\n### More information and gotchas\n\nRead more of how to use Markdown to deploy to the WordPress based blog [in this documentation](https://dev.azure.com/devdiv/DevDiv/_wiki/wikis/DevDiv.wiki/10339/Drafting-in-GitHub?anchor=template-to-add-at-the-top-of-a-github-file).\n\nThe tool used for this GH -\u003e WP synchronization has a few limitations, so please keep the following in mind:\n\n- any edits to the post in WordPress side will not be synced back to GitHub. They will need to be manually replicated.\n- remember: author username need to be the WordPress ones, not the GitHub ID\n- on main, you need to do a one-commit-per-one-blog strategy (you can checkout the history for examples): the GH-\u003eWP tool doesn't work when you push multiple files in the same commit\n\nFor any further questions reach out to the editorial team.\n\n## Code of Conduct\n\nThis project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).\nFor more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or\ncontact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.\n\n## Trademarks\n\nThis project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft\ntrademarks or logos is subject to and must follow\n[Microsoft's Trademark \u0026 Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).\nUse of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.\nAny use of third-party trademarks or logos are subject to those third-party's policies.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmicrosoft%2Freact-native-devblog","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmicrosoft%2Freact-native-devblog","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmicrosoft%2Freact-native-devblog/lists"}