an-empty-string / an-empty-string/website

feat: map item type

Open
#24 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
HTML
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

places I've been, using the items framework; this gets us AP integration for free

these are kind of a type of blog post; I think we want long text bodies / support for one item per file, using yaml frontmatter + markdown body, where the body becomes a regular property of the item, as html

they would render into a map, clicking on a point loads more detail into a side panel (so it works best on desktop, idk what mobile looks like...)

they have tags and coloring rules, so we could have e.g. bell towers, restaurants, other significant places all be different colors

they have optional properties that we can pick up and render a special way in the pane, e.g. dove's guide tower IDs, URLs, maybe star ratings...? not all props will make sense for all items, even of the same type/tag

are they searchable somehow...? are items searchable more generally as in the bookmarks list?

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 inspecting the existing items framework and the blog-post-like content model referenced in the issue. Determine how YAML frontmatter and Markdown bodies are currently handled, then clarify the map, side-panel, tagging, coloring, optional properties, and search requirements before implementation. Done means the agreed item type and its rendering behavior are documented and working.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, markdown, yaml
Domain
content, frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.