This is an initial walkthrough for how to create your own Kinja Group Blog. This post has been updated with images and is provided as an additional aid to the provided Kinja Help files which are linked at the bottom of this post.
Note: this walkthrough is taking one additional step of creating an entirely separate account instead of using your primary account. You can use your primary account, but I chose to write this up in this manner because this has zero risk of losing your primary commenting account. (But does involve creating a secondary Kinja account, which may or may not be wanted).
For those who want to use their currently existing account, treat that as the commenting account in the steps below and associate the newly created account with a different login method than the one you currently are using. (If your current account is linked to twitter, then create a new Kinja account using a gmail or Facebook account (this new account will be the one you will turn into a group blog, so name it carefully. You cannot change the URL once it is set.), and then proceed from step 7 logging into your current Kinja account.
Step 1: Create a Gmail Account
Step 2: Create a Twitter account
Step 3: Create a Kinja Account with Gmail Account, this can be an account you would want to keep, or potentially be one that you are willing to sacrifice. Once you set the name of the account, the URL address cannot be changed, so if this one will be the groupblog, name it carefully in terms of your URL (XXXX.kinja.com). Heck, name it carefully otherwise as well, if you plan on using this account as a commenting account.
Step 4: Log out of new Kinja Account.
Step 5: Create a Kinja Account with Twitter account, this can be an account you would want to keep, or potentially be one that you are willing to sacrifice. (same as above, but one of them will need to go, and you have control which one you lose. Once you set the name of the account, the URL address cannot be changed, so if this one will be the groupblog, name it carefully in terms of your URL (XXXX.kinja.com))
Step 6: Log out of new Kinja Account.
Step 7: Log into the Kinja Account you want to keep as a commenting account (not the one you want to turn into a blog). Then navigate to an existing group blog, go to your Account Settings in your personal dropdown and select Expand Connected Accounts. Select Connect for the other account which you have just created (i.e. if you are logged into your gmail created account at this point, and want to turn your twitter created account into a groupblog, you will connect your new twitter account).
Step 8: Once you understand that the account which you are connecting will be lost, and cannot be undone, confirm that you want to merge the accounts. (In the example where you are signed into your gmail associated kinja account, you will be making a group blog out of the twitter associated kinja account. THE MERGED ACCOUNT WILL NO LONGER BE A COMMENTING ACCOUNT.
Step 9: verify that the account has been connected and created and then manage the new group blog and associate the blog with your standard account by adding your standard login as a member in the Manage Blog area. You can then exit this window and come back and make that account either an admin or transfer ownership to your primary account if you wish.
Step 10: BLOG!
For additional documentation, see these help files:
And this HackerSpace post on how to see what Moderators can do, and how they do it:
Kinja Admin Powers
***Note***: as burner accounts cannot be associated with other login credentials, it appears that you cannot use them to create a group blog.
Additionally, as Magister notes in the comments, it should be cautioned that if a burner owns a group and if they lose their key, there will be no way to name (or dismiss) an admin and if they are the only admin, then the place would forever be modless and no one would be able to add new members.
If anyone has any additional comments on this subject (burners are not my specialty, but I know that these accounts have some restrictions, or perhaps had) please let me know.