Support Custom component

[trusktr]

Solution A:

---

<!-- component-name -->
...
<!---->

---

Solution B:

---

:::component-name
...
:::

---

Solution C:

---

<docsify name='component-name' attr=''>
...
</docsify>

---

[trusktr]

@anikethsaha What's the motivation here? Was there another issue describing this with more detail? (I converted the 5.0 board's card into this issue, but we can close this if there's already another issue)

Regarding components, the I believe the markdown already support Vue components, so perhaps that's good enough? Plus the markdown support HTML, so we can also just use Custom Elements (here's my Custom Element lib, @lume/element (disclaimer: I made it)).

Let's better understand the goals, so that we can evaluate if we can just use Vue or Custom Elements, which already give us comonents.

Maybe the goal is to have outside markdown files, and be able to nest the inside other markdown files?

[anikethsaha]

I am not sure about this. was it mentioned in v5 roadmap issue ?

I think we can close this. it was never in the roadmap.

cc @trusktr

[trusktr]

It was a simple card that I found inside 5.0! project, then I converted it into an issue.

Yeah, it can wait. Was there a PR relating to this?

[anikethsaha]

I dont think so 👍