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

All non technical documentation removed #1195

Open
codingedgar opened this issue May 4, 2020 · 6 comments
Open

All non technical documentation removed #1195

codingedgar opened this issue May 4, 2020 · 6 comments

Comments

@codingedgar
Copy link

📖 Documentation

In this commit : e08a16e all non-technical documentation was removed.

The images and all that non-technical documentation was incredibly valuable and a reference for me to understand better not only the library but FP in general, especially this map: https://github.com/gcanti/fp-ts/blob/2.4.3/docs/type-classes.svg .

I understand that almost all have been ported to blog posts, but I cannot find this SVG, could it be added again? It really helps me navigate better the type classes.

Thank you for this amazing library.

@jacobdr
Copy link

jacobdr commented May 16, 2020

Is there a plan to restore the docs with new content? If not, is that something the maintainers would be open to? The technical docs are exhaustive but IMO impossible for most TS developers to grok if they want to take the leap into FP

@steida
Copy link
Contributor

steida commented May 16, 2020

I think the key is to use only what you understand. pipe, Option, Either, Task, TaskEither, sequenceS/T, with map/chain/a few other functions. I think that's almost all I use because it's relatively easy to understand. There are a lot of more interesting things, but, without clear real-world examples, it's hard to understand. I wish I had time to write about it.

@jacobdr
Copy link

jacobdr commented May 17, 2020

The resources at the Getting started with fp-ts series I think is exactly what I wanted. It is referenced in the docs but I thought slightly hidden (and also, kept out of tree)

@jacobdr
Copy link

jacobdr commented May 17, 2020

Perhaps the OP's desire could be satisfied by generating the inheritance diagrams through Typedoc when publishing the docs?

Relevant reading:
Typedoc issue: TypeStrong/typedoc#175
The ill-maintained: https://www.npmjs.com/package/typedoc-plantuml-extended
The non-automated: https://www.npmjs.com/package/typedoc-plugin-mermaid

@nyctef
Copy link

nyctef commented Jun 4, 2020

a reference for me to understand better not only the library but FP in general, especially this map: https://github.com/gcanti/fp-ts/blob/2.4.3/docs/type-classes.svg .

Wow, that image is really good! I wish I'd seen that earlier. Currently the docs just have a big list of alphabetical modules, which is rather intimidating when you don't already know what you're looking for :)

@codingedgar
Copy link
Author

Thanks, @nyctef , my thoughts, exactly.

@jacobdr maybe the inheritance diagram will end up generating something similar, but I doubt it, there are many kinds that do not map to that image at all.

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

4 participants