Skip to content

RFC: Native docs merge #92

@bcarroll22

Description

@bcarroll22

Is your feature request related to a problem? Please describe.
Nope, promised I'd be back to talk about this with a plan though 😉

Describe the solution you'd like
I'd like to merge the docs sites. Seems very doable now.

Describe alternatives you've considered
Not merging the docs sites 🤷‍♂️

Additional context
Alright here we go. Here's the content hierarchy I'm proposing:

Topnav

  • DOM
  • Native
  • Ecosystem
  • Help
  • Blog

Sidebars

  • DOM
    • Getting started
    • Main API
    • Wrapper APIs
    • Examples
  • Native
    • Getting started
    • API
    • Examples
  • Ecosystem
    • user-event
    • jest-dom
    • bs-jest-dom
    • jest-native
  • Help
    • Guides
      • Which query:
        • Make it more generic so that it applies to DOM and Native
      • Appearance and disappearance
        • Make it more generic so that it applies to DOM and Native
    • Learning material
    • Contributing

I know it's quite a bit different than current state, but the content of most things doesn't need to change. It's mostly re-organizing the making some references more generic (which I mostly addressed in my latest PR.

I took a couple screenshots of how the topnav would look with these items at different sizes:

Screen Shot 2019-04-28 at 10 33 47 PM

Screen Shot 2019-04-28 at 10 34 51 PM

So I think it looks really nice! And this would allow us both to have the amount of docs we'd need for users to have the same great experience.

This is intended to be a first draft, let me know what you guys think. I think in this model I could pretty much just copy the native docs over without many changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions