Skip to content

Add integrations, add symfony bundle documentation #93

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

Merged
merged 1 commit into from
Mar 2, 2016
Merged

Conversation

sagikazarmark
Copy link
Member

Initial version based on README. Needs proofreading.

@Nyholm
Copy link
Member

Nyholm commented Feb 29, 2016

Here is a suggestion to structure/headings:

  • Intro
  • Configuration and usage example
  • Installation
  • Toolbar feature
  • Auto discovery and not
  • Small client config
  • Small plugin config
  • List of services

Pages:

  • Full configuration example
  • How to implement this in other bundles

Is this structure okey? Any other suggestions or comments?

@sagikazarmark
Copy link
Member Author

Looks good to me. Although for me installation sounds more logical before configuration.

@Nyholm
Copy link
Member

Nyholm commented Feb 29, 2016

I've thought about this a lot and I believe we discussed that in the Sound of Symfony podcast. My reasoning is the following:
If I've heard about a bundle that might help me, I want to see what it does as quick as possible. At this moment I do not care how to install it, I want to know if the bundle satisfy my problem first. If I like itm then I'm more committed to the bundle and can spend some time looking for the installation instructions.

To be honest, I do not think many people will read our 4 lines of introduction before they look at the usage example.

But that is my 50cent

@sagikazarmark
Copy link
Member Author

Actually that sounds quite reasonable. In this case I guess configuration is some kind of minimalistic example of configuration.

@Nyholm
Copy link
Member

Nyholm commented Feb 29, 2016

Yes,

Do you mind if I make a PR to this branch?

@sagikazarmark
Copy link
Member Author

Not at all, but you are free to push to this branch directly.

@dbu
Copy link
Contributor

dbu commented Mar 1, 2016

in the symfony cmf, we have things in chronological order, so installation first, then configuration. and first have a short introduction that explains what the bundle does, without code. as installation is quite short, it should not be difficult to scroll over it when looking for how the bundle works. i would vote for keeping the technical order here - but if you all think the other way round is better, i won't make a fuss :-)


The usage documentation is split into two parts. First we explain how to configure the bundle in an application. The second part is for developing reusable Symfony bundles that depend on an HTTP client defined by the Httplug interface.

For information how to write applications with the services provided by this bundle, have a look at the [Httplug documentation](http://docs.php-http.org).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is now the same documentation, so we should probably do this as internal link and rephrase.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

handled in #94

@dbu
Copy link
Contributor

dbu commented Mar 1, 2016

most of my comments are already handled in #94, only a few remaining:

  • in RST, code can only be noted with double backticks, single backticks are used for links and such. this needs to be fixed throughout this page, code will not be rendered correctly as is.
  • usage in reusable bundles

@Nyholm Nyholm mentioned this pull request Mar 1, 2016
@dbu
Copy link
Contributor

dbu commented Mar 2, 2016

once we have #96 in this, i am happy with this to be merged.

@Nyholm
Copy link
Member

Nyholm commented Mar 2, 2016

How about #95?

@dbu
Copy link
Contributor

dbu commented Mar 2, 2016

ups, sorry. merge that one. i am fixing the spelling errors in #96 (i hope all of them...)

@dbu
Copy link
Contributor

dbu commented Mar 2, 2016

we also need to update the application-developers.rst

@@ -1,11 +0,0 @@
HTTPlug for application developers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was only linking to the httplug bundle so it becomes redundant with the integrations chapter.

@sagikazarmark
Copy link
Member Author

LGTM

Squash first?

@dbu dbu force-pushed the symfony_bundle branch 2 times, most recently from b487394 to da1a879 Compare March 2, 2016 08:40
@dbu
Copy link
Contributor

dbu commented Mar 2, 2016

squashed all commits. sorry tobias, authorship is now shown as mark... but things where moved around a lot, so i thought keeping several commits is unnecessary confusing.

@sagikazarmark
Copy link
Member Author

MUHAHAHAHAHAHAHA

@sagikazarmark
Copy link
Member Author

kepernyokep 2016-03-02 09-47-36

@sagikazarmark
Copy link
Member Author

Just for the record that I was the author earlier. Now Tobias is. 😉

@Nyholm
Copy link
Member

Nyholm commented Mar 2, 2016

screen shot 2016-03-02 at 09 59 19

Yeah, that is weird. I though I would disappear from the history when squashed...

dbu added a commit that referenced this pull request Mar 2, 2016
Add integrations, add symfony bundle documentation
@dbu dbu merged commit 4eaee49 into master Mar 2, 2016
@dbu dbu deleted the symfony_bundle branch March 2, 2016 09:02
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

Successfully merging this pull request may close these issues.

3 participants