leostera / tldr.jsx Goto Github PK

Make small sass mixin for grid's based on http://uniweb.victorfleur.com/uniweb.css

.content
  +grid(columns: 2, rows: 2)

It'll make it possible to point to other repositories (forks) and maybe even bropages.

Hi,

On pages like history, the example markdown contains embedded backquotes (surrounding bash):

- Clear the commands history list (only for `bash`)

The client reads it as a command inserts a new line before and after.

The output looks something like :

Clear the commands history list (only for
bash
)

Cordially

• Lowercase everything before searching.

Steps to reproduce:

1. Open the page
2. Insert "ln".
3. Wait for page to load, notice the link to edit ln.md page.
4. Press "BackSpace" in the search field.
5. The page is updated to "No such command", but the link to edit ln.md remains.

https://monosnap.com/file/0atBOhRWgXGHY6n6oRKP41iQwuBRdw

Make it look sweet on mobile!

Take a look here: https://buttons.github.io/

yield on index loading, then do the look up

As per discussion on: tldr-pages/tldr#948

http://www.ostera.io/tldr.jsx/ should probably redirect to the new? site: https://tldr.ostera.io/

A spinner animation or "loading..." text would be nice to provide an indication that the page is fetching the requested command.

Wouldn't it be nice to be able to share this pages easily? www.ostera.io/tldr.jsx/git-add, as per tldr-pages/tldr#440.

How about adding a OpenSearch Description Document.
Basically just a xml file telling the browser how to search in the tldr pages.
So I could enter the url of the webpage in chromium press tab write "git tag" press enter and I would be on the according tldr-page.
Further information: http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_description_document0

Make it evident that a new page has been rendered, some pages have so similar a format that it makes it hard to see if there was any change at all.

• Build dist target
• Use deploy: config to deploy assets to S3
• With an after_deploy: script invalidate the index.html from CloudFront (more info on keys)

Maybe:

• Investigate other invalidation mechanisms for index.html file

Use-case:

I have watch and try. Two small cli utils that have no place in tldr itself because they do not come bundled with any UN*X distro.

I'd like to be able to reuse the current frontend and serve a small tldr page on how to use it from within the repo, by requesting https://tldr.ostera.io/ostera/watch.

The page could live in ./TLDR.md inside the ostera/watch repo.

Upsides:

• Effectively allow any repo out there to use tldr.jsx without polluting the index into gigantic proportions
• Drive more traffic that will drive our improvements to the tldr-pages

Downsides:

• Not being able to suggest ostera/try as an alternative to a failed command search for try
• Unclear how to lint these external pages, non-vetted content could be an issue

I'd like to know what @waldyrious thinks of this.

Just that: https://docs.travis-ci.com/user/caching/

Github now makes this easy with a simple configuration toggle (IIUC): https://github.com/blog/2186-https-for-github-pages

This is required for proper embedding on tldr-pages.github.io

If command is not found, offer a suggestion based on the input string Levenshtein distance to the indexed commands.

If command is found for another platform, show it under the suggestions as well.

Needs new pictures

Fix to the right, with a smaller size

E.g. "edit this page" or "see on github".