Hello you,
When you drill down to the product display page on the developer portal, I know that the respective node is populated using smartdocs template. It looks quite satisfying out of the box, but just to enhance the user experience we are thinking of making the product display page more informative and elaborate.
Here's what we're thinking of implementing for the product display page and against are my thoughts on achieving the same-
1) All the API Endpoints related to the product on a sidebar ( render a block in smartdocs template which holds "Method TOC" view)
2) Documentation of the selected endpoint in the "page-content' region which holds-
a - Parameters with fields-->Name, Located in?, Description ( customize smartdocs context, template)
b - Responses with fields-->Code, Description, Schema ( customize smartdocs context, template)
c - Test Endpoint- (Out of the box)
d - Models ( customize smartdocs context, template)
3) A "Use this Product" feature which lets user register the product in a new app or any existing app (passing the product UUID via url on clicking a button ?)
I hope I made sense and myself clear. Am I thinking right/ Are the above even possible ? I do not expect a ready-to-go solution here in the comments/answers, all I need is a push in the right direction so that I don't travel far in the wrong one.
Thanks for reading patiently !
Dharma
Solved! Go to Solution.
Absolutely great ideas & It's a great way to display products, APIs associated with it. It's definitely doable within a shot span of time (May be 8 - 16 hours of effort) with relevant Drupal Expertise & Understanding Edge - Developer Portal Interaction, How smartdocs works.
Let me clarify few things,
Here is what i will do to build a page & navigation like you mentioned in above wireframe.
Hope it helps. Let us know how it goes.
Thanks for the valuable pointers.
In case anyone's trying to achieve the above, read through.
Automated the process of creating blocks using contextual filters in the method listing view (pull NID from URL) and then published the block using context ( condition being--> node type=smart method, action--> include myblock).
I like the ideas here, but I don't have a ready-built solution fo ryou.
Maybe @Anil Sagar or @Gitesh Koli might have some further suggestions.
Or @Cass Obregon .
@Dino Thanks for the reply. @Anil Sagar, @Gitesh Koli, @Cass Obregon To be much clearer, this is what we're trying to achieve-sample-frame.png
As I said I do not need a ready-built solution, just a few pointers would be appreciated.
Absolutely great ideas & It's a great way to display products, APIs associated with it. It's definitely doable within a shot span of time (May be 8 - 16 hours of effort) with relevant Drupal Expertise & Understanding Edge - Developer Portal Interaction, How smartdocs works.
Let me clarify few things,
Here is what i will do to build a page & navigation like you mentioned in above wireframe.
Hope it helps. Let us know how it goes.
Thanks for the reply @Anil Sagar, really appreciate the time and thoughts you've put on this question.
I understand that you want me create two blocks-
1) For the top part which holds Name, Description etc..
2) Sidebar that holds "Method Listing"
And then add these blocks to the smartdocs nodes individually. Even I thought the same and this definitely a way to do it. But, I'm looking for a solution that could be better automated than this. For instance, I'm thinking of using Mini-Panels, a view on the left for the method listing and the "Content pane" on the right for the rendered smartdocs node. All I want is a way to somehow integrate the "Smartdocs Method Listing" view and the actual smartdocs node itself.
Thanks again,
Dharma
@Dharma Teja Adusumilli , No , You shouldn't add these blocks to smartdocs nodes to individually. You will enable these blocks using context module & condition where method type is smartdocs. You will dynamically read the current node id & filter the relevant smartdocs using contextual filters in views. Hope it helps. Need little bit of Drupal Views contextual filters expertise here.
Thanks for the valuable pointers.
In case anyone's trying to achieve the above, read through.
Automated the process of creating blocks using contextual filters in the method listing view (pull NID from URL) and then published the block using context ( condition being--> node type=smart method, action--> include myblock).