Organization page not able to create

[gitesh-sharma]

Discussion Type

Question

Discussion Content

Dear team,

I just want to create the page of organization called Places and make site like places.github.io. Please help me..

Thank you.

[karanks6]

To publish an organization site at places.github.io without running into a 404 error, verify each of the following configuration requirements:

1. Match the Exact Organization Handle

To get a root site URL like https://<organization>.github.io, the repository must be named exactly <organization>.github.io:

• Ensure the organization handle on GitHub is indeed places (i.e., [https://github.com/places](https://github.com/places)).
• If your organization URL is slightly different (e.g., [https://github.com/places-org](https://github.com/places-org) or [https://github.com/places-team](https://github.com/places-team)), the repository must match that exact handle (e.g., places-org.github.io).
• The repository must be owned directly by that organization, not under a personal user account.

2. Set Repository Visibility to Public

On standard free GitHub accounts, GitHub Pages is only available for Public repositories. If the repository is set to Private, the Pages site will fail to publish and return a 404 error unless your organization has an active GitHub Team or Enterprise plan.

3. Add an Entry File (index.html or index.md)

GitHub Pages requires an entry point file in the root of your publishing branch:

• Ensure the repository is not empty.
• Add an index.html file (or index.md) in the root directory so the web server has a landing page to serve.

4. Enable GitHub Pages in Settings

1. Open the repository on GitHub.
2. Go to Settings > Pages (under the "Code and automation" menu on the left).
3. Under Build and deployment:

• Source: Select Deploy from a branch.
• Branch: Choose your default branch (usually main) and the / (root) folder.
• Click Save.

5. Check the Actions Workflow and Propagation Delay

After enabling Pages and pushing an index.html:

• Click the Actions tab in your repository and verify that the pages-build-deployment workflow has finished with a green checkmark.
• After the workflow successfully runs, allow 2–5 minutes for DNS propagation before refreshing the URL.

[ZigaLeopold]

i like bbc