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

Improve documentation #38

Open
lpil opened this issue Feb 13, 2018 · 16 comments
Open

Improve documentation #38

lpil opened this issue Feb 13, 2018 · 16 comments

Comments

@lpil
Copy link
Contributor

lpil commented Feb 13, 2018

Hi there!

I'm enjoying Elli after switching a couple projects to it from Cowboy.

My main problem has been lack of documentation, for example I needed to read the source code to determine how to use middleware (and I feel I'm still missing many of the details).

I feel this results in Elli being less accessible and less likely to be used, especially to people who are more used to Elixir rather than Erlang. Could we improve the docs? Perhaps include a series of examples in the README?

I'd be happy to help here.

Cheers,
Louis

@deadtrickster
Copy link
Member

Hi,

you totally right! we need more examples and use-cases. Personally I don't have much time for this unfortunately. But if you decide to contribute I'll be happy to discuss and merge.

@lpil
Copy link
Contributor Author

lpil commented Feb 13, 2018

Cool. Where would you like me to put them?

@deadtrickster
Copy link
Member

I think starting with extending REAME would be good enough. complete app(s) can go to a separate directory.

@yurrriq
Copy link
Member

yurrriq commented Feb 13, 2018

I wouldn't mind a separate elli-lib repo even.

@lpil
Copy link
Contributor Author

lpil commented Mar 14, 2018

Hi @yurrriq, could you make an elli-example repo please? I'll make a pull request there afterwards :)

@deadtrickster
Copy link
Member

@lpil
Copy link
Contributor Author

lpil commented Mar 14, 2018

examples would be better than example unless we only want one example per repo.

I was imagining many small ones in there for users to read without getting lost in a big app

@lpil
Copy link
Contributor Author

lpil commented Mar 14, 2018

Also this seems to hand been closed prematurely, the documentation is still very sparse.

@deadtrickster deadtrickster reopened this Mar 14, 2018
@deadtrickster
Copy link
Member

I closed this issue accidentally

@lpil
Copy link
Contributor Author

lpil commented Mar 14, 2018

Thanks @deadtrickster ! :)

@lpil
Copy link
Contributor Author

lpil commented Mar 14, 2018

Me again, sorry. I don't seem to be able to make a PR until there is a first commit. Could you perhaps make a commit with an empty README or such?

@tsloughter
Copy link
Member

@lpil looks like there is one now.

Also, we should publish docs to hex. I'm fine putting all docs in edoc stuff and publishing to hex for everything, but we could also consider something like readme.io.

@lpil
Copy link
Contributor Author

lpil commented Apr 11, 2018

Aye, I've made some PRs since :)

Documentation on hexdocs would be fantastic from my point of view

@yurrriq
Copy link
Member

yurrriq commented Feb 2, 2021

Hmm.. looks like something's gone wrong with the last couple times publishing to hexdocs. Not my wheelhouse, though I'd be happy to look into it. Ideally we can fix this for 4.0

@paulo-ferraz-oliveira
Copy link
Contributor

@lpil, a bit late to the party, but... is that repo. enough for what you envisioned? (I know you're busy with other stuff) I was just wondering if there's the need to update in the scope of this issue, or it could be closed (?) The one I linked doesn't solve all issues, of course, it just moves to ex_doc 😄

@lpil
Copy link
Contributor Author

lpil commented Sep 9, 2023

I'm sorry but I've not given this any thought in recent years!

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

No branches or pull requests

5 participants