I'm facing an issue atm which has been taking up most of my time so far. I can't understand the way the renderer is structured/how it works as there seem to be svelte files and pug files with similar code as well as a template.pug file which I'm also not certain what it's purpose is. I would like to know the following:

• Where exactly I should import and render the richLink component?
• Where can I find a post with rich links so I can test my component?

Start here @gregorymcmillan

Split on few independent PRs/commits.

• start with pure UI (no networking and no controllers/parsers).

@markholdex @gregorymcmillan When you have a moment, please provide the article which contains a rich link element

@surajsharma If you check their docs, you will they that they don't support browser usage, check my comment one more time

@markholdex please where exactly is the issue occuring?.What component or page does the issue occur.What is the test article for

@Isaacprogi this is not a bug to occur on a specific page or component. The Problem has the Enhancement label which means it's a new feature that requires development. The title denotes that this feature is not supported at all in any of our articles.

To solve the Problem, you must provide a solution that will make sure LinkBlocks are supported.

Test article is for you to use locally to test if your implementation works or not. As the name suggest, it's for testing purposes.

@markholdex please can i have a before and after image for the problem and where it should be applicable in the test article. Also I am trying to locate the components or page of the "test article" locally but cant seem to. Does it having a different configuration from the normal c route. The route is working but am trying to find component page

Also where exactly is the link displayed as text here
https://holdex.io/c/learn/editorial-guidelines

@Isaacprogi You have the local thread available in the description, check it.

Note: Pay attention to the payload you get from API before it is rendered and you will get the point.

@Isaacprogi please take a close look at the test article and at the component design in Figma.

@markholdex Okay understood

@Isaacprogi You have the local thread available in the description, check it.

Note: Pay attention to the payload you get from API before it is rendered and you will get the point.

@georgeciubotaru not clear on this. Please can you point to

@Isaacprogi You have the local thread available in the description, check it.
Note: Pay attention to the payload you get from API before it is rendered and you will get the point.

@georgeciubotaru not clear on this. Please can you point to

@Isaacprogi please check the description of the Problem. You will find instructions to run local environment there.

When you run locally pay attention to the Payload that needs to be parsed.

@Isaacprogi You have the local thread available in the description, check it.
Note: Pay attention to the payload you get from API before it is rendered and you will get the point.

@georgeciubotaru not clear on this. Please can you point to

@Isaacprogi please check the description of the Problem. You will find instructions to run local environment there.

When you run locally pay attention to the Payload that needs to be parsed.

Okay,clear

@markholdex this is what i have so far

What should replace the title and description of the links

@markholdex this is what i have so far What should replace the title and description of the links

@Isaacprogi Good progress so far. Don't forget to link your active Pull Request with this Issue as stated in our Principles document.

Regarding the Title and description: They should be taken form the OG meta information of the link.

Okay