scribe/src/pages/articles/show_page.cr

class Articles::ShowPage < MainLayout
  needs page : Page

  def page_title
    page.title
  end

  def content
    h1 page.title
    if subtitle = page.subtitle
      para subtitle, class: "subtitle"
    end
    article do
      section do
        mount PageContent, page: page
      end
    end
  end
end
Add basic response (except images) The basic idea here is to fetch the post with the medium API, parse the JSON into types, and then re-display the content. We also have to fetch each media object as a REST call to get things like embeded iframes. 2021-05-01 23:26:48 +02:00			`class Articles::ShowPage < MainLayout`
First step rendering a page The API responds with a bunch of paragraphs which the client converts into Paragraph objects. This turns the paragraphs in a PostResponse's Paragraph objects into the form needed to render them on a page. This includes converting flat list elements into list elements nested by a UL. And adding a limited markups along the way. The array of paragraphs is passed to a recursive function. The function takes the first paragraph and either wraps the (marked up) contents in a container tag (like Paragraph or Heading3), and then moves onto the next tag. If it finds a list, it starts parsing the next paragraphs as a list instead. Originally, this was implemented like so: ```crystal paragraph = paragraphs.shift if list? convert_list([paragraph] + paragraphs) end ``` However, passing the `paragraphs` after adding it to the already shifted `paragraph` creates a new object. This means `paragraphs` won't be mutated and once the list is parsed, it starts with the next element of the list. Instead, the element is `shift`ed inside each converter. ```crystal if paragraphs.first == list? convert_list(paragraphs) end def convert_list(paragraphs) paragraph = paragraphs.shift # ... end ``` When rendering, there is an Empty and Container object. These represent a kind of "null object" for both leafs and parent objects respectively. They should never actually render. Emptys are filtered out, and Containers are never created explicitly but this will make the types pass. IFrames are a bit of a special case. Each IFrame has custom data on it that this system would need to be aware of. For now, instead of trying to parse the seemingly large number of iframe variations and dealing with embedded iframe problems, this will just keep track of the source page URL and send the user there with a link. 2021-05-16 20:14:25 +02:00			`needs page : Page`
Add basic response (except images) The basic idea here is to fetch the post with the medium API, parse the JSON into types, and then re-display the content. We also have to fetch each media object as a REST call to get things like embeded iframes. 2021-05-01 23:26:48 +02:00
Add page title to <header> <title> 2021-09-04 20:44:05 +02:00			`def page_title`
			`page.title`
			`end`

Add basic response (except images) The basic idea here is to fetch the post with the medium API, parse the JSON into types, and then re-display the content. We also have to fetch each media object as a REST call to get things like embeded iframes. 2021-05-01 23:26:48 +02:00			`def content`
Display title and subtitle Also wrap the content in an article for semantic formatting tufte.css requires that content is wrapped in an <article> and at least one <section>. There's no way of determining new semantic sections so there is only one. 2021-08-15 21:01:18 +02:00			`h1 page.title`
			`if subtitle = page.subtitle`
			`para subtitle, class: "subtitle"`
			`end`
			`article do`
			`section do`
			`mount PageContent, page: page`
			`end`
			`end`
Add basic response (except images) The basic idea here is to fetch the post with the medium API, parse the JSON into types, and then re-display the content. We also have to fetch each media object as a REST call to get things like embeded iframes. 2021-05-01 23:26:48 +02:00			`end`
			`end`