Skip to content
This repository has been archived by the owner on Aug 12, 2020. It is now read-only.

Inconsistent image locations in design repos - likely understood #33

Open
narration-sd opened this issue Mar 31, 2020 · 0 comments
Open

Comments

@narration-sd
Copy link
Contributor

narration-sd commented Mar 31, 2020

In the early repos, there are problems with image location. The mit-emergency-ventilator is a good place to observe them.

  • there are two different img/ folders: one at top level, and one within the docs/ folder.
  • very possibly this is because of inconsistency in the way image links may be written in the markdown documents, it occurs to me - some using one location, some using the other, some using web-linked images but the repo wanting to possess them. This is work for the person collating the archives, but maybe necessary
  • However this is done in practice, we need consistency so that the Viewer ability for clicking through the images quickly always knows where to find them. That's so users can rapidly get their visual sense of a design,
  • then having all images always in the /img folder at top makes sense for viewing the set of images, and Viewer will use only that for its coming quick-scan through images.
  • in the markdown image link correctors the companion Incomplete links for image locations in in design repo content #32 (comment) issue raises, the in-document link will be parsed, and that will allow discovery and handling of local /docs/img file links, as well as the web links currently handled. We have to do it because the best available Markdown parser doesn't.

This issue the exists to verify and assure the dual image locations process.

@narration-sd narration-sd changed the title Inconsistent image locations in design repos Inconsistent image locations in design repos - probably understood Mar 31, 2020
@narration-sd narration-sd changed the title Inconsistent image locations in design repos - probably understood Inconsistent image locations in design repos - likely understood Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant