As suggested by @khalidabuhakmeh - consider searching all of GitHub for a file like discoverdotnet.yml and use the ones we find to supplement the project data in this project. Some considerations:

• Security will be a concern - when all the data is here it has to go through review, not so if pulling data. Will need to make sure all content that gets output is properly escaped.
• Need to handle malformed files. Again, because data here is reviewed it’s not a problem, but could have bad data from external files.
• Consider quality of projects - how to make sure folks don’t just add hundreds of “Hello World” projects? Some minimum bar to include them?
• Tag taxonomy might be a problem, consider implementing a tag white list and only use tags from that. How to warn if a tag is used that isn’t part of the whitelist?
• If a data file exists both in here and at the originating repo, which one takes precedence? First thought is that the external one is always used first but any values from it are overwritten by equivalent properties from the internal one. That way we can override bad data here, but supplemental data like chat, donations, etc. and get pulled from the external file even if we define the project here.

Output general-purpose JSON files for all items to an "API" and document them. Consider two versions of each type of item: one JSON file that contains all the data and a set of JSON files that's been pre-paged (with page number, total pages, and total count for each)

Not sure what this would look like and how it would get triggered. Maybe at generation time, or maybe as a separate Azure Function or something.

Consider defining a tag white list for project tags. That should help keep them clean, especially if #17 is implemented. Make sure the white list is displayed for folks making contributions.

The discover card supports them, but they're not being dumped in the JSON

Could just link initially, but look at getting deeper data like we do for NuGet packages

Add a section on the homepage (and feed, api) called Hot Bits that lists new NuGet (and Choco?) packages from known projects in the last 24/48 hours.

Pull from GitHub once Octokit supports (may already in most recent version). Fallback YAML property. Add filters to grid and display on cards.

Should Tweet out content from the site like the daily discovery, recent blog posts, issues, random projects, etc.

A reddit user noted that the site doesn't work in IE, and they're not wrong. I took a quick look to see if it was easily fixable and got part way there. However, there are still some layout issues with the footer not being pushed down (possibly due to flex: 1 usage) and cards not rendering.

At this point I've spent all the time I can on this unless there's a large outcry for IE support. Otherwise, I welcome someone from the community who's much better with the front-end and JavaScript to take a look.

Loose brainstorming follows, will refine as I go:

• Static site generated by Wyam

• Generated nightly (or even more often) on a schedule by AppVeyor

  • Metadata for projects (stars, forks, etc.) will be regathered nightly for every project

• Hosted at Netlify

• Similar idea and presentation to staticgen.com

• ✓ Projects will be represented as .md files so an optional description can be provided as page content

  • ✓ If no page content, use the rendered readme file from GitHub (if available)

• ✓ Home page

  • Be sure to link to main .NET site and .NET Foundation

• ✓ "Daily Discovery" features a single OSS project per day

  • ✓ Featured on the top of the home page
  • Tweeted out each night (from dedicated Twitter account, dotnetoss, ?)
  • ✓ Specified by a particular date value in front matter like Discovery in the project .md file
  • List of n previous days discoveries under today's discovery
  • Link to full project archive under most recent days

• ✓ Project details page

  • ✓ Each project has it's own page
  • ✓ Section for metadata, maybe in a sidebar
  • ✓ Get metadata from GitHub: stars, forks, issue count, commit count, earliest commit date?, most recent commit date?
  • Specify additional metadata in the project .md front matter: primary language (C#, F#, VB, ???), tags (how to reconcile with GitHub topics?), web site (or use GitHub value if not specified), Twitter handle, chat link (Gitter/Slack), NuGet package, ???
  • Get readme content from GitHub and mirror, possibly as tab in main content section
  • Some way to show help wanted issues (how to identify them? by indicating the used help wanted label in project .md front matter?)
  • Should some sort of commenting system be supported? Might be cool, or might be just another place maintainers would have to keep an eye on (bad)
  • Display other projects from the same owner

• Full project archive

  • Separate section from home page
  • Includes daily discoveries as well as not-yet-featured projects
  • Card interface like StaticGen
    • Same card UI for archive and daily discovery section on home page
  • How to deal with list when it gets long (paginate, endless scroll?)
  • Sort full archive by day featured, project name, stars, forks, issue count, ???
  • “Shuffle the deck” option to display in a random order (maybe this should be default?)
  • Filter full archive by primary language (auto-populated from front matter values)
  • Filter full archive by tags (auto-populated from front matter values)

• Help wanted issues

  • Aggregate over all known projects
  • Search and filter
  • Projects that might be in trouble and need help (long time since last commit, how else to determine?)

• Form to suggest new projects

  • Should automatically submit as a PR - maybe using https://staticman.net/ or similar
  • Each type of data (project, blog, etc.) will need a slightly different form to match the expected front matter - put them all under /add

• Blogs

  • With an aggregate blog roll
  • Download an opml with all the blogs
  • A daily recap of all new blog posts the previous day

• Broadcasts

  • Podcasts and Video (YouTube Channels, etc.)
  • Pull latest from RSS feeds

• Resources

  • Tags and filters to help find stuff
  • Non-personal Twitter accounts and bots
  • Other sites

• People

  • Detail page could link to blogs/projects section, list data from GitHub if given username
  • Not too sure about this one - keeping a database of all community members would be tough, and how to identify them?
  • Interview with community members featuring same questions for everyone - feature one a week (?)

• Events

  • Conferences, users groups, live coding sessions
  • Distinguish between event (user group, conference) and meeting (instance of the conference this year) - keeping a full database of meetings might be too much trouble, does Meetup have an API? Could at least pull from that for upcoming meetings of user groups...

• Email newsletters

  • Daily discovery
  • Previous days blog posts and broadcasts
  • A daily version and possibly a weekly digest

• RSS feeds

  • Daily discovery
  • Previous days blog posts and broadcasts

Any more ideas? Add them as comments!

Could just link initially, but look at getting deeper data like we do for NuGet packages

Use vue2-leaflet. Should reflect the current filtering applied to the grid, and should filter the grid based on viewport.

https://discoverdot.net/projects/nake
May be loosely related to #67, but seems less likely since that issue was closed with a recent commit.

Update the URL to include any filters or sorts applied when browsing projects.
It would be nice to be able to link someone directly to, for example, the CLI tag if you need a new library for a CLI parser.

e.g.

https://discoverdot.net/projects/?tags=CLI,PDF

Until Wyam supports includes, move common helper code to a library that Wyam can reference. Use the Cake build script to compile the library prior to running Wyam.

Either use something like staticman.net or pre-populate a GitHub PR from form data.

Support multiple NuGet packages for each project. If a NuGet package ends in .*, look up all the NuGet packages with that pattern and include them on the project page. Will need to revise the way packages are presented to allow for multiples (and probably rename the "Versions" tab to "Packages"). Include package descriptions for each package to help distinguish.

Add a filter to limit projects to only those that are "active" (need to define what that means). That way if users don't want to see older projects they can hide them.

Hi, you have a problem with feed from my blogs:

http://amerlin.keantex.com/feed/
http://www.dotnettortona.net/feed/

If can help you, they are two wordpress blog.

Thanks!

Hi,

First, thanks for this awesome site 👍!

The last 3 recent discoveries all have the same date (June 2, 2018). I amready noticed it yesterday but it was only the last 2 recent discoveries (the date was June 1, 2018).

Several non-English blogs have been submitted. Not sure about the best way to handle these yet so I've been requesting we add them to the resources section for now. I'd like to include them, but the concern about adding them in the main blog section is that will make it multi-language which means it'll be a toss-up whether you know the language when you open one. At least with English it's consistent.

One approach would be to add them with a Language metadata value (English assumed if omitted) and then hide non-English blogs initially and from the feed. That way if you understand and want to include another language you can elect to do so, but the blog section stays single-language by default.

Saw https://awesometalks.party/ and got inspired. Consider something similar.

Hello,

I think about create a flag for Call4Paper in the events section with a link to this CFP.

What's do you think about this idea?

Best regards,

Adrien Clerbois

I forked the repo, but have no idea how to get wyam to build what's there. A simple how to get started would help :)

If you look at the Events page, there are events in the past, which isn't really helpful

https://discoverdot.net/events/

Maybe add a filter to check current date and date of event?

Can get the full set of supported frameworks once we can look at all NuGet packages (#15)

Perform a validation build for PRs:

• Pull existing data from the API so we don't need to issue any GitHub/NuGet/etc. queries (#25)
• Load YAML files and skip the ones we already got data from the API for
• Issue web service requests to get a complete document for the new ones (use the shared helper code from #24 so requests are the same as a normal build)
• Do verification (no duplicate titles, no duplicate source repos, existing tags, etc.)

Especially important for things like resources, groups, events, etc. where there’s no on-site detail page. Need to handle situations like cards from the Meetup API that don’t have a backing YAML file.

When I navigate to my blog link https://discoverdot.net/blogs/laurentkempe I see a white page!

btw @daveaglick Thanks for including my blog on your site 👍

Show any posts, episodes, etc. that relate to the current project. If no results, hide the tab.

There's been a lot of feedback on Reddit that the homepage is confusing and has too much data: https://www.reddit.com/r/csharp/comments/8lahhq/discover_net/dze7sjr/ - consider how it might be simplified or cleaned up without loosing quick access to important data and still highlighting functionality like help wanted issues.

Not sure if this should be a separate section or just a filter in the projects section. Here's a good list to get started: https://github.com/natemcmaster/dotnet-tools

Needs to key off of GitHub data - if not a GitHub repo, should owner be a YAML property?

There is an event yaml file for c-tech but it is not appearing in list:
https://github.com/daveaglick/discoverdotnet/blob/master/input/data/events/c-tech.yml

I can't spot a mistake.
I can help with this if you tell me where I should look.

Some blogs and broadcasts are focused on a specific project. I don't think it makes sense to include these in the general blog/broadcast areas - if we get enough of them they'll overpower the more general information. Instead, should add a project field to blogs and broadcasts that, when set, will hide the feed from the general section (perhaps with a filter so you can turn them back on if you want?) and instead include it on the project page.

Hi!

Nice work!

I wanted to ask you what is your opinion on non-English material. For instance, I wrote nearly 400 posts about dot net tips in Hebrew (located here).

Would it be ok to add this as a resource (it is not very active as a blog)?

Elad

Once multiple NuGet packages are implemented (#15), consider adding Choco packages to the mix

We've got enough data between project owners, NuGet owners, feed authors, etc. to get a pretty good picture of people. Additional data like Twitter accounts and avatar images could be pulled from one or more of those sources. Challenge will be finding data elements that accurately correlate a specific person between services.

Specifically, Open Graph and Twitter Cards. See https://css-tricks.com/essential-meta-tags-social-media/

The HTTP Vue loader has worked well, but it's time to grow up and use webpack to create a single bundle. Blocked by https://github.com/Wyamio/Wyam/issues/613 - need Wyam to drive and keep the webpack bundler active during builds.

It's valuable to have them listed and aggregated, but would be nice to be able to filter them out too. See if we can get the GitHub read-only status via Octokit to set.

With link to pre-filtered issues grid on project details page.

The GitHub API is periodically failing. Instead of failing the whole build, we should retry a few times first.