I noticed that the arrow on the right of the drop-down menus looked a bit closer after Josh's last change, but I don't think it's a problem (it's not on my screen, anyway). (though, I think I prefer the anchors on the left for the sections)
One annoying think about the anchor links is that linking directly to a section puts the section name underneath our top menu... that's kinda annoying, but not sure how to avoid it. Maybe make the menu auto-hide unless you're scrolled all the way to the top? On Tue, Mar 22, 2016 at 2:34 AM Christopher <[email protected]> wrote: > I think I updated all the existing pages covering that, but the whole site > could do with a cleanup and reorganization, along with additional howtos. > > On Mon, Mar 21, 2016, 22:17 Josh Elser <[email protected]> wrote: > >> Moved the anchor links to the right side again :) >> >> In your post-commit hook, `mktemp` doesn't work on OSX with the >> `--tmpdir` option. >> >> Have you made a canonical "How to update the website" page yet? >> >> Christopher wrote: >> > I didn't see anything which indicated we had those in the past. Maybe it >> > was something CMS was doing special, but I figured out how to get the >> > section links present. >> > >> > On Sat, Mar 19, 2016 at 5:21 PM Christopher<[email protected]> >> wrote: >> > >> >> I don't think I ever noticed those before. There might be a kramdown >> >> option we can turn on. >> >> >> >> On Sat, Mar 19, 2016, 16:55 Josh Elser<[email protected]> wrote: >> >> >> >>> One thing I just noticed is that the quick "anchor" links at the end >> of >> >>> each header (specifically on the release notes page) are missing. >> >>> >> >>> I liked those because it was easy to click the header to get a url and >> >>> use it to reference. >> >>> >> >>> The IDs are still there on each section, just the quick link to get >> >>> there is missing (so I have to look it up). Not sure if there is an >> easy >> >>> way to get this with Jekyll (or if it'd just be something we have to >> do >> >>> by hand). >> >>> >> >>> Christopher wrote: >> >>>> There's plenty of room for improvement to the new git/Jekyll site. >> For >> >>>> instance, we can start blogging there, so we have greater control >> over >> >>> the >> >>>> look and feel of our blog posts, and so any committer can blog >> without >> >>>> needing to request an extra account. At some point, I think it'd be >> >>> good to >> >>>> migrate our existing blogs over to this. >> >>>> >> >>>> Another thing we can do is put our release notes in an RSS feed, so >> >>> users >> >>>> subscribe to new release announcements/notes. I might put some >> thought >> >>> into >> >>>> that at a later point in time. For now, I'm just happy we're on git >> for >> >>>> everything except the dist.apache.org/release mirroring (for which >> I'm >> >>>> totally fine using git-svn). >> >>>> >> > >> >
