-
Notifications
You must be signed in to change notification settings - Fork 1
/
TODO.txt
134 lines (112 loc) · 7.51 KB
/
TODO.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
Possible list of things to write about:
- wordpress
- high school
- peter thiel, elon musk, travis kalanick, jeff bezos, mark zuckerberg
- bertrand russell
- the value of books
- neoreactionaries
- the difference between "knowing about a topic" and "knowing what experts/the mainstream think about a topic"
NEW:
- figure out if img {max-width:100%;height:auto;} is a good idea.
- make side bar responsive: as gwern notes, there are TWO kinds of
navigational information. one is site-specific, so home, about, feed,
comment, and website source. the other is page-specific, so the table
of contents, permalink to page, and page source. the site-specific
things can stay at the top (where it has always been), but having the
TOC and other page-specific stuff in the same place or in the page is
less useful. it's hard to find things in the page and easy to get lost
from the overall structure of the page when there are many headings.
one way is to make each page small and manageable, but as someone who
suffers from low working memory, shouldn't i be helping my readers by
always presenting the overall structure of the page to the side? I
like the design in
<http://www.stephendiehl.com/posts/essential_compilers.html>, but
unfortunately that page displays the *global* (i.e. site-specific)
stuff on the side, not page-specific stuff. By the same author:
<http://dev.stephendiehl.com/hask/>, which is much nicer (this one is
more fancy, and actually expands subsections as the user scrolls; I
don't need this. However, one annoying bug is that if the TOC is too
long, the user can't even see the whole TOC! There has *got* to be
something better (hmm actually on further experimentation, it appears
that something as simple as `overflow: auto` fixes the problem.
great!)). Also some browsers like elinks and firefox with vimfx can
easily go to the top/bottom of pages, but i have to remember that most
people aren't as obsessed about customizing browsers, so it would be
good to have an easier way to navigate a page.
The sidebar should also be responsive, in that when the width
becomes too small, the display "squishes" into the original (i.e.
current) form.
One thing to consider: could people find this annoying to browse? I
personally dislike mobile sites that try to show the navigation bar
when i scroll up, since it often activates when i don't intend it to
(so there could be an analogy here, where a user doesn't expect the
sidebar to stick, and gets annoyed when it doesn't behave like they
expect it to). also mobile readers probably lack attention span
more: but which direction should this make us update in? should we
say "give them what they want, by showing them more things to click
on"? or "give them the overall structure so they know where they are
since they are forgetful"? or "give them a clean column of text
without distractions and maybe we can keep them here longer"?
this is a distinction gwern recently made as well, though i think
his solution is suboptimal (since the TOC doesn't stick).
something like the following works, after some quick hacking. of
course, more adjustments will become necessary. note that this is a
completely javascript-free solution.
```
@media (min-width: 48em) {
div#TOC {
position: fixed;
left: 0;
top: 10px;
bottom: 0;
overflow: auto;
}
h2#TOCheading {
border-bottom: none;
}
}
```
NEW VERSION (works with site after switching to just pandoc and makefile; note, you must surround the content div with a content_container div):
```
@media (min-width: 50em) {
nav#TOC {
position: fixed;
left: 0;
top: 4ex;
bottom: 0;
overflow: auto;
width: 15em;
display: block;
}
h2#TOCheading {
border-bottom: none;
}
div#content_container {
padding-left: 15em;
}
}
```
See also
<https://stackoverflow.com/questions/21896151/css-and-div-with-header-and-body-with-scrollable-content-and-fixed-sidebar-to-r>
for getting the top navbar and sidebar to play nicely. (set width in
the sidebar and conditionally set a left-margin in the top bar)
Related discussion for Wikipedia: https://www.reddit.com/r/wikipedia/comments/137e7d/i_wish_the_contents_box_followed_you_at_the_left/
- make mathjax the default math display if javascript is available, but
*somehow* detect and switch to image-based math (like wikipedia's
default) when javascript isn't available. moreover, somehow just show
the raw LaTeX in an unobtrusive way when the user is on a text-only
browser.
- decide what to do about the problem of adding multiple languages/other parameters.
right now the structure is flat, i.e. everything comes after issarice.com/ . But what if we have another language, and want to have pagename1 for both languages (maybe they are even the exact same word in each language).
One solution is subdomains, but this is a bit tricky if one wants to have a locally-generated site. We could also do something like issarice.com/wiki/en/pagename1 for the english page, but then this breaks compatibility with what already exists. One solution is to have all the main pages flat (which are english for the time being), but then have a few "blacklisted" pages that cannot be created. This is already the case with "tags", "images" (though this one isn't really true, since images are added to the flat issarice.com/ ), "static".
We could then add to this blacklist e.g. single alpha characters a..z, which we can use for further things.
Like 'c' could stand for "content", so we could then just have issarice.com/c/wiki/en/pagename1, for instance. Then still the most obvious place to go (which is issarice.com/pagename1) will work, while the more "logical" placement will also work.
- maybe add backlinks (like in roam or obsidian)
OLD:
- import remaining pages from github pages site. & add more notes files.
- on tags, show the number of items in each tag in parentheses
Random things to write about:
- sensible general policy for making thoughts public? I feel like most of my thoughts aren't novel at all. And there are also a lot of thoughts that are momentarily exciting but which become much less exciting after sleeping on them. Is it a good idea to write these down? How much googling/searching/asking questions on various places be reasonable before I jot down an idea?
In general there are "research" type pages that summarize things i've read, and more "musing", "reflection", or "opinion" type pages that don't involve detail-oriented research but are more like summarizations of the vast amount of information i've consumer over years, or like just based on my limited life experience. So that epistemic stance is important to communicate.
- sensible policy for signalling/sales? especially in a "reflective equilibrium" sense. for instance, I don't like it when people pester me with things I'm not interested in, so I shouldn't pester others with similar things. but also I want others to give feedback on my work, and I'm fine with giving feedback on others' work.
There is a similar question about a sensible general policy for giving upvotes/downvotes/likes/reactions on comment threads or facebook posts or whatever. Because every time you give a "like" on one comment in a thread and not another, you are getting others to pay more attention to the comment you liked.