1. Introduction: Oh we missed on introducing you to internal domains

Welcome to the world of internal domains. We will introduce you to one of this platform's simple yet effective features.

What is the internal domain or internal subdomain?

Well, we lack creativity, and so do all the engineers on the floor. Oh yes, we are engineers indeed. We look, love, and admire the internal beauty.

Getting back to the topic, internal domains are the platform-managed publishing spaces provided to all the authors. We understand that not all authors will start publishing using their domains. Just look at us. We are also using this platform to host our documentation. Oh, wait a minute, we are developing this platform. So, we are bound to host the documentation on this platform. But we can host it elsewhere. I think XXX would be interested in hosting these docs elsewhere.

Resuming back to the topic. This is our honest effort to provide every author with the tools they need to start publishing their work if they wish to.

Internal domains are provided at no additional cost. The only risk I can think of as I write is what if I push smelly code that breaks the publishing flow. Wait, you are still able to read this article. If not, please reach out to us at authorbox.app@gmail.com. (Why do we use the Gmail email address? Well, that's a long story worth its sidetrack.)

Cool. So, I told you about internal domains, which are provided at no additional cost. Awesome. So I think I am done. Wait. I think I am missing something. Oh yes, did I talk about the structure of these domains?

Structure Of Internal Domains

https://<project_name>.<box_name>.authorbox.org

In English, we use the project name, followed by the box name and authorbox.org. The project and box names are separated by a dot [.], and we ship them with SSL certificates. Thanks to our friends at Let's Encrypt.