You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jaekwon proposed creating a community wiki in the awesome-gno repository during one of the developer calls. This repository is the most official place for community-curated content.
What do you think about creating a simple wiki folder in the repo, allowing people to open PRs, review them, and eventually establishing stricter rules such as a fixed structure?
The text was updated successfully, but these errors were encountered:
I think awesome-gno lacks visibility but maybe it would giving it some.
I can see an alternative though, it would be to:
encourage people to edit files in gnoland/website/pages (after some structuration, could be just creating a contrib folder or something like that for all I know),
This way, github users can easily see what's new in website/pages/contrib when git pull, and visit from their local gnoweb etc. So a markdown wiki, without the interactivity but having pretty much the same spirit.
(I guess those ideas are pretty similar all-in-all, since awesome-gno is linked from gno.land)
@jaekwon proposed creating a community wiki in the awesome-gno repository during one of the developer calls. This repository is the most official place for community-curated content.
What do you think about creating a simple wiki folder in the repo, allowing people to open PRs, review them, and eventually establishing stricter rules such as a fixed structure?
The text was updated successfully, but these errors were encountered: