Needs review
Project:
Decoupled Menus Initiative
Component:
Task
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Nov 2020 at 17:29 UTC
Updated:
15 Apr 2021 at 19:47 UTC
Jump to comment: Most recent
It would be nice to have a FAQ for the initiative that explains the decisions we've made. For example, why are we not building actual components with markup and styles?
If you have a question or an answer to a question, feel free to put it in here and we will then gather this to a FAQ on this project.
Questions
What are decoupled menus?
Why start with menus?
What is the difference between library and the component?
How can I join?
Where is the code?
Wait, did you not have a JS modernisation initiative that is working on this?
Why are you not working with (other JS framework)?
Comments
Comment #2
nod_Comment #3
yoroy commentedI created a documenation page for this project where the FAQ could be hosted:
https://www.drupal.org/docs/contributed-modules/decoupled-menus-initiative
to edit: https://www.drupal.org/node/3182113/edit
Comment #4
yoroy commentedComment #5
yoroy commentedAdded @nod_, @gabesullice, @lhockley, @baddysonja as maintainers for a start, hope that's ok, otherwise let me know!
Comment #6
yoroy commentedComment #7
yoroy commentedPasting over from Slack:
How can I use this with (other JS framework)? / Can I help to add support for (other JS framework)?
Why don't you use (existing menu library)?
Why don't you use GraphQL?
What is difference from jsonapi_menu_links or native json:api menu support?
How does this differ to using the JSON:API Menu Items module?
(A: A core solution negates the need for a Contrib module)
Comment #8
mirom commentedI just created GDoc where we can collaborate on writing Q&A https://docs.google.com/document/d/1Tv0GNayYeXvhnK0NNNdvwh-Cw8iA77D48Jlq..., if you want to edit it directly, could you please send me your email on Slack?
Comment #9
baddysonja