Voyager: Documentation lacking

[SUPERNOVI]

• Laravel Version: 5.4.18
• Voyager Version: 0.11.9
• PHP Version: 7.1
• Database Driver & Version: MariaDB 10.2.3

Description:

Hi,

I really love this project but I'm finding the documentation a little lacking.

As an example, if I create a custom view for the BREAD for an add and edit page and I'd like to use one of the Voyager generated inputs like Multi select there is no documentation on how to call it within the blade template manually.
So could someone give me an idea where I need to look to figure this out or even tell me?

I apologise if this isn't a suitable place to ask, but I really struggled to find any means of contact other than GitHub.

Much appreciated,
Tim

[SUPERNOVI]

Has anyone at Voyager read this?

[fletch3555]

I recommend you join our slack chat and ask there. The #help channel would be a good place to start with questions like this.

We know the documentation is lacking, and I promise it's something we're working on.

[uchsarath]

Agree with @fletch3555 just join the Slack, and it's easier to get supported by community.

[adriangordon1231]

I don't think that "just join slack" is a good solution to this problem. The docs should be updated with the relevant information.

[akazorg]

You're absolutely right @adriangordon1231, documentation requires update. You are free to contribute by sending a PR - that will help us.

In case you need help, then slack is available for support.

[SUPERNOVI]

@akazorg bit passive aggressive there.

I'd happily contribute some of the stuff I've learnt but I'm 90% sure the way I've done things is not the voyager way.

I have to agree also, "Just join Slack" whilst helpful should not be considered the norm. Slack whilst popular is not something everyone uses, I had to sign up just for this purpose.

[fletch3555]

@SUPERNOVI, his comment was not passive-aggressive in my eyes. We always welcome and encourage pull requests if you find something missing or wrong. The worst we'll say is "no sorry, this is wrong, could you please do it [this way] instead?"

As for slack, the way it works is that everyone has to sign up to use it. Each slack group has unique authentication, meaning you would have 4 unique accounts for 4 different slack groups. We encourage users to join us there to minimize the "how do I do this?" issues here. That helps us get to actual issues faster.

[akazorg]

@SUPERNOVI, I don't know what happen on your side of the communication, but my message was intended to help.

Please keep in mind this is an open source project, created with love, for free, from all of us.

If something is missing, let's work together on that!

Slack is a great support channel, you can get real time response.

Happy coding :)

(Close this issue?)

[akazorg]

@SUPERNOVI I was thinking, did you checked VoyagerPostController? maybe it can help you to figure out how to create custom controllers.
I hope it helps.

[adriangordon1231]

@akazorg Wish I could, however I am facing similar issues to the OP

[akazorg]

@adriangordon1231, sorry, OP?

[adriangordon1231]

@akazorg "Original Poster" ... of the issue. Sorry.

[akazorg]

The documentation?
All help is grateful, for instance, what do you miss on docs @SUPERNOVI @adriangordon1231?

Maybe we can create a list of missing topics and work from there?

[akazorg]

closed due to inactivity

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you have further questions please ask in our Slack group.