Skip to content

[ExpressionLanguage] Merge docs about ExpresssionLanguage #17724

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
Jan 12, 2023

Conversation

fabpot
Copy link
Member

@fabpot fabpot commented Jan 11, 2023

No description provided.

@carsonbot carsonbot added this to the 5.4 milestone Jan 11, 2023
@fabpot fabpot requested a review from xabbuh as a code owner January 11, 2023 19:48
@fabpot fabpot force-pushed the expression-language-docs-merge branch from bb23a4a to 98abff5 Compare January 11, 2023 19:50
@carsonbot carsonbot changed the title Merge docs about ExpresssionLanguage [ExpressionLanguage] Merge docs about ExpresssionLanguage Jan 12, 2023
@javiereguiluz javiereguiluz force-pushed the expression-language-docs-merge branch from 98abff5 to 3ecb282 Compare January 12, 2023 09:33
@javiereguiluz javiereguiluz merged commit 9a90511 into symfony:5.4 Jan 12, 2023
@javiereguiluz
Copy link
Member

Thanks Fabien for another nice doc merging PR.

@@ -1,320 +0,0 @@
.. index::
Copy link
Member

Choose a reason for hiding this comment

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

I think we should keep th is article separate, as this is much more a reference article than a guide

Copy link
Member

Choose a reason for hiding this comment

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

I'm not saying that you are wrong ... but in my opinion, having most of the things related to ExpressionLanguage in a single (long, but manageable) article is better for readers.

And with the recent doc redesign, the sticky TOC will make it easier to browse long articles and quickly move between sections.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, for the same type of documentation (and with emphasis on the managable).
But no for different types of documentation imho.

https://documentation.divio.com/

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

Successfully merging this pull request may close these issues.

4 participants