On the contact page at http://loklak.fossasia.org/contact, please add a section with the following info and use the sign up form of fossasia.org at https://github.com/fossasia/fossasia.org/blob/gh-pages/index.html .

If you would like to get updates about our activities and new releases, please subscribe to our newsletter here:

Name, Email, Subscribe

If you are a developer:

• Please join our mailing list to discuss development questions about the project: https://groups.google.com/forum/#!forum/loklak

• You can also find us on our chat channel on gitter here: https://gitter.im/loklak/loklak

Console log.

Uncaught Error: Template parse errors:
Unexpected closing tag "a" ("XPwD/AVER/qFOTZZGAAAAAElFTkSuQmCC" alt="loklak social media search engine">
         </a>">
        [ERROR ->]</a>
      </div>
      <div id="navbar" class="navbar-collapse collapse">
"): ContactComponent@12:8

Many news organizations have a twitter and youtube account. Please show a stream from news organization in the sub tab "News".

Implement as follows:

• Create a json file with a list of accounts of social media of news organizations (sort alphabetically and by media, e.g. Twitter, Youtube)
• Show the stream just like other search results in a sub tab "News"

The gray bottom bar is to close to the above area. Please leave some space above the bar.

When a user enters a search site like google.com, the site activates the search bar and shows the cursor in the bar right away. This means the user does not have to click the search box to type.

Please implement it in the same way.

• Please implement the same height as the Google search bar.
• Currently the search gets a blue kind of shadow, when it is highlighted. Please only change the line color to blue and do not show a box shadow.

�[31;1mERROR:�[0m An error occured while trying to parse your .travis.yml file.

Please make sure that the file is valid YAML.

http://lint.travis-ci.org can check your .travis.yml.

The log message was: Build config file had a parse error: found character that cannot start any token while scanning for the next token at line 10 column 1.

[Issue]

• Whenever there is a refresh in the route segment of the page (not the home page), the gh-pages 404 is shown.
• This is due to the fact that gh-pages doesn't have a file corresponding to that route, the route handling needs to be done by the framework (angular) itself.

[Expected Behaviour]

• All single page applications (angular here) expect the all the routes to be redirected to the index.html, from where their router kicks in and handles the appropriate.

The root directory of the project should show the start page of the project.

If you are unsure how to implement this, please compare this to other Angular2 repositories like: https://github.com/tjvantoll/groceries and the website here https://github.com/tjvantoll/groceries

Also check out: https://github.com/angular/angular-cli

Please help to finish the deployment to gh-pages.

If no results match the search, please move the info bottom bar to - bottom and display message as follows:

Your search {search terms/keywords here} did not match any documents.

We will crawl the social web with this search term again in the upcoming hours. Please check back again later. In the meantime please try the following to get relevant results. Suggestions:

Make sure that all words are spelled correctly.
Try different keywords, accounts or hashtags.
Try more general keywords, accounts or hashtags.

Compare to Google:

There are some files in the repository, where the usage is not clear.

@hemantjadon Any idea?

I was trying to access the api http://api.loklak.org/api/search.json?q=foo but the resource is erroring with No 'Access-Control-Allow-Origin' header is present on the requested resource.

I want to know that is this an intended behaviour or something which can be fixed?

For testing the site should i use local version of loklak_server and not the api

• Use bootstrap
• Create front page search site #2
• Create sub search sites #3

Files in src/assets/images total size is 261kb. At least two of these files can be compressed without losing quality.

Instead of imprint please add a contact page at /contact.

Use the same design as the "about" page and add the following information:

Contact Us

Loklak
93 Mau Than Street
Can Tho
Viet Nam
Phone +84 (0) 907 65 29 27
Email: [email protected]
Board of Directors: Phuc Hau Dang
Loklak Ltd. is registered in Can Tho, Viet Nam.

Report a safety or abuse issue affecting our products.
If you know of a safety or abuse problem with any of loklak's services, we'd like to hear about it right away. Please use our contact form to report the issue.

Please load the site without "loading..." message.

Circle CI is already integrated, but tests are lacking.

The alternate text for the image loklak_banner_206x45 is set as "Dispute Bills" as shown in the image below.

I think it should be something related to loklak.

Will it be good to have the model/schema (Typescript classes) of the api-responses or just plain JSON should be used?

• Using classes will make the use of the response object more robust and easier to write.
• But using plain JSON gives us more flexibility in case structure of response changes over time.

Please Suggest :)

Currently only one webpage has the loklak icon. http://api.loklak.org/

I suggest adding the icon to every webpage in loklak search.

The following files in assets/images are named incorrectly based on their sizes.
cow_200x233.png
loklak_banner_252x45.png

The screenshot below shows different facettes/filters.

Please implement it in the same style for

• All #17
• Video Results #49
• Image Results #48
• News Results #46

Please implement additional pages just as other search engines, e.g. Google.

The web client prototype (currently at http://loklak.net) has the feature of autocompletion. Please implement autocompletion for the new site.

• Implement Google theme (with loklak logo)
• At first glance show search bar in middle
• Implement moving up of search area to top left on typing start similar to Google

The screenshot below shows different facettes/filters.

Please implement it in the same style for Image Results

Subissue to #3

Clicking on bottom links does not bring a user to the top of pages, e.g. if I am on the contact page (http://loklak.fossasia.org/contact) and I click on "Terms" I get into the middle of that page.

Please implement the expected behavior and open the new page on the top.

Please implement the result page similar to Google/Twitter.

• The front page image is currently 64KB. Please check how this image size can be decreased without loosing quality.
• Currently there is no favicon defined. Please add the loklak animal as a favicon.

Please add a link for RSS and JSON for search results on right below top bar.

There should be model/class for query string processing, which can contain various filters and aspects of a search, mentions, hashtags, and most importantly time and location based searches, along with client side filtering like, videos/images/news

• There should be direct linking of query string (from url) to a query object on component initialization.

• On subsequent changes in query the object is modified and various filters can be applied on the object.

• This will decouple the query string logic into a more robust object whose properties can be changed irrespective of the component.

  Eg. We want to implement the time restricted search in #43, this will be much easier to normalise if there is only one query object with property say since and until if these properties are set irrespective of which component sets it, the query will be performed accordingly.

• Basically There can be single query object in the application whose properties varies according to the applied filters and narrowing of search results. These can be varied by different components and query will be performed on cumulative changes rather than each change requesting the search service to fetch the results.

• Using this approach debouncing and defering of searches can be performed as there will be single requesting source.

Please provide inputs and suggestions :)

• Fix the unintended switch which occurs in firefox on press of keys like esc, tab and delete/backspace.
• First keystroke is ignored in firefox (during the switch). Needs a fix.

Both these issues occur as firefox handles the events differently than webkit browsers. In webkit the keypress event is fired only when a character key or enter/return key is pressed.
But in firefox it is also triggered with other keys as well.

Please implement a footer similar to Google as shown below.

One the left side add:

• "About" to an about page at /about
• "Blog" to http://blog.loklak.net
• "Developers" to http://api.loklak.org

On the right hand side add:

• "Terms" to /terms
• "Imprint" to /imprint

There are different banners images, that should not be there.

• Please rename the about-banner.jpg to banner.jpg
• Delete all other banners and use banner.jpg across the relevant pages

Parent Issue: #3

Please implement a live result page for searches.

Similar to Google implement a time restricted search after clicking on "Search Tools".

Currently hashtags in search results link to the list of hashtag results on twitter.

The expected behavior is that "#hashtags" link to the search result page of loklak_search.

Currently there are a number of issues for mobile resolutions of pages (e.g. see below). Please ensure pages are working on small resolutions.

If there are just a few results the bottom menu currently does not show up on the absolute browser window bottom.

Please ensure the bottom is on the actual bottom area if this happens.

Please design the about page following the design of https://www.google.com/intl/en/about/

Please add the following information

• one column
  Our mission is to make the world’s social media information openly accessible and useful generating open knowledge for all. # OpenData (/search?query=#OpenData) #OpenSource (/search?query=#OpenSource) #OpenKnowledge (/search?query=#OpenKnowledge)
• three columns

News from us
Read up on our latest news and browse our blog (http://blog.loklak.net) for updates on our work.

Developers
Wanna know how to set up loklak yourself or you would like to develop an app based on loklak. On http://api.loklak.org you find more info about our APIs.

Contribute to our projects
Ever wondered what life as a developers looks like or what benefits you might expect as an Open Source contributor? Search for an issue to solve on our repositories with FOSSASIA (https://github.com/fossasia?utf8=%E2%9C%93&query=loklak) or the loklak org (http://github.com/loklak/) and check out feature requests and issues.

• adjust height and use this image
  

The screenshot below shows different facettes/filters.

Please implement it in the same style for video results.

Subissue to #3

This file is a logo not a banner.

On the bottom of search page results we often find "related searches". Please implement a similar thing "related hashtags".

The goal of the issue is to make the start page accessible from the root at https://fossasia.github.io/loklak_search/ and show a simple search button.

A sample of the front page search site below.

With Chrome and Firefox images do not show up in private/incognito browsing mode. I am not clear if this is a Github/Cloudflare issue or caused by us. Other fossasia sites are fine in private mode.

Chrome has the feature to enable voice. Please enable the site to use this feature.

The page at http://loklak.fossasia.org/terms currently does not hold information. Please implement the page as a terms of reference page in the same design as the other info pages, but without the picture. See below. The text for the terms is here: https://docs.google.com/document/d/1-w7C-PySdw1c8J2WbkBaqRRXjeXj3qFUoyDqAMbhlig

Also compare to: https://www.google.com/intl/en/policies/terms/

@mariobehling
Hi sir,
As I am able to see the Travis CI is not enabled for this repository, please look into that.
Also Circle CI is failing on builds and throwing some errors (due to absence of .circle.yml, i suppose).
The codecov is still showing unknown(don't know the reason).

Also i think direct merge to gh-pages should not be there, I mean there must be another branch for development (as mentioned in readme.md) so that production and development code remains segregated.