Mike's Notes
I'm working out a pattern to use for naming workspace URLs. This is part of the current build roadmap.
Resources
- https://en.wikipedia.org/wiki/Google_Workspace
- https://en.wikipedia.org/wiki/Zoho_Office_Suite
- https://www.blog.ajabbi.com/2025/09/the-internal-control-hierarchy-of-pipi.html
- https://www.blog.ajabbi.com/2025/09/localisation-options.html
- https://developer.ajabbi.com/eng/9/report/roadmap.html
- https://help.forcepoint.com/fpone/deploy/rhtml/application/guid-ee073056-4fe1-40f5-b44e-3bf21491f0bb.html
- https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide
- https://support.google.com/a/answer/53340?hl=en
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
25/10/2025
Workspace URL naming pattern
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
Logged-in Ajabbi users will be able to use web-based applications called a workspace. Each application requires a URL that follows a predefined pattern.
Again, this is a work in progress and is likely to change, especially as it addresses performance, usability, security, and privacy issues.
Here are examples used by other companies.
Google Workspace example URLs
- https://calendar.google.com/calendar/u/0/r/week
- https://calendar.google.com/calendar/u/0/r/month
- https://mail.google.com/mail/u/0/#inbox
- https://mail.google.com/mail/u/0/#sent
- https://draft.blogger.com/blog/posts/jsdksjdksJK;Sjk;SJDKsjd/
- https://draft.blogger.com/blog/post/edit/hhddfddfd/
- https://docs.google.com/document/d/5fd8f5/
- https://contacts.google.com/directory
- https://contacts.google.com/person/123456789/
- https://groups.google.com/all-groups
- https://groups.google.com/g/ontolog-forum
- https://groups.google.com/g/ontolog-forum/c/coj8JqR6nzw
Zoho Office Suite example URLs
- https://www.zoho.com/mail/
- https://accounts.zoho.com.au/signin?
Service Now example URLs
- <instance>.service-now.com/now/cmdb/relationship-health-dashboard/
- https://www.servicenow.com/docs/bundle/zurich-healthcare-life-sciences/page/product/healthcare-life-sciences/concept/hcls-cto-care-team-portal.html
- <instance>.service-now.com/now/servicenow-studio/home
- https://www.servicenow.com/docs/bundle/zurich-application-development/page/administer/ui-builder/concept/ui-builder-overview.html
MuleSoft example URLs
- https://docs.mulesoft.com/exchange/to-describe-an-asset
Note: The URLs below don't link to anything.
Ajabbi workspace domain
Note: workspace. or app. or cloud. or wsp/ ? I have decided on cloud.
The default naked domain URL is
- https;//cloud.ajabbi.com/
The user account code name will be added as a URL before the domain.
- https;//example.cloud.ajabbi.com/
Domain redirection enables
- https://cloud.example.com/
Ajabbi Workspace proposed available URL patterns
A lot of customisation will be possible for user accounts.
- https://cloud.ajabbi.com/eng/9/e/calendar/
- https://example.cloud.ajabbi.com/eng/9/e/calendar/
- https://example.com/cloud/eng/9/e/calendar/
- https://example.com/eng-uk/cloud/9/e/calendar/
- https://app.example.com/eng-uk/e/calendar/
- https://calendar.example.com/eng-uk/
- https://en.example.com/workspace/e/calendar/
- https://fr.example.com/espace/e/calendrier/
Workspace application directories
Each application has directories associated with different tasks.
- inbox/
- draft/
- sent/
Some simple examples using mail.
- https://cloud.ajabbi.com/eng/9/e/email/inbox/
- https://cloud.ajabbi.com/eng/9/e/email/draft/12345678/
Security concerns
Long, meaningless code will be used to name endpoints similar to those used by Google.
- https;//cloud.ajabbi.com/eng/9/e/email/draft/hnjsdhtrhxn79snrfusni9c5/
To do next
- Define the code names to use with all the workspace applications
- Build some static web-based workspace mockups
- Make some examples in other languages and scripts
- Share with volunteer testers
- Reiterate till people are happy
- Build a working demo at
- https://demo.cloud.ajabbi.com/
- Provide a Template Engine template for the Pipi Render Engine to render on demand from the Pipi Deployment Engine.
- Automate the deployment of workspaces for logged-in users.
No comments:
Post a Comment