A question I’m getting more than once is ‘how do you organize your wiki so that it’s useful for your writing.’ Which… is not a minor question, because my initial response is ‘I’ve organized it? It’s a big enormous tangled mess of stubs and passages from one blank space to another and then boom! Wall of text.’
It is tempting to go at this like a prescriptive text: “The proper way to organize your wiki is to divide it into the following nine sections, under which you should have some number of these categories.” That would be so satisfying, and anxiety-reducing, because it would suggest there is a Right Way to organize your writers’ bible (because that’s what it is, really), and if you organize it so, you will get it right the first time and it will be perfect.
But… there isn’t a right way. All I can tell you is my organizational principles, and maybe they’ll spark some ideas in your head.
My first and most important guiding principle is: start with the stuff you need. By which I mean the things you know you’re always forgetting and are desperate to have at your fingertips. For me, that’s character info. What color was someone’s eyes? How old are they? What was their middle name? What did they do in that last book? Do they drink coffee or tea? Did they mention any pets? Ever?
So I started by making pages for characters. (I have a lot of characters.) I knew that was a good choice because when I began writing the newest book, I consulted the wiki not even a week into its establishment to check some facts. As I continued writing, I kept finding other frequent offenders: “I remember saying some things about this location, but not what,” and “I can never remember how many provinces are in this nation” and “Didn’t I make up names for these historical figures.” At which point I started making pages for those things too. Every time I ran into something that I needed to know, I made a page for it, looked that info up, and dropped it in the right place.
Wikis aren’t just for writers, either; I have these “oh no I need to look that up” moments about art things too, so I started uploading all the major pieces of art I keep looking for: maps of different continents, uniforms from different services, representations of species, portraits of particular people. If you have images like this, putting them in one place is great for any artists you might want to hire in the future, too. Just make sure you have the rights to reproduce those images if they’re not yours. (Obvious, but must be said.)
All of us have major pain points in our worldbuilding and they will be idiosyncratic. Maybe you keep making up words in a conlang. Or you have named the cuisines of seven different fictitious countries and their ritual significance. Maybe you are fascinated by coastlines and keep creating port cities. The thing that you’ve developed most, and the thing you need to remember, is the place you need to start filling in data. So while my wiki might have grown from characters to those characters’ species to those species’ worlds and foods and religions and histories, yours might begin with types of ships, or noble families, or principle exports and imports.
The thing you need the most is the thing you need to record first.
Once you’ve recorded the stuff you need most, organize it so that you’ll find it fastest. I like the wiki for being able to search, but sometimes search doesn’t get you the results you want, or in the order you want them, which is where categorizing comes in. At several people’s suggestion I enabled the Category Tree extension which lets you create nested categories, and that’s been immensely helpful because it allows the display of all the items in a category. So if I want to keep track of all the Scout-class ships in Fleet, I can add them to that category and then display that category on some master page (like “All the Ships in Fleet”).
As you can imagine, categorization is even more idiosyncratic than “start with the stuff you need.” Because I could tell you ‘you should classify your food pages based on whether they are breakfast, dinner, or lunch’ while what you really need to know is whether each dish is served hot or cold, or whether they’re religious foods or common meals, or what have you.
The nice thing about categories is that you can use more than one… so if you want something to show up as both a brunch and a food served only at a treaty table, you can place it in both “Brunch” and “Peace Feast Foods” and find it both ways. You can also categorize images; most of mine have multiple categories, telling me what stories they’re relevant to along with what characters are in them and what kind of image they are (map? Schematic? Portrait?)
None of which was my idea, but I’ll get to that momentarily.
Use references immediately. Even if they’re imprecise or slapdash. Assuming you’re starting from some existing material you want to backfill, when you begin making your stubs, mention where you got your information, even if it’s just ‘I think it was chap 1 or 2 of this book.’ That’ll give you somewhere to start when you need to doublecheck the data, or add to it. Even when you record something that seems inconsequential, putting down where it came from is immensely useful to Future You: context matters. You can always go back and tidy up the references if they’re imprecise or not pretty, but if you put in the work immediately you will avoid a lot of extra research.
(My faithful volunteers have reminded me that the cool wiki reference tags are an extension that needs to be enabled. Mine is ‘Cite.’)
Another thing that I’ve found immensely useful is to make pages for every story I’ve published, because it gives my references somewhere to point to. If I say “This event happened in Book 2 of this series” or “This character first appeared there,” then the reference can link back to the page and give you the necessary info to either buy or find that story (if it’s in a collection somewhere). My fiction pages give basic citation info (publication date, series, etc), along with summaries and buy links. They’re also a great place to add easily lost material, like the cover images of previous editions, and ephemeral teaser and marketing materials that were used once and never reproduced on any gallery page.
I cordon off these pages by appending (Fiction) to all of them, just to make sure they don’t get mixed up with the data pages.
- A relatively “complete” novel entry: https://peltedverse.org/wiki/index.php?title=Dreamhearth_(Fiction)
- A short fiction entry with “just put it down and worry about the details later”-like stuff: https://peltedverse.org/wiki/index.php?title=Leadership_Lessons_(Fiction)
Make stubs. Then consolidate until it’s time to expand again. (A stub is a placeholder page with little to no data on it.) One of the nice things about the wiki has been that it’s easy to mend. My mantra has been “put it down now, organize it later,” and that works well because it’s trivial to delete or rename pages. I’ve made pages for things that I immediately needed, only to realize they didn’t need an entire page to themselves and that it would be easier to find them on some different page… and fixing that was a few moments’ work, by pasting the material into the other page and deleting its stub (and leaving a redirect, so if I ever searched for it again the wiki would send me to the new page). So, for instance, I had a separate page for a particular hospital, when I realized that there just wasn’t enough data to justify it being on a single page, and that I kept looking for it through its associated city anyway. That was a quick fix.
On the other hand, I discovered several items that became so big that it was far more sensible to break them off their parent pages onto pages of their own, which is how Fleet Procedures ended up on a new page from Fleet, which is where basic facts about the organization live.
The other nice thing about your wiki is that it doesn’t have to conform to any standard, and nothing you do has to be permanent. I had a group of friends that went on to do things together… where one went, the others were usually along for the ride. So I made a page for them as a group: “Jahir’s Retinue.” Is this a formal organization? Not yet. Will I always need a page to group them together? Maybe not. But for now, it’s fantastic to be able to type ‘Jahir’s retinue’ into search and get all those people in one place. And if one day, that retinue is disbanded, then I can move or delete that page, and relegate their prior service to a biographical section on their pages.
I feel that last point is particularly important: that you should feel okay about making completely nonsensical or whimsical-seeming pages that will only be useful to you, and only for as long as you need them. The point isn’t for your writer’s bible to function as a formal encyclopedia. It’s for it to be useful to you, whatever that means.
Which brings me to a theme underlying several of these points that needs to be made explicit: it’s better to get it wrong than to not do it at all. Wikis are forgiving; they maintain a log of all the changes made and allow you to rollback to any version of that history. Given that, there’s no reason not to make pages and flail around until you figure out what you’re doing… and every reason to do that flailing. You can’t work with something that doesn’t exist, so it’s better for your information to be awkward or in the wrong spot or even incorrectly named than it is to not have it there at all. You can always fix it. But until you have it down, you probably won’t know how.
That’s really one of the magical things about wikis: they reward flailing. They reward mistakes. Most of us don’t know all the things in our heads, or the relative importance of their relationships to other things, until we start making those things concrete and visible… and a wiki is a great way to start putting those things down in a form that allows us to see those relationships and decide what about them matters.
A brief digression about wikis as a technology. Most of us think of Wikipedia when we think of a wiki, and that’s a good example of one: it’s clean, easy to use, and feels like an encyclopedia. It’s not a bad mental model for what a wiki is, though what it actually is, is a database. (Here are my heart eyes, because who doesn’t love a database?). The reason it can be so hard to wrap your head around how to get started with a wiki is because it will cheerfully do and organize itself however you decide: it’s the ‘too much freedom’ problem. My suggestion, if you’re going at it for writer’s bible-purposes, is to keep the Wikipedia framing in mind and think of it as an encyclopedia. It has entries (pages) about topics, with accompanying illustration, and links within it are the equivalent of a paper encyclopedia writing “see also This Entry.”
Some of you haven’t ever used a paper encyclopedia, and… um… you probably don’t need my lecture on wikis because you understand them natively. Lol.
Another good example of a wiki framing: TVTropes. No I won’t link there, so if you go and get lost, don’t blame me. But if you do go there, take notes, because that’s an interesting, alternate use of a similar framework.
Okay, resuming the how-to. One of the great things about wikis is that, if you make them public, you will sometimes attract help! (Particularly if you ask for it, though not always.) By design, wikis are meant to be group-editable, which is one of the reasons their tools for repair are so robust. Unless you go to lengths to prevent it, people will be able to make accounts and contribute to your wiki. Which brings me to the most important principle regarding other people’s help: Volunteers are a source of chaos, and chaos is revelatory.
Just as readers bring themselves to your work when they engage with it, they bring themselves to their efforts on a wiki. They’ll have their own areas of interest, and their own experiences with the software, and their own ideas. It will be tempting to give anyone who shows up marching orders: “I really need this data” and “I want it organized this way.” But if you do that, you will shut down any ideas they would generate, and their ideas may be better than yours. Take the wiki’s infinite capacity for restoration to heart—anything you dislike or find awkward, you can adjust or fix, and no one’s going to argue with you about it because it’s your site. But as much as possible, when people show up and want to help, let them decide how and let that educate you… about the software (as I was, by one volunteer’s suggestion about Category Tree); about organization (someone made a section for family trees under biographical data, and that was brilliant); and even about the canon (someone made me a martial arts page, when I never thought I had enough data about martial arts to warrant one—I was wrong).
Besides if you let them have their heads, they make stubs like the one at the top of this page, and that’s worth any pain and suffering. 😆
If you have no volunteers, you can “borrow” this random seed by examining how other people organize their writer’s bibles, wikis, or data… which is how my template for planets got borrowed from the CIA’s World Factbook. (Also not my idea.) (Also brilliant.)
And for those of you who are thinking ‘does that mean I can borrow your ideas,’ the answer is ‘of course.’ 😊
Finally, a related principle, and really the most important one: your canon is your responsibility. The moment you start worldbuilding, you’re the one in charge, and that means to you devolve the pleasures of creating it… and the responsibilities of maintaining it. Eventually, you will have people point out errors to you, and those will be your fault, and their fixing will be as well, whether you fix them by addressing them or by washing your hands of them. There will be times where you change something and will have to stand by it even when it distresses people who didn’t want you to make those changes… and there will be times where people will want to help you with obscure projects you didn’t realize were useful, like recording every meal you’ve ever had your characters eat, or every time you’ve mentioned someone’s relative height, or how every minor character who’s ever died kicked that bucket, and if you accept their help (and why shouldn’t you, because you will learn a great deal!) it does not relieve you of the ultimate responsibility. The buck stops with you. It will never be anyone else’s fault, but on the other hand, it will never be anyone else’s glory, either, so at least there are compensations.
That, for now, is my advice on how to use a wiki for a writer’s bible, and the organizational properties that make mine useful. I’m about 600 content pages into this endeavor, and not even a little bit done, so I’m sure there’s a lot more to learn ahead of me…! And please, hit me with your questions; as you can see, your questions inspire entries, and I’m happy to write them. If I can spare people the problems I run into, I want to.