Skip to content

Conversation

@joecritch
Copy link
Contributor

  • A "Community" section has been created, to house both the previous "Support" section and "Community Resources" docs category
  • Separates the concerns of documentation vs. community, with the primary goal of cleaning up the docs nav (See Docs nav is too noisy #1669)
  • Old permalinks supported via redirect_from field
  • Note: Recommended to merge [Docs] Added icon for external links in nav #6090 first, so we get icons for external pages.

screen shot 2016-02-23 at 13 33 47

@quantizor
Copy link
Contributor

I think the nav title should be "Community & Help" - I wouldn't look to "Community" for support-related stuff as a first instinct.

@joecritch
Copy link
Contributor Author

I personally disagree, as 'Community & Help' signifies that the help wouldn't be coming from the community. Also, FWIW, Ember.js has support inside of Community.

@quantizor
Copy link
Contributor

I wouldn't consider the Ember website the gold standard of information design.

@joecritch
Copy link
Contributor Author

Me neither, but convention can go a long way. If anyone shares @yaycmyk's concern here, shout out :)

@winkler1
Copy link

Community is one word like all the other heading in that section, seems like a good thing..

@facebook-github-bot
Copy link
Contributor

@joecritch updated the pull request.

@joecritch
Copy link
Contributor Author

Added a "More From Facebook" category, similar to "Complementary" on the Flux site. (I went with "More From Facebook" to distinguish against non-Facebook led projects)

screen shot 2016-02-24 at 23 23 18

@facebook-github-bot
Copy link
Contributor

@joecritch updated the pull request.

@gaearon
Copy link
Collaborator

gaearon commented Oct 23, 2016

Thanks for the PR. I'm closing because we released new version of docs with a Community tab:
https://facebook.github.io/react/community/support.html

If you have ideas about improving it, please submit a PR against master and assign it to @lacker. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants