Skip to content
This repository was archived by the owner on Nov 21, 2018. It is now read-only.
This repository was archived by the owner on Nov 21, 2018. It is now read-only.

Avoid nth-child for selecting p's in rendered markdown #175

Closed

Description

@aravindet

I understand why it is needed now, but this is likely to be hard to maintain in the long run. Localizers might add new paragraphs or change the structure in unpredictable ways.

There could be two ways to fix this:

  1. Use embedded HTML in the markdown files (translators have to be careful not to change them), or
  2. Split the homepage content into two markdown files (content-above-logo, content-below-logo), implement the logo box in the template HTML and use template.json strings to localize text within it.

Activity

  1. therebelrobot commented on Feb 12, 2015

    @therebelrobot
    Contributor

    That's a good point. I felt a little part of me die inside when I programmed that. I'll look into that as I do the template refactor this weekend.

  2. Fishrock123 commented on Feb 12, 2015

    @Fishrock123
    Contributor

    Saw this today when looking at things. The version box should probably be mostly html. Styles should be generic for everything else and applied to header levels when necessary.

    Extracting the header and footer into their own files for each translation may help.

  3. therebelrobot commented on Feb 12, 2015

    @therebelrobot
    Contributor

    Yeah, I was trying to go with a generic-as-possible template, but we will need to expand it a bit.

  4. Fishrock123 commented on Mar 13, 2015

    @Fishrock123
    Contributor

    Should be fixed in #276

  5. snostorm commented on Mar 13, 2015

    @snostorm
    Contributor

    I'd be tempted to close this now even with #276 not merged, as it will be resolved soon. Or we can keep this until all groups move to the new homepage format?

  6. fhemberger commented on Jul 1, 2015

    @fhemberger
    Contributor

    Pinging @nodejs/iojs-ar @nodejs/iojs-bg @nodejs/iojs-bn @nodejs/iojs-cn @nodejs/iojs-cs @nodejs/iojs-da @nodejs/iojs-de @nodejs/iojs-el @nodejs/iojs-es @nodejs/iojs-fa @nodejs/iojs-fi @nodejs/iojs-fr @nodejs/iojs-he @nodejs/iojs-hi @nodejs/iojs-hu @nodejs/iojs-id @nodejs/iojs-it @nodejs/iojs-ja @nodejs/iojs-ka @nodejs/iojs-ko @nodejs/iojs-mk @nodejs/iojs-ms @nodejs/iojs-nl @nodejs/iojs-no @nodejs/iojs-pl @nodejs/iojs-pt @nodejs/iojs-ro @nodejs/iojs-ru @nodejs/iojs-sv @nodejs/iojs-sw @nodejs/iojs-ta @nodejs/iojs-tr @nodejs/iojs-tw @nodejs/iojs-uk @nodejs/iojs-vi:

    If you haven't already done so, please change to the new homepage format using template.json (see content/en).

    (Phew, we have to come up with something better than this)

  7. fhemberger commented on Jul 5, 2015

    @fhemberger
    Contributor

    Languages, which need to be updated:

    • @nodejs/iojs-el (PR waiting for +1)
    • @nodejs/iojs-es
    • @nodejs/iojs-fi
    • @nodejs/iojs-he
    • @nodejs/iojs-it
    • @nodejs/iojs-ko (PR waiting for +1)
    • @nodejs/iojs-no (PR waiting for +1)
    • @nodejs/iojs-pt (PR waiting for +1)
    • @nodejs/iojs-ru
    • @nodejs/iojs-tr (PR waiting for +1)
    • @nodejs/iojs-uk
    • @nodejs/iojs-tw (PR waiting for +1)
    • @nodejs/iojs-vi (PR waiting for +1)
  8. added a commit that references this issue on Jul 5, 2015
  9. stringparser commented on Jul 5, 2015

    @stringparser
    Contributor

    For @nodejs/iojs-es the change was addressed in #362, we are missing the links.rss though so I'll do PR for this on a bit

  10. fhemberger commented on Jul 5, 2015

    @fhemberger
    Contributor

    @stringparser Ah, sorry about that. I just had a quick look which languages still had the index.md in place. If the template.json version of the home page works fine for you, please remove the old index file.

  11. stringparser commented on Jul 5, 2015

    @stringparser
    Contributor

    @fhemberger no problem. You are right we still have the index.md :), I'll remove it.

  12. added a commit that references this issue on Jul 11, 2015
  13. fhemberger commented on Sep 20, 2015

    @fhemberger
    Contributor

    I guess this won't be fixed for all i18n groups, so I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions