thusoy/blag

Bloggish homepage thingie. Probablity of more activity in repo than on blog is very high.

blag's Issues

RSS feed of blog posts

Subblog for bug hunts

With good keywords from each hunt so that it's possible for others in the same situation to find the solution and the hunt procedure.

Proper code block with pygments

Needed very soon for blog post..

Add a non-sucky text block

Sir-Trevor core text block refuses to play nice with ordinary markdown, escaping it and doing nasty stuff with my text. Fuck that. Write a markdown block that is untouched by sir-trevor, and rendered solely server-side.

Uploaded images need to be scaled and dumped to fileserver

Sounds like a celery task. Needs running fileserver first though.

Render tweets server-side

Shouldn't be any need to hit the twitter API to render them in the frontend when we have all the info backend.

Daytime sensitive color scheme

Low-order source rough geolookup of IP to estimated sunset (algo from f.lux).

Tagging functionality

It should be able to tag posts and follow certain tags:

• tag posts
• create new tag from within post
• view all posts with tag
• follow RSS for posts with tag

Open graph tags on posts

Post urls should redirect to a slug

Like /blog/10 should redirect to /blog/2015/dont-split-interdependent-values. Or other URL design?

hubby repo?

Tarjei,
I hope it's not too annoying to contact you through an issue.

Do you think we have your approval if we asked pypi for the name "hubby"?

It appeared to us you are no longer using https://pypi.org/project/hubby/ , but perhaps you want to reserve that for a future use?

We would like to rebrand the open source project https://pypi.org/project/qhub/ to distance it from QuanSight, the company that did the initial development work. We are hoping this will encourage more use and contributions from the community. And since this is an infrastructure-as-code project designed to make it easy to deploy JupyterHub backed by Kubernetes on any Cloud, it seemed "hubby" would be a great name.

Thanks for your consideration,
Rich Signell
USGS

Proper localization: Support for posts in multiple languages

Allows writing a post for Norwegians in Norwegian, and in English, and have viewers displayed the correct language based on a chain of decisions:

Query param (Post-specific) -> Cookie (site-specific) -> HTTP header (Browser/user specific) -> IP area (best guess, when nothing given explicit) -> Default English. Area could be skipped if IP is detected to come from known proxy service or Tor exit. Write blog post about how language, and other preference related decisions, should happen.

Allow guests to contribute a translation, with text reproduced on my site, link to text on their site and credits.

Default to filter comments on the language they responded to?

Don't set cookies for anon users

No point in this folly.

Add slugified name to headings

Rendering headings like <h1 name="section-header">Section header</h1> makes it possible to link to the section from the rest of the document.

Footnotes in blog posts

Should be possible. Preferably in the style of waitbutwhy, small clickable boxes with more information loaded in the case of javascript, list on the bottom in case it's missing.

Background is not rendered on post details page

Pinch-zooming should increase text size

On small devices text should always fill the screen, but for hard-to-read users pinching shouldn't zoom in on the text, which is useless since you'd have to scroll horizontally to read, but increase the text size.