indieweb / indieweb/indiewebify-me

Detect likely missing or bad p-name markup and provide a warning

Open
#30 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
188
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Here's a really simple heuristic for detecting whether the p-name of an h-entry is "bad" in some way, i.e. either missing and thus implied (could check for that in the markup explicitly), or errantly exceedingly big:

if (content && (strlen(name) >= strlen(content)) { /\* warn about bad or missing name property, likely same as content or includes of content and UI beyond it */ }

Would be great if indiewebify.me validate-h-entry could detect this and provide a warning, e.g. here is a real world test case:

http://indiewebify.me/validate-h-entry/?url=http%3A%2F%2Fwerd.io%2F2014%2Fegg-brooklyn

Note how big the p-name property on the h-entry is here (bigger than the content)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the h-entry validation at the linked indiewebify.me/validate-h-entry URL and compare the real-world example. Trace where p-name and content are evaluated; done means the validator warns when p-name is missing or at least as large as content, including the example case.

Written by the indexing model from the issue text.

Assessment

Domain
web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.