How Markdown flows through FeedLand

Open
#269 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
html, markdown
Domain
frontend, web-dev

Research direction

Start with the FeedLand feed URL and the planned feedlandHome rendering path, comparing the supplied timeline image, feed XML, and source:markdown content. The issue provides no repository file, test, concrete change, or completion criterion, so the expected documentation outcome would need to be clarified first.

Written by the indexing model from the issue text.

Description

I have a fictitious user, Bull Mancuso, who uses FeedLand. His outgoing feed is here:

http://data.feedland.org/feeds/bull.xml

To start the exploration, I added a titled item with a single bit of styled text in it.

image

This is what the item looks like in the timeline.
image
And this is what it looks like in the feed.
<item>
      <title>First Markdown test</title>
      <description>I want to take a look at how Markdown is generated by FeedLand and how it displays it. This is where we start, with a post with a <strong>single bit</strong> of marked up text.</description>
      <pubDate>Thu, 17 Aug 2023 14:56:56 GMT</pubDate>
      <link>https://feedland.org/?item=5015542</link>
      <guid>https://feedland.org/?item=5015542</guid>
      <source:markdown>I want to take a look at how Markdown is generated by FeedLand and how it displays it. This is where we start, with a post with a **single bit** of marked up text.</source:markdown>
      </item>

This all looks exactly as I wanted it to. Next step I'm going to see how the rendering if the item takes place in feedlandHome. I want to see the actual code that's turning the Markdown text into HTML. Back in a bit..

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.