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

Make the resource list grow! #1

Open
alfonsogarciacaro opened this issue Aug 19, 2019 · 14 comments
Open

Make the resource list grow! #1

alfonsogarciacaro opened this issue Aug 19, 2019 · 14 comments

Comments

@alfonsogarciacaro
Copy link
Member

alfonsogarciacaro commented Aug 19, 2019

Hi there, great Fable community contributors!

I've put together a community resource finder. It's very simple for now, but we can make it more sophisticated later and I hope that it helps make your contributions more visible to Fable users.

Could you please add your resources to the public/community.json file? You only need to add the name/title, a brief description, a link and a category.

Thanks everybody for your help!

@ncave @MangelMaxime @Zaid-Ajaj @et1975 @forki @dbrattli @cmeeren @musheddev @zanaptak @rommsen @nojaf @theimowski

@cmeeren
Copy link
Contributor

cmeeren commented Aug 19, 2019

Should this include all manner of Fable bindings for npm packages?

@sergey-tihon
Copy link

What about using using fable GitHub tag?
https://github.com/topics/fable?o=desc&s=stars

@nojaf
Copy link
Member

nojaf commented Aug 19, 2019

Using the fable tag on GitHub also included old non-maintained projects right? Might be misleading for beginners.

Would you also list tools here? I once made a thing that convert json to Thoth decoders (https://nojaf.github.io/jason-to-thoth/), do those kinds of things also apply?

Lastly great initiative @alfonsogarciacaro ! Let's start simple and get this thing going.

@nojaf nojaf mentioned this issue Aug 19, 2019
@alfonsogarciacaro
Copy link
Member Author

@cmeeren Yes, I think that anything that's valuable for Fable users should be there.

@sergey-tihon That's an option, but hopefully this gives a better way to select the results (for example, like @nojaf discarding old projects). I would also like that authors are responsible of keeping the info up-to-date, and they may want to link to documentation instead of Github page, for example. This also gives us the opportunity to list resources that are not in GH (like videos or blog posts).

@nojaf Yes, tools can be included. For now I added these categories, but we can extend/modify them:

community/src/Global.fs

Lines 6 to 10 in eac7d23

type ResourceCategory =
| Library
| Tool
| Tutorial
| Video

@cmeeren
Copy link
Contributor

cmeeren commented Aug 20, 2019

I guess bindings should go under library, but what about boilerplates/examples like fable-elmish-electron-material-ui-demo?

@alfonsogarciacaro
Copy link
Member Author

Probably we need a new category named "Template" or "Sample" 🤔

@cmeeren
Copy link
Contributor

cmeeren commented Aug 20, 2019

👍 please ping me when it's added

@alfonsogarciacaro
Copy link
Member Author

Done!

@MangelMaxime
Copy link
Member

@alfonsogarciacaro I think we can have both categories because Fulma-demo is not really a template per se for example. What do you think?

@cmeeren
Copy link
Contributor

cmeeren commented Aug 21, 2019

fable-elmish-electron-material-ui-demo is also not really a template, but more like Fulma-demo. "Sample" would work well I think.

@alfonsogarciacaro
Copy link
Member Author

Ok, let's add the "Sample" category too then :)

@davedawkins
Copy link
Contributor

I have a new package to add

https://github.com/davedawkins/Fable.React.Autocomplete

Is this the correct procedure to update this list?

  • Fork this repository (to my own github account - Is a branch needed?)
  • Update community.json / commit / push back to repository
  • Create a pull request to this repository
    [ - Wait until PR applied and optionally delete my fork of this repository ? ]

Thanks

@MangelMaxime
Copy link
Member

Hello @davedawkins yes this is the correct procedure.

You don't necessarily need a branch you can push your changes in your own master branch.

@alfonsogarciacaro
Copy link
Member Author

You can also just use the edit button in GitHub, this automates the process of forking and sending the PR, so the only thing you need to do is edit the community.json file.

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

6 participants