Summary: As reported a few times in the internal chat
Reviewed By: passy
Differential Revision: D26813161
fbshipit-source-id: 8b834c7807a7634f23c3ab922bb43e288ea4bd68
Summary:
Based on the issue here https://github.com/facebook/flipper/issues/967, I'm adding the flipper diagram to a documentation.
It should help explain briefly how does all parts communicate together and visualise key terms.
## Changelog
- Add Flipper architecture diagram to documentation
Pull Request resolved: https://github.com/facebook/flipper/pull/1073
Reviewed By: jknoxville
Differential Revision: D21278322
Pulled By: passy
fbshipit-source-id: 3cd8c71b2595b86911f5c9061bc2e8119da1d315
Summary: Changes the link color to something that isn't very similar to the rest of the text.
Reviewed By: nikoant
Differential Revision: D21328856
fbshipit-source-id: 9467e368411caeb58e00642b48ef4413d285850e
Summary:
After moving to docusaurus v2, our h3 tags are bigger than the h2 tags.
Removing our custom css fixes this, so doing that to get closer to the default theme.
Reviewed By: mweststrate
Differential Revision: D21283840
fbshipit-source-id: ceaf7488b90bbb90a463037d9e1dfcca1d694366
Summary:
Docusaurus 2 is quite a lot more powerful than docu 1 it turns out.
This should convert the website fully.
* [done] Go through migration guide https://v2.docusaurus.io/docs/migrating-from-v1-to-v2
* [done] Convert landing page html
* [done] Convert all images to img tags
* [done] Convert all .md files to .mdx
* [done] Make sure ui-doc generation and including still works
* [done] Scan every page visually for sanity check
* [done] Make sure footer still works
* [done] Make sure search still works
* [done] Change all links/ to links/index
* [done] Change all links.md to links
* [done] Add some custom css to make the navbar look like the old one and darken the footer.
Reviewed By: passy
Differential Revision: D21158717
fbshipit-source-id: 5f45b711b1b6fd5ece4c5c15c55635c7ebbfb568
Summary:
Sync the Getting Started section about React Native integration with the latest changes in https://github.com/facebook/react-native/pull/27426.
## Changelog
Refresh Getting Started with the latest React Native integration
Pull Request resolved: https://github.com/facebook/flipper/pull/676
Test Plan: Tested in RN's template.
Reviewed By: mweststrate
Differential Revision: D18853584
Pulled By: passy
fbshipit-source-id: d001046106743b68d2f08b084c7618d8f768dea1
Summary:
This didn't look quite right to me, "Download Mac", "Linux", "Windows".
Changed it to a separate "Download for", with "Mac", "Linux" and "Windows" buttons.
Reviewed By: passy
Differential Revision: D18225271
fbshipit-source-id: d644570d072029fc792cd9d9c18d8616ada0017b
Summary:
There's probably a more elegant way for doing this
so please let me know if you can think of something.
Reviewed By: danielbuechele
Differential Revision: D17318727
fbshipit-source-id: 9afcc30205171cfb07f0a749c552692cb40a3ced
Summary: priteshrnandgaonkar pointed out that they sometimes overlap with the text.
Reviewed By: jknoxville
Differential Revision: D15182356
fbshipit-source-id: def39676d5dcce85aa0b41760cec0ec5cfb9398c
Summary: Adding a small ruler between each section on the landing page.
Reviewed By: jknoxville
Differential Revision: D15148067
fbshipit-source-id: 604f443c06eef16570dcdfbb21e121962b325127
Summary: Adding a "features" page to the to bar and splitting plugin descriptions from their setup instructions.
Reviewed By: jknoxville
Differential Revision: D15147464
fbshipit-source-id: b2106d825454c3b2989eb1e536b128ef9b6d0247
Summary:
All bumps are within range, so this shouldn't introduce any breaking
changes.
Pull Request resolved: https://github.com/facebook/flipper/pull/419
Reviewed By: danielbuechele
Differential Revision: D15120854
Pulled By: passy
fbshipit-source-id: dee4b52947cb548d13cd4bf625b29e3a643d8fc3
Summary:
Using `react-docgen` to automatically generate docs for our UI components.
React-docgen parses the files in `components/ui` and using comments and flowtypes to generate structured information about the UI components.
For higher-order-components `react-docgen` is not able to get the information. As we are using HOC often as part of emotion's styled-components, I added a custom parser for HOCs. Using babel/parser I am parsing the components and using their doc-comments to generate the structured description.
Then, the description generated by react-docgen and my custom parser is used to generate markdown which is added to the `ui-components.md` file of our docs.
Plus: Added some styling around the documentation of props, mostly table styles.
Reviewed By: jknoxville
Differential Revision: D12896110
fbshipit-source-id: 1337c924c06e10a5d3aa752579428fd2cc7b4743
Summary:
It's easier to find when they're in the repo. Exported them
from the AI template.
Reviewed By: priteshrnandgaonkar
Differential Revision: D9789825
fbshipit-source-id: ca717d130495842dcab4d06e02986d3df598dbe6
Summary: Fix a small issue we had with our mascot.
Reviewed By: danielbuechele
Differential Revision: D9180345
fbshipit-source-id: de1c34768b4f75202d78bd4404798a7549aa0457
