Random TODOs related to the Wiki and infrastructure:
- it'd be nice to link to template and wiki sources (or maybe they are all in one repo; I don't know ikiwiki well)
- I'm close to having this working -- bkuhn
- something odd about /about /about/about /about/colophon links (and seem not present now)
- no history link for each page (usually by recent changes, etc) loses major wiki affordance, cf https://ikiwiki.info/users/joey/ ... looks to require configuration
- no diff link in rcentchanges loses major wiki affordance, cf https://ikiwiki.info/recentchanges/ ... looks to require plugin
look into lstlisting to see if we can do code highlighting or otherwise better presentation of it in HTML.
The Guide has this specific problem regarding the offsets of relative href links in a tags. http://pixelflips.com/blog/anchor-links-with-a-fixed-header http://css-tricks.com/hash-tag-links-padding/ http://community.sitepoint.com/t/fixed-header-change-default-starting-position-of-body-text-for-anchor-tag/21360 http://stackoverflow.com/questions/4996330/changing-default-starting-position-of-anchor
http://lifesforlearning.wordpress.com/2012/12/24/anchor-links-with-fixed-header-part-ii/
^ the one where you put it in with padding and take it back out with margin makes the links in the wrong place
We should probably try one of those solutions.
Figure out what we're doing with the second/third/first person issue and post to the mailing list.
Figure out how to make users/ work in ikiwiki.
- this works now?
k.copyleft.org never sends email to anyone for anything. It should do that at least for authentication.
SSL setup on lists.copyleft.org has problem that is somewhat undiagnoised.
an SSL Labs report compared to the SSL Labs report for lists.sfconservancy.org is interesting here.
Draft copy: build target that creates draftcopy PDF and somehow puts that on the web page too for guide-next. Make it part of build process.
on guide-next, monolithic link goes to the production one.
No footnote number reset on monolithic version.
SVG file needs additional pixels on edges to avoid clipping. The banner on the front page is now a PNG, but we have an SVG of it, but someone needs to bad the SVG file, as wolftune argues that this is the manner to address the issue.
Verify that the header and footer space on various pages look fine on small screen devices, and if not, propose changes to the templates to make sure it looks good.
Translation
Enable translation of wiki interface and pages, see https://ikiwiki.info/translation/ and https://ikiwiki.info/plugins/po/ ?
Document preferred approach to translating tutorial. It seems there are various technical approaches such as http://po4a.alioth.debian.org/man/man3/Locale::Po4a::TeX.3pm.php or language editions could be maintained independently (if any are ever created)
Gitorious migration -- is there anything else left to do on this?