Skip to content

Latest commit

 

History

History
69 lines (36 loc) · 2.08 KB

File metadata and controls

69 lines (36 loc) · 2.08 KB

Journal

2023-01-14 ~ @theo-armour

Finally noticed @javarome's repo:

Added GitHub Pages capability.

Added relevant text and links to plain-javascript readme.

Added new discussion item

Need:

  • favicon
  • 404.html

2023-01-06 ~ @theo-armour

  • Add features I look for in Kitchen Sink efforts

2023-01-02 ~ @theo-armour

Added @javarome as an owner

Added brainstorming as a file and populated it with some thoughts

Open a discussion item

Moved my files to a new repo: https://github.com/plain-JavaScript/kitchen-sink

2022-12-23

Added descriptions to four articles

Started a Target Audience section

2022-12-22

Where do you draw the line between JavaScript and plain JavaScript?

Time will tell. Observations will be made. Guidelines and rules will be created. Content will be updated and amended.

Until then, it's complicated.

Some thoughts:

  • I'd rather start with being more inclusive then less. [There is Wikipedia concept around this. What is its name?]
  • In whatever topic being addressed where there is significant "fully-leaded" JavaScript content, it will be nice to provide links to relevant "awesome lists" on that topic
  • If for some reason, a link is dropped from a topic because it is no longer seen as relevant, then I hope it may still appear in an archive somewhere - with a not indicating the reason why the link was demoted. Knowing why something is deleted may be as important as to why it was added.

Done

  • Reconstitute the sections under major categories: Reference, background, resources, sources. etc
  • Add links

2022-12-18

This is my second day on this project. It is a work-in-progress. My goal is to spend an hour or so a day in this effort - until such time I feel that the effort is worth sharing. ❧ Theo Armour