HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pallets
website
Python2016–2016
pallets / website

website

Code and content for the Pallets website

2Distinct people
2Mentions
0Explicit recommenders
13GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Code and content for the Pallets website

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2016-04-15 23:32:28 UTC to 2016-09-04 15:02:06 UTC. Weeks start Monday, UTC.

012016-04-11 00:00:00 UTC to 2016-04-18 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 112016-04-18 00:00:00 UTC to 2016-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-25 00:00:00 UTC to 2016-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-02 00:00:00 UTC to 2016-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-09 00:00:00 UTC to 2016-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-16 00:00:00 UTC to 2016-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-23 00:00:00 UTC to 2016-05-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-30 00:00:00 UTC to 2016-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-06 00:00:00 UTC to 2016-06-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-13 00:00:00 UTC to 2016-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-20 00:00:00 UTC to 2016-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 202016-06-27 00:00:00 UTC to 2016-07-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-04 00:00:00 UTC to 2016-07-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-11 00:00:00 UTC to 2016-07-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-18 00:00:00 UTC to 2016-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-25 00:00:00 UTC to 2016-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-01 00:00:00 UTC to 2016-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-08 00:00:00 UTC to 2016-08-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-15 00:00:00 UTC to 2016-08-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-22 00:00:00 UTC to 2016-08-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-29 00:00:00 UTC to 2016-09-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 29

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 112016-04-11 00:00:00 UTC2016-04-18 00:00:00 UTC101
Apr 182016-04-18 00:00:00 UTC2016-04-25 00:00:00 UTC000
Apr 252016-04-25 00:00:00 UTC2016-05-02 00:00:00 UTC000
May 22016-05-02 00:00:00 UTC2016-05-09 00:00:00 UTC000
May 92016-05-09 00:00:00 UTC2016-05-16 00:00:00 UTC000
May 162016-05-16 00:00:00 UTC2016-05-23 00:00:00 UTC000
May 232016-05-23 00:00:00 UTC2016-05-30 00:00:00 UTC000
May 302016-05-30 00:00:00 UTC2016-06-06 00:00:00 UTC000
Jun 62016-06-06 00:00:00 UTC2016-06-13 00:00:00 UTC000
Jun 132016-06-13 00:00:00 UTC2016-06-20 00:00:00 UTC000
Jun 202016-06-20 00:00:00 UTC2016-06-27 00:00:00 UTC000
Jun 272016-06-27 00:00:00 UTC2016-07-04 00:00:00 UTC000
Jul 42016-07-04 00:00:00 UTC2016-07-11 00:00:00 UTC000
Jul 112016-07-11 00:00:00 UTC2016-07-18 00:00:00 UTC000
Jul 182016-07-18 00:00:00 UTC2016-07-25 00:00:00 UTC000
Jul 252016-07-25 00:00:00 UTC2016-08-01 00:00:00 UTC000
Aug 12016-08-01 00:00:00 UTC2016-08-08 00:00:00 UTC000
Aug 82016-08-08 00:00:00 UTC2016-08-15 00:00:00 UTC000
Aug 152016-08-15 00:00:00 UTC2016-08-22 00:00:00 UTC000
Aug 222016-08-22 00:00:00 UTC2016-08-29 00:00:00 UTC000
Aug 292016-08-29 00:00:00 UTC2016-09-05 00:00:00 UTC101

What Hacker News says

2 sources
There are many sites that showcase their simplicity with free software: https://www.palletsprojects.com/ (python / lektor) - source: https://github.com/pallets/website http://flask.pocoo.org/ (python / flask) - source: https://github.com/pallets/flask-website/ https://developers.google.com/web/fundamentals/ (appengine / jekyll) - source: https://github.com/google/ Have you tried writing a progressive web app using Polymer?
In Ask HN: Simple client websites – What do you use?
As someone who spent way too much time building Django inspired template engines (Jinja, Jinja2, Twig, etc.) I must say this is really cool and very close to what I wanted to build myself for Rust but did not have the time. > Tera uses serde which means that in the example above Very good. But serde needs to get stable :( > beautiful html output out of the box (ie no need for the {{- tags) This is a request that comes up often but I tested this so much and always came back to not doing magic. It breaks too many applications in unintended ways (particularly plain text output). > able to register new tags easily like the {% url ... %} in Django I would not do that again. Jinja has an extension interface and I regret adding it. I much rather have people just expose functions to the templates. That said, in Rust that might be not a good i
Read the rest
dea because there are no keyword arguments so make it makes sense there. > no macros or other complex logic in the template […] include partial templates Another thing i strongly disagree with but I can see the motivation. Macros in Jinja I prefer so much over includes because it becomes clear what values exist. Includes become really messy unless you are very organized. Macros (which are just functions) accept the parameters and it becomes clear what the thing does. Just look at that macro as an example: https://github.com/pallets/website/blob/master/templates/mac... It's absolutely clear what it accepts as parameters. If that was a partial include the "caller" needs to set up the variables appropriately and there is no clear documentation on what the template wants etc. But awesome to see this happen for Rust!
In Introducing Tera, a template engine in Rust

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.