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

content structure #6

Open
grudelsud opened this issue Jan 26, 2018 · 6 comments
Open

content structure #6

grudelsud opened this issue Jan 26, 2018 · 6 comments
Labels

Comments

@grudelsud
Copy link
Member

new site map

website map

@acewf
Copy link

acewf commented Jan 26, 2018

considering if we could/should split members into categories ex:

  • backend
  • frontend

@andrevenancio
Copy link

yeah maybe tags would be nice. If I want to find someone who does webgl, I can filter members per technology, or tech (react, angular, etc)

@grudelsud
Copy link
Member Author

that'd be cool, the problem I see is: who is going to curate the tags? where are they going to be stored? at the moment we only have a google spreadsheet with content entered by users at submission date (that could have happened 2-3 years ago!)

It somehow reminds me of Devart, the project I did with google while at Stinkdigital, pulling content and tags directly from users Github repos. The problem (which makes it also interesting TBH) with this approach would be to have all members to create a fork of a template repo and follow some guidelines to write their own bio and tags.

It'd be cool because we could somehow opensource a way of writing a mini bio on GH and would make clear that a user is a member because (s)he has forked the organisation's repo.
Let's think about it!

@acewf
Copy link

acewf commented Jan 27, 2018

i like this idea, because it enables every member only to add is bio if they want, not forcing anyone is concerned with privacy to participate.
To feed the participants list with their repos links, we could have a JSON on this repo, where the participants can do a PR to add them.

@marcelkornblum
Copy link

It seems overly complex to me TBH. GH already allows people to create bios. And if we make all DevCon members into GH DevCon org members, there's inbuilt functionality for whether people want their membership to be public or not.

In terms of skillset tags, why dont we scrape the repos on people's GH accounts for the tags on those repos, and pull out e.g. the most common 5?

@grudelsud
Copy link
Member Author

In terms of skillset tags, why dont we scrape the repos on people's GH accounts for the tags on those repos, and pull out e.g. the most common 5?

Re. tags, it sounds more like a useless complication to me at this stage. Is it what I'm doing? what I'm interested exploring? I might have tons of private repos with the companies I work(ed) with, I might not have anything of my current interests, etc.

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

No branches or pull requests

4 participants