Write. Review. Publish.

1. Start a new article

Open Pages CMS, sign in with GitHub, choose your blog repository, and open Articles. Use New entry. The practice draft is available for learning the editor.

2. Set the title and URL

Write your title in English. For URL name, use a short English phrase with hyphens, such as small-bedroom-storage. The resulting link is /articles/small-bedroom-storage/. Keep this URL name unchanged after publishing to preserve existing links.

3. Format your content

Select text and use the editor toolbar. Use H2 for main sections and H3 for smaller sections. The article title already supplies H1. Use ordered lists for steps and bullet lists for items. Select text and click the link control to link to an article or a relevant source. Use the image control to upload a picture you have rights to use.

4. Check the details

Add a clear summary, category and publication date. Describe your cover image in the image-description field. For health topics, include authoritative sources and avoid unsupported treatment claims.

5. Save and publish

Keep Published off while drafting. Turn it on and save when ready. Saving commits your changes to GitHub, and the publishing workflow updates your blog and sitemap. A future date is held back until a later build on or after that date; this setup does not promise automatic timed publishing.

6. Edit or unpublish

Open an existing article to edit it. Change the updated date only after a substantial revision. To unpublish, turn Published off and save. The next successful build removes the article from the website and sitemap; search engines may take longer to remove cached results.

7. Tell Google about your blog

Add https://arun-ahirwar.github.io/ as a URL-prefix property in Google Search Console. Copy the HTML verification tag’s content value into Website settings → Google Search Console verification code. Save, wait for publishing, verify in Google, then submit sitemap.xml.

GitHub Free uses a public repository for this website. Draft content and Git history are visible there. This is a publishing workflow, not a private notebook.