How To Use Forging Keys Custom Components

Congrats! You found my super-secret testing page for verifying all our fancy custom components work. These html tags can be directly inserted into the Markdown editor in the CMS for all your custom components. Note that the preview pane in the CMS will not render these elements, if I can find a way to make that work too, I will!

For the most part, partial card and deck names should work, for example using just "skippy" should work for skippy timehog

but if it's too generic you might end up with the wrong content. For example "library" might return library of babel or library of the damned. Always check your posts after publishing it to make sure everything worked properly.

Ok let's start out with a decklist:

<DeckList name="the captain of terahill"/>




I've had to build in a delay between requests for deck data as the database gets mad if you make too many requests too quickly, so the more decklists included in a post, the longer it will take for their data to be fetched. The rest of the page will load right away, but the decklists may appear blank for a number of seconds. Don't panic, but also be conservative with the number of decklists.

Now for cards, if I just want a hoverable card name:
<Card name="shooler"/>

and I get a hover image: shooler

which is inline with the rest of the text!

What if I want one big card in as a paragraph break with a caption? Just use BigCard:

<BigCard name="bulwark" caption="very crisp"/>

very crisp

But what about multiple cards in a row?? Gotcha covered with XCards:

<XCards names="anger, routine job, miasma" caption="wow those are some cards for sure"/>

wow those are some cards for sure

If you're using VueJS to power your blog, drop us a line and I'll hook you up with the components!