Site Organization (How To Use)

The Official Chraki Language Site can be a little confusing at first to the uninitiated. But fear not, I, Asher Wolfstein, shall explain how to get around so that you may make the best of the available resources.


First and foremost, if you want to engage in discussions on blog posts of the main site (this one), suggest and edit encyclopaedia entries, or engage with fellow Chrakians (Chrakiphones?) on the forum, you’ll need to register yourself an account. This is a relatively painless procedure, but it’ll get you much farther in the site.

Once you’ve registered an account you’ll be able to edit your main account information in the account section of the main site. The forum also contains an account/profile section as well, so if you’re looking for that functionality make sure you’re currently under the forum subdomain.

For logging in and logging out you can either use the links found at the top and bottoms of the page (desktop), or in the expandable menus (mobile). You can also use the handy widget located to the right (desktop), or to the bottom (mobile).

The Subdomains

The site, currently, is split into three (eventually it will be four) different subdomains. Subdomains are the part of the domain name that comes before, such as the www in The first subdomain is actually not a subdomain, it’s just the domain and that is this site (the main site.)

Main Site is the “main” site that hosts all of the overarching general information for the language, as well as “official” developments, research musings, and decisions made about the language. It is in a traditional blog structure with pages (like this one) and posts. The posts belong to categories and are each attached to various tags. You can see these categories and tags (it’s the fourth tab over on the multi-tabbed widget) on the left when viewing the lists of posts or the right if you’re on a single page or post.

Encyclopaedia is the “wiki” section of the Chraki language site, otherwise known as the encyclopaedia (or encyclopedia if you prefer.) This section houses all of the specific information for the language including codification definitions, syntax structures, grammar rules, phonetic scripts, and more. Each entry here can, generally, be edited by any user making it much like a wiki (though not a traditional MediaWiki installation.)

In an older version of the encyclopaedia you had to suggest entries using a form found near the bottom right of the page. However, since the wiki functionality has been revamped you can now create a potential wiki entry for review right on the main encyclopaedia page. To access the main encyclopaedia functionality, simply click on the “Encyclopaedia” link in the header menu (below the site title) to go to From there you can add/suggest a wiki entry using the “New Article” button in the upper right of the page.

With the new encyclopaedia you can leave comments for discussion, and there is a built-in formal revision system accessible to the administrators in case changes need to be unmade. These were two issues that were addressed with the new wiki system.

Forum is where community discussion about Chraki (and whatever else strikes our fancy) occurs, particularly in lieu of a specific “talk” page in the wiki at the moment. Feel free to express yourself, your thoughts, your creative aspirations, and more in a welcoming (maybe a bit geeky?) moderated community of enthusiasts.

Since this site/project has just started, I will admit that the community is rather small, however, that can be a good thing. Please don’t be intimidated, or dismissive, too prematurely for lack of postings. You could tread new ground!

In terms of other avenues towards community the Chraki language also currently has an official Twitter account (@chrakidev) I’m looking into also establishing a presence on Pinterest, and perhaps Instagram, but as of now, these are only tenuous prognostications. If there is interest in something more immediate for communication, such as real-time chat, I am also open to establishing a Chraki chat server on a service such as Discord or Slack.

Server (Coming Soon!) (doesn’t exist yet) is the planned destination for what I hope can really set this site apart. This portion is planned to offer several different functionalities, all focusing on (attempting to) make Chraki an easily utilized and accessible (enough) resource.

For example, since the writing system of Chraki is, at its core, ideographic (as opposed to using a roman-like alphabet or other alphabetic symbols available in the exhaustive Unicode standard) then a most useful thing to have would be a (web-)font that could allow font-compatible services/applications (like web browsers) to map character encodings to the appropriate font symbols.

This is where something like The Chraki Language Server can come in, offering an HTTP (or otherwise) accessible end-point for (down)loading a font file in various formats, compiled from all the available resources (codifications, scripts, etc.) that have been input into the Chraki site in near-real-time and on-demand. Think of it as a typographic content delivery network, ala Google Fonts.

I can personally see it go even farther than that (being the ever programmer extraordinaire I am), to the point where it could offer REST-style API’s for loading codification definitions, codification relationships, browsing the encyclopaedia, editing symbols/entries, and such to a compatible client, and even provide an interface for learning the language through spaced-repetition (like WaniKani does for Japanese) and other software. It can also provide documentation and code snippets/libraries for integrating Chraki into other applications, general-purpose conlang-centric software tools/libraries, and of course the eventual Chraki compiler(s) and specs.

In Conclusion

I hope this was able to convey how this site is structured and how best you might get use out of it. If you have any further questions, I’ll be compiling a FAQ in the future, so please contact me and I’ll be happy to clear up any confusion.

%d bloggers like this: