Now you’ll want to open the folder you’ve created your project in. With those sorted out, you can hit Create Repository and Clone and you’ll be greeted by something like this: As for Where to clone to, navigate to an empty folder where you’ll be keeping all your wiki files.Clone after init needs to be checked, so that everything will be set up on your hard drive.Name is, of course, the name of your wiki.For Account, select the dropdown and choose your account on GitHub.To run down what’s actually important here: If the accounts are connected right, that will take you to this popup full of options: You’ll probably be greeted by this window:įrom there, you’ll need to hit the button I’ve highlighted on the screenshot above, to start a hosted project. The very first thing you’ll want to do is to fire up GitKraken and follow all the instructions to connect your GitHub account. I’ll be using GitKraken, which makes everything nice and visual with pretty buttons. A client to make uploading to GitHub easier if you don’t already know Git.A GitHub account, which will be used for hosting and updating the wiki.TiddlyDesktop, which makes editing and saving wikis easier.An empty wiki file, straight from the source:.The way I’ve set this one up turned out to be the most straightforward way to do it for me even though it’s a bit hacky. Part I: Setting up a new wikiįirst off, there’s a lot of different ways of using, managing and hosting these wikis with no limit with how complicated you can get with it. Eventually I came across TiddlyWiki and it’s incredible, so here is a tutorial on how to use it for your own worldbuilding wikis. I’ve spent far too much time going through all sorts of ways of doing wikis, trying to find something that does exactly what I want and is easy enough to use. You can find a live version of it on /QuintalisWorldbuilding/ Things have pivoted more towards worldbuilding and tabletop RPGs for me and with that, I’ve started working on a wiki to keep the world and the game organized: IN NO EVENT\nSHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,\nINCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED\nTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE, DATA, OR PROFITS OR\nBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN\nCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN\nANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH\nDAMAGE.Magusdawn is solidly enshrined in the realms of vaporware, but that doesn’t mean the world of Quintalis is shut. "text": "TiddlyWiki created by Jeremy Ruston, (jeremy jermolene com)\n\nCopyright © Jeremy Ruston 2004-2007\nCopyright © UnaMesa Association 2007-2014\n\nRedistribution and use in source and binary forms, with or without modification,\nare permitted provided that the following conditions are met:\n\nRedistributions of source code must retain the above copyright notice, this\nlist of conditions and the following disclaimer.\n\nRedistributions in binary form must reproduce the above copyright notice, this\nlist of conditions and the following disclaimer in the documentation and/or other\nmaterials provided with the distribution.\n\nNeither the name of the UnaMesa Association nor the names of its contributors may be\nused to endorse or promote products derived from this software without specific\nprior written permission.\n\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY\nEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES\nOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. "text": "TiddlyWiki incorporates code from these fine OpenSource projects:\n\n* ]\n* ]\n* ]\n\nAnd media from these projects:\n\n* World flag icons from ]\n"
0 Comments
Leave a Reply. |