⪼ Made with 💜 by Polyglot.
- Business :: Ideas
- Software Engineering :: Database :: Redis :: Example :: Gist Auto-Complete Description
- Software Engineering :: Markup :: Markdown :: Templates
- Software Engineering :: Web Browser :: Extension
- Software Engineering :: Web Browser :: Extension :: Ultimate Sidebar for GitHub Gists
- Overlay a Gist with transparency, open in new tab or edit in place
- Allows editing a Gist in place over the current web page
- provides a keyboard shortcut for
edit - autosave every 10 seconds if content changed since last save
- awesome-chrome
- Craft (Table of Contents Sidebar)
There are so many things to love about GitHub Gists; however, there are so many ways in which they can be improved. GitHub Gist is my favorite place to write. When I want to spike out some code, I write it in a Gist. When I have an idea for an app, I write it in a Gist. When I want to journal, I write it in a Gist. When I want to learn a new technology, I create a new Gist for it. The power of a GitHub Gist is grossly underrated.
Gist is a GitHub side-system, meaning, it is a system separate from the main GitHub service. The Gist system can be interacted with via the web UI or the GitHub API (additionally, you can append .json to the web URL of a Gist to retrieve a JSON representation of the Gist content where markdown files are pre-rendered in the response):
- A Git repository per gist for storing the file content of the Gist.
- A database entry for storing the Git repository ID, description, public/private status (not for security, but whether or not it shows up in public search), created_at, files, owner (currently useless since anyone witht the URL can access any gist).
- A web UI allowing users to create/manage their gists
- A search service (likely elasticsearch or postgresql) so gists can be searched. From what I can tell, they are only indexing on the title and maybe the description, but not the content of the files.
The web interface provides the following main functions:
- Create a new Gist
- Delete an existing Gist
- Edit/Update an existing Gist
- Search for existing Gists
- View and existing Gist where markdown files are rendered as HTML
A new Gist requires at least one file. Each file requires content (in other words, you cannot create an empty file). If you do not name the file, it will be named automatically gistfile{1..N}.txt.
There is a weird edge case where when gistfile1.txt doesn't exist, but, gistfile{N}.txt exists, if you create a new file with no name, the highest numbered gistfile{N}.txt file's contents are overwritten without warning witht the content of the unnamed file.
This behavior is not incorrect, but unexpected. I would expect gistfile1.txt to be created.
Inspired by Dropbox Interface
I love the dropbox interface. It's clean and things seem easy to find.
Then, there's codespaces, which is really nice because it's a real editor in the browser
For an interface like this, we'd need OAuth 2.1 (or a Personal Access Key set in LocalStorage or IndexDB)
