SCP by Series
Other SCP
Feed
Stories
Discovery
Random
I find it mildly amusing that Magnus' more advanced guide was put up before this one.
No signature defined.
Magnus's included a lot of more advanced stuff, and this one's more meant for a quick reference to point new writers to when they inevitably ask how to do that cool tab thingy you've got on your sandbox, also how do you insert audio, and what's a collapsible, etc etc. Basic info for how to use wikidot syntax, rather than make advanced fancy stuff.
My guide is much more geared towards non-wiki code, and making things look good display wise.
This is extremely useful for the nuts and bolts of how to do wiki stuff, and I think the two guides synergize really well.
also there's a couple things on here I've always been fuzzy about so thank you ghost <3
(account deleted)21 Jul 2017 15:07Along the lines of what mlister said, yeah, am I having Deja-Vu? This already exists as of a few weeks ago, I just can't remember the URL or specific page name.
Edit: Okay,found it. Looking back at it, itis geared toward advanced stuff, so both pages have their uses. Might I suggest that this page and that page be crosslinked to each other?
I'm sure this will become a resource used by SCP writers for generations to come. I'm also echoing the suggestion to crosslink between the syntax guides to maximize visibility.
Whether you like it or not, history is on our side. We will bury you!
I added a link to Magnus's essay at the top of the essay as well. Crosslinking ahoy!
Why do we need a page on the site reiterating content from theofficial Wikidot syntax page? The official documentation is perfectly readable and accessible.
if your reading this your gay
The wiki syntax pages, while….technically informative, tend to have very weak examples, or no examples of most types of parameters.
The thing I like about this page is the raw code next to the finished code, which provides good illustration of how stuff works.
You can always trawl through official documentation of any API and learn it, but generally reading a simple example will be more instructive.
I greatly appreciate and utilize this guide page for just about everything I post on this wiki.
Thank you and thank you again!
This guide works exactly as intended in my personal experience. I'm a fairly new user and this guide had me using
quoteblocks,
colored text, and all kinds of other stuff that seems to have become second nature to the vets of the site within minutes. Its an invaluable resource, and, combined with Magnus' guide, a new author has no excuse for not using proper code in their SCPs and comments.
[[div style="float:right; margin:0 2em 1em 2em; width:300px; border:0;"]]
|||| [[image URL-GOES-HERE width="300px"]] ||
||||~ ^^Caption^^ ||
[[/div]]
Why is this image format in this guide? It's been outdated for years, and is currently somewhat broken as a result of the superscript CSS update on site.
This is the better way to include images:
[[include component:image-block name=URL-GOES-HERE | caption=CAPTION-GOES-HERE]]
can I get some nice "no signatures on my forum"
sigma-9 css machine broke
understandable have a nice day
Thank you for making this page, it's really easy to understand and will help me a lot!
Probably my only issue with this guide is that it treats the two linking methods (i.e.[URL link name] vs[[[URL | link name]]]) like they're the same. If you're linking on-site, the latter is preferable, because it allows the Backlinks to function properly and provides more visibility to your article. Also, as someone who's forced to use scp-wiki.wikidot.com on their phone, it's an annoyance to click on a link and then manually correct the URL to view the site.
Could a clarification be made in this guide to emphasize that the triple-bracket method is preferred?