Re: [jlreq] Use /docs/ as store of refrence materials for discussions etc., and mention in README (#292)

> I think that it's a problem to have a copy of the simple-ruby document in this repo. Given that there is some history (https://github.com/w3c/jlreq/commits/gh-pages/docs/simple-ruby/index.html) it's perhaps not appropriate to simply delete the files. However, i think that we should remove all the text from index.html and replace it with a line that says "Go look over here".

How should we deal with the accessibility part of the simple-ruby document (see https://github.com/w3c/jlreq/pull/271#issuecomment-851207232 )?

(FYI - Murata-san is working on [a series of new documents about ruby accessibility](https://github.com/Japan-Daisy-Consortium/documents/wiki) in the Japan DAISY Consortium and plan to create a W3C WG Note based on these documents. Maybe we can work with Murata-san to see if these documents and the accessibility part of simple-ruby can be integrated into a new document?)

-----

> I see that @kidayasuo has added a document already to the /docs folder. Seems to me a good idea.
> 
> If this was just the odd image or other isolated resource that is kept in the repo for safe-keeping, i would suggest using a new directory called 'resources'. But @kidayasuo's addition is clearly a document, so i think that's a good addition to the 'docs' folder.
> 
> I also think @kidayasuo did the right thing in creating a subfolder (spacing_property) for his document, which can contain any other files needed for his document, and keep the higher level tidy and clean.
> 
> So, bottom line for my initial reaction: yes, put documents in /docs, but put _random_ images etc in /resources.

+1

-- 
GitHub Notification of comment by xfq
Please view or discuss this issue at https://github.com/w3c/jlreq/issues/292#issuecomment-894599768 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 7 August 2021 03:52:18 UTC