Learn how to properly name your projects and automatically assign a free custom URL on a subdomain based on the project name.

Table of Contents

1. Why Project Naming Matters
2. Rules for Project Naming
3. Automatically Generating Subdomains
4. Setting Up Free URLs for Projects
5. Best Practices
6. Troubleshooting
7. Glossary

---

Why Project Naming Matters

A good project name is essential because:

• It becomes part of your project's identity.
• It is used in URLs, making it part of your brand.
• It helps with user recognition and SEO.
• It must be unique within your platform.

---

Rules for Project Naming

To ensure smooth URL creation and avoid conflicts, project names should:

• Be unique across your platform.
• Contain only lowercase letters, numbers, and hyphens (-).
• Start and end with a letter or number.
• Have a length between 3 and 30 characters.
• Avoid reserved words or special characters.

Example valid names:

• my-awesome-project
• project123
• team-x

---

Automatically Generating Subdomains

Once a project name is chosen and validated, the platform automatically generates a free URL in the format:

https\://{project-name}.esadax.com

For example, if your project name is my-awesome-project, your free project URL will be:

[https://my-awesome-project.esadax.com](https://my-awesome-project.esadax.com)

This URL is:

• Automatically assigned and reserved.
• Unique per project.
• Available immediately upon project creation.

---

Setting Up Free URLs for Projects

Here is how the free URL assignment works behind the scenes:

1. Validate Project Name: Ensure it meets naming rules and is unique.
2. Assign Subdomain: Use the project name as the subdomain.
3. DNS Configuration: Your platform’s DNS uses a wildcard *.esadax.com record pointing to your hosting infrastructure.
4. Routing Setup: The platform routes incoming requests to the correct project based on the subdomain.
5. SSL/TLS Certificates: Automatic provisioning of SSL certificates (e.g., via Let's Encrypt) for secure HTTPS access.

---

Best Practices

• Validate names client and server side to prevent invalid URLs.
• Reserve or block offensive or sensitive names to protect your brand.
• Implement conflict resolution if users try duplicate names.
• Allow users to preview their project URL before finalizing creation.
• Provide custom domain support for users wanting their own branded URLs.

---

Troubleshooting

• Subdomain already taken?

  • Choose a different project name.
  • Append numbers or unique suffixes to your desired name.

• URL not resolving?

  • Check DNS wildcard configuration.
  • Verify routing rules on your backend.

• SSL errors?

  • Confirm SSL certs are provisioned and renewed properly.

---

Glossary

• Subdomain: The prefix before your main domain, used to separate projects.
• Wildcard DNS: A DNS record that matches any subdomain.
• SSL Certificate: Security certificate enabling HTTPS.
• Unique Project Name: A project name that no other user has chosen.

---

This approach offers users a smooth experience with instantly accessible, branded URLs tied to their project names, increasing visibility and professionalism.