nickmcl / myaku Goto Github PK

The Myaku icon shrinks to a smaller size for mobile-sized viewports, but the shrunk down version has jagged edges and looks blurry.

Since only the date information is displayed on search result tiles with no time information, it's redundant to show last updated date if it is the same day as the publication date even if they differ in time.

Currently, the content for a query in the first page cache is rewritten by the crawler and rescore services whenever they make any change to a found lexical item for that query in the database.

Most of the time, the changes made to found lexical items in the database by these services does not affect the first page results for a query that matches that found lexical item. This means these services are wasting a bunch of time rewriting first page cache data with the exact same data when the update the first page cache in that case.

The services should be smarter about this so that they don't rewrite the first page cache for queries when nothing will change from the currently cached data for those queries.

To emphasize the recency of very recent articles, instead of showing their date in the standard format, use natural time like "today", "yesterday", "3 days ago", etc.

If a title is only white space, it will not be rendered in the search result tiles and thus will be unclickable.

If a title is only white space, either some other contextual data such as the blog section title should be used instead of the title, or at least some placeholder needs to be used in the search result tiles to make the article link clickable.

If a search query matches the title of an article and that match is used in the preview of the article in the search tile, the position of the match is displayed as '0% into article'. It would look better if it displayed the position as 'In title' or something similar in this case.

Beautiful soup replaces '&" characters in text with "&". Currently, this isn't considered at all in the crawlers, so whenever they parse text from HTML with "&" characters, the resulting strings are getting stored with the "&" characters replaced with "&".

This needs to be fixed so that parsed strings are stored with "&" characters intact.

The article preview generator can currently include long strings of symbols in article previews like:

☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★☆★

Although small groups of symbols like 顔文字 can be fine in previews, including long strings of symbols like that almost certainly will make for a bad preview, so long strings of symbols should be excluded during preview creation.

Currently, the article preview in the search results tiles will only show the sentence containing the matched term for the search. This means that even if the sentence is only a few characters long, that is all that will be displayed for the preview.

Previews with only a few characters are basically useless, so in order to always get a meaningful preview, it would be better to also display the preceding and/or following sentences for the sentence containing the matched term in the case that the sentence containing the matched term is very short.

The article preview generator currently does nothing special in regards to quote characters. They're just treated like any other character.

This means that article previews can easily be generated that only take a portion of a quote when the full quote could have been used while still staying within the article preview character limits.

The article preview generator should start prioritizing on preview expansion including the full quote in the preview when it already includes part of a quote.