[ 
https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127275#comment-17127275
 ] 

Aemie commented on CAMEL-14958:
-------------------------------

I don't like the design of search implemented with typescript much but that of 
bootstrap is really good. Docsearch and my implementation is similar. Also the 
only problem I am trying to state here is your idea of design and that of 
bootstrap looks amazing with screen width < 1024px when the nav burger appears. 
From width ranging from 1024 - 1220 there is no navbar burger and no search bar 
as well. And using bootstrap design to cover the entire width right below 
navbar might not look neat. I will implement the idea of bootstrap and see on 
this range of width and let you know. 

> Suggestion on search bar within smaller screen width.
> -----------------------------------------------------
>
>                 Key: CAMEL-14958
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14958
>             Project: Camel
>          Issue Type: Improvement
>          Components: website
>            Reporter: Aemie
>            Priority: Major
>              Labels: outreachy2020, suggestions
>         Attachments: inline-search.png, nav-search-icon-1220.png, 
> nav-searchbar-1220.png, nav-searchbar-414.png, navbar-search-414.png, 
> navbar-searchbar.png
>
>
> Within the small width screen, the setting is to only display the social icon 
> button as of now. However, I thought it would be a good idea to include the 
> search icon alongside the social button icons. On click of the social button 
> icons, we could include animation, for instance, a fade-in effect of the 
> search bar occupying the entire navbar. The user can do the search as 
> required. On the left side of the search bar, there will be back arrow, which 
> on click would give us the original navbar look with a fade-out effect.
> Before I start working on this, I would like an opinion about this idea.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to