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

Integrate presentations #24

Open
godber opened this issue Mar 27, 2019 · 4 comments
Open

Integrate presentations #24

godber opened this issue Mar 27, 2019 · 4 comments

Comments

@godber
Copy link
Member

godber commented Mar 27, 2019

It would be awesome if by including some small snippet in a presentation directory here:

https://github.com/desertpy/presentations

Like .meta.json:

{
  "author": "Austin Godber",
  "title": "Stream Processing with Python and Kafka"
...
}

The presentation got automatically included in the website's presentation page.

@godber
Copy link
Member Author

godber commented Mar 27, 2019

@nelsonjchen if you feel like thinking about a new challenge.

@nelsonjchen
Copy link
Contributor

nelsonjchen commented Mar 27, 2019

That sounds like a great idea. Maybe we can crowd source the tagging and metadata for a few minutes during a meetup.

@godber
Copy link
Member Author

godber commented Mar 28, 2019

I am less concerned about back filling the tagging than devising the mechanism and implementing the code so that future presentations get managed automatically.

Not that your suggestion of crowd sourcing it isn't a good idea. In fact, in some way's it's a great idea. Since we have a lot of members who are new to programming and new to git ... we could use it as a teaching tool. Say someone new comes on a Saturday, we can get them setup with git, github account, and help them send a pull request. Really great idea Nelson.

That, of course, assumes the interface and code exists.

@godber
Copy link
Member Author

godber commented Mar 28, 2019

Another thought I just had ... instead of a separate .meta.json file it might make more sense to require that every presentation linked to follow these rules:

  • have it's own directory in the presentation repo with the directory name <person>-<topic slug>-<iso date>. Note that we never parse the directory name for info, that's just for consistency.
  • have a README.md the contains the jekyll style fore-matter:

This fore-matter would provide the metadata we need in an unobtrusive way that adds context to something that should already be there (a README.md).

Again, this is just a suggestion of a possible solution.

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

No branches or pull requests

2 participants