Giters

abelljs / abell

A Low-Level, Framework Agnostic, Highly Flexible Static-Site-Generator to help you build Static Sites on a smaller learning curve 🌀

Home Page:https://abelljs.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Inlined Markdown

saurabhdaware opened this issue · comments

commented

Describe the solution you'd like

<html>
 <body>
   <h2>About Me</h2>
   <AbellMarkdown>
     Hi, I am **Saurabh**. I love making websites. 
     You can follow me on [Twitter at saurabhcodes](https://twitter.com/saurabhcodes)
   </AbellMarkdown>
</body>
</html>
commented

Dropping it here for future reference

<AbellMarkdown source="../content/index.md" />

suggested by @anuraghazra on Discord

commented

Maybe also directly fetch the content by passing an url :-

<AbellMarkdown fetch="https://md.com" />

or with the same prop

<AbellMarkdown source="https://md.com" />
commented

I think we should call it path instead of source and URLs may cause confusion. Here's why:
In HTML, when we use, <img src="./hello.jpg"/> and then change the hello.jpg image, it changes in the website.
But in abell, if we say

<AbellMarkdown source="https://example.com/myblog.md" />

and then make changes in markdown file and push it. It won't change in Abell's website since it needs a rebuild and the source is only read during the abell build

So I think, for now, we can leave URL markdowns to be handled by source plugins since that syntax may push users to link external markdown files and expect them to change when the markdown is changed.