![]() This is also used for making one cell take up more columns such as where I’m using a whole row as a title line. The ‘fun’ is when you start wanting to combine two cells to either make room for more stuff, such as two longer words, or giving the implied use of one header to two lower cells. With just that you can make a stat block.ĮG |Brawn|Agility|Intellect|Cunning|Willpower|Presence| Vertical breaks are dealt with by line breaks in the edit field, what’s on one line stays on that line and what is on the next line goes on the next line. The very basics are vertical lines | and they are the start and end of a cell, they split up everything you want to split into another cell on the same row. ![]() This is allowing extra information to be stored while not making a single column become too wide and looking ‘weird’. Towards the bottom I have full across lines that are there for equipment. If you have two rows of things that people are looking at and they are aligned vertically it’s easy to pick out what is being done, and easier to maintain while adding more stuff without reformatting, adding layers and layers to a big table club house sandwich.Īs you can see I have double width columns for skills/talent names as well as implying one thing describes two separate stats. The reason you want it to be as condensed vertically as possible is ease of grouping. Underneath the header cells can go the values for each header and this makes it easy to figure out what number go with which attribute. Surprisingly enough the usual width of stat blocks works, either the D20 eight or the FFG Star Wars six. ![]() This is the result of my meddling with my little table. Textile has a few cute tricks that I’ve learned to use. The Obsidian Portal back end automatically widens the column to the width of whatever is in there, a long sentence will become a really wide cell which makes for a very wide column. The thing to remember is width you want to make it as easy to remember the width as possible. ![]() Tables are a little weird but easy to implement if you take time to deal with them. Quick links can be modified to display whatever you want by placing a | between the link and the description.Įxamples: ] Quick links are great, but you can do another thing to them that makes them even better. The easiest way of dealing with this is use a short but practical name that can be chosen from a list. The Void, Lepskin Void, and The Lepskin Void all would go to different places. The problem stems from long page names and a desire for nicknaming things. I can link to The Lepskin Void by putting square brackets around it like so ] and it becomes hyper linked. This is why you want to have the name as short as possible and preferably unique. Wiki Quick Links are a little trickier because you can’t create slugs for them. The colon is what tells Obsidian Portal that the link is for a character. ] will bring up and display Icor Brimarch and link to his page with decidedly less typing and creating a link. The reason to keep the slugs and the titles short is the ease of Quick Links.Ĭharacter Quick Links can be put in with a double square bracket and a colon before the slug. Tags and the insert links can help, but become a hassle for simple entry. Having long wiki titles and character names becomes unwieldy when more and more entries show up to look through. Linking can be easy if information is treated simply. It’s the period that tells textile the random stuff that came before are commands to follow. Textile lets you mess around with commands in its language and combine different commands easily, you can smash together alignment, bold, and size changes all at once with a single leading string of seemingly nonsensical characters followed by a period. The page is already sectioned off into two major halves, anything more no one is reading.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |