indieweb / indieweb/indiewebify-me

h-entry validator missing content suggestions unclear

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

Nobody has claimed this yet.

Dominant language
CSS
Stars
188
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Using the h-entry validator for my site (https://scottnm.com) -- which I've recently added h-entry markup to -- shows me a somewhat unhelpful validator output?

Image

it seems to be able to find the h-entry tags correctly, but it looks like its suggesting it can't find any of the sub-tags I've already added and the h-entry it has parsed appears to be entirely empty??

I'm expecting it to have found p-name, u-url, and p-summary tags at least on quite a few of the h-entry's. e-content *is* missing.

I think this is a mix of a bug report to ask what's going wrong here and a feature ask that it'd be helpful if you could view the markup that the validator was currently reading and saying was missing the tags.

Here's some example h-entry HTML markup that I would expect the validator to find on my page

```html


  • Avipaper.p8







    A Pico-8 demo. Fly a paper airplane through some targets.


    Tools: pico8, lua

  • ```

    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.

    Research direction

    Start by reproducing the validator output for https://scottnm.com and compare its parsed h-entry data with the example HTML in the issue. Trace why p-name, u-url, and p-summary are not shown, while noting the requested ability to view the markup being validated; done means the existing tags are reported correctly and the requested inspection behavior is addressed.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    css, html
    Domain
    testing, web-dev
    Issue type
    Bug
    Difficulty
    4/5
    Estimated time
    3-5 days
    Activity status
    Stale
    Clarity
    Mostly clear
    Newbie friendliness
    38/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.