Improve README layout and structure #1

Open
opened 2020-08-07 12:13:40 +00:00 by circlebuilder · 0 comments

There are many ways to structure this list and many categories still missing. This issue is for discussion of improvements still needed to have a solid basis to extend from.

One thing I was thinking about was splitting into informational entries and code project entries such that:

  • Information entries are lines of text, new entries added to the bottom, and maybe showing month + year at the end e.g. (Aug 2020).
  • Code projects have a table layout with columns Project, Description, License, Technology / language e.g. React, Typescript.
There are many ways to structure this list and many categories still missing. This issue is for discussion of improvements still needed to have a solid basis to extend from. One thing I was thinking about was splitting into informational entries and code project entries such that: - Information entries are lines of text, new entries added to the bottom, and maybe showing month + year at the end e.g. `(Aug 2020)`. - Code projects have a table layout with columns Project, Description, License, Technology / language e.g. `React, Typescript`.
circlebuilder added the
help wanted
label 2020-08-07 12:13:40 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: teaserbot-labs/delightful-linked-data#1
There is no content yet.