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 tags to resume #10

Open
suramya-shah opened this issue Sep 23, 2017 · 4 comments
Open

Add tags to resume #10

suramya-shah opened this issue Sep 23, 2017 · 4 comments

Comments

@suramya-shah
Copy link
Contributor

It will be nice to have tags on resume that will help in filtering purposes and applying to varying jobs

@stp-ip
Copy link
Member

stp-ip commented Feb 13, 2019

There was quite a bit of discussion on this.

My thinking currently is to have tags, that get shown as actual tags on themes etc. for the main sections etc., but for filtering purposes we use keywords.

Tags: public
Keywords: private, for filtering

A bit more context in this thread and the comment: jsonresume/resume-schema#203 (comment)

Happy to discuss this further.

@stp-ip stp-ip added the revisit label Feb 13, 2019
@stp-ip
Copy link
Member

stp-ip commented Mar 15, 2019

@ArmanMazdaee I think this needs a bit more discussion. Let's jump into this in parallel.

A few things that need to be cleared up first:

  • split tags and keywords?
  • which one is public and private aka used for filtering or showcasing?
  • which section/subsection to add this to?
  • different filter mechanism such as a similar one to our i18n idea Discuss i18n for schema #81?

@stp-ip
Copy link
Member

stp-ip commented Apr 3, 2019

metadata.tags = [{
    "pro-bono": {
       "references": [
       "work['greenpeace']",
     ]
  }, {
    "greenpeace": {
        "references": [
          "projects['volunteering party organization']",
          "events['demonstration 123'].talks['saving cats']"
      ]
}]

@stp-ip
Copy link
Member

stp-ip commented Apr 23, 2020

What we currently have is keywords being public.

The next step would be using a filter and tagging syntax within the meta section.

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

Successfully merging a pull request may close this issue.

2 participants