Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add color coding #32

Open
lolmaus opened this issue Dec 5, 2013 · 3 comments
Open

Add color coding #32

lolmaus opened this issue Dec 5, 2013 · 3 comments

Comments

@lolmaus
Copy link

lolmaus commented Dec 5, 2013

E. g. work could be red, personal life could be green, web presence could be blue, etc.

@dLopreiato
Copy link

Markdown doesn't provide a way to specify color of a text, so to do this we would have to introduce some non-markdown syntax. Unless we want to specify hardcoded set of colors that one could use.

@lolmaus
Copy link
Author

lolmaus commented Dec 6, 2013

Neither does Markdown provide a syntax for dates, approximate dates and date spans. Yet somehow you managed to support them.

I suggest that a user could be able to provide a table of categories and their colors like this:

## Categories

* default: grey
* work: red
* life milestone: white
* personal life: LimeGreen
* web presence: #12f

The JS could parse this table and hide it. Or even better, turn into a legend for the convenience of readers.

The categories can be applied like this:

- life milestone: 24/02/1955 Born
- ~1968 Summer job

Or like this:

- 24/02/1955 Born
- ~1968 Summer job [work]

@lirsacc
Copy link

lirsacc commented Dec 7, 2013

This could integrate well with #34 from michaelowens.

I made a quick try (see here) with his old code and a tag object in config.json (not life.md to keep parsing of the events simple).
Doesn't draw a legend for now, but could easily be added to the step.

In the interest of keeping things simple, I would also keep this limited to colors. IMO a custom stylesheet seems more appropriate for a finer control of the tags don't you think ?

I will update once #34 has been merged to account for the latest changes and make a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants