Reminder to investigate dreamhost's letsencrypt integration (https://www.dreamhost.com/hosting/ssl-tls-certificates/) and get lrug.org onto https.

Going to have a initial look at this - do we have a required URL structure for this? If not I think it's probably going to be more manageable to have yearly archives for meetings so I'll probably re-organise the files a bit if that's ok.

I wasn't sure of the best way to report this, but searching on http://lists.lrug.org/pipermail/chat-lrug.org/ fails with:

ht://Dig error

htsearch detected an error. Please report this to the webmaster of this site by sending an e-mail to: [email protected] The error message is:

Unable to read word database file '/dh/mailman/else/archives/private/chat-lrug.org/htdig/db.words.db'
Did you run htdig?

Need an ErrorDocument ref in a .htaccess file, and to actually have a 404 page.

There are enough "hey I posted my slides at <url>" style messages on the mailing list that it might be worth attempting some kind of scrape of the mailing list archives to try and find those links and add them as coverage links.

It's email so it's going to be hard, but might be worth while. Perhaps we could get the data and then crowdsource converting them into coverage links?

We used to host a SVN repo that had some uploaded presentations and code from talks. We have the SVN repo so could re-host, but maybe we need to source permission from the original authors? We should at least we rewrite the urls to go somewhere other than a dead svn repo.

We don't get any fancy twitter card / facebook post / slack unfurl stuff when sharing lrug.org links which isn't great. This article https://medium.com/slack-developer-blog/everything-you-ever-wanted-to-know-about-unfurling-but-were-afraid-to-ask-or-how-to-make-your-e64b4bb9254 has details on what metadata we should use to get better results.

This might mean we need to put more things into the frontmatter for meetings if we want to get super fancy - but we should start simple and at least get the page title and an image (the logo probably ?).

There's no record of it on the site, but it appears to have happened according to https://skillsmatter.com/meetups/167-lrug-meeting-august - maybe there's something in the mailing list archives and we can resurrect it from there.

There's a lot of frontmatter to deal with and some of it could be automatically populated.

We might want a task for generating new normal pages and then a specialization for each sub-type (podcast, meeting, book-review, nights, &c).

members-and-friends, posting-jobs, sponsors, the-lrug-irc-room, the "being the mitch" page, the logo fite pages

To help with letting people know what this repo is about and what we use it for.

Once all the old pages are redone we should do a final check for any rogue radius tags in the source files (search for <r:blah...>) and see what they are and if they can be redone or removed.

Probably a bunch of rewrite rules in the .htaccess

Might be something we can script the generation of from the old radiant? Or at least get all the old urls that way.

Hello,

I noticed that the WorkingWithRails link in the "Get In Touch" list is dead (http://www.workingwithrails.com/ return "WorkingWithRails is being retired." ).

Have a nice day

Middleman 4 is out (since Dec 2015 no less) so we should consider upgrading. We don't use a lot of other dependencies but it'd be a chance to bump our version of ruby and such too. When building the writing was on the wall about the changes coming in middleman 4 so we tried to not use anything we knew was going away. Handily, there's a guide to help us: https://middlemanapp.com/basics/upgrade-v4/

Looks like lanyrd is being left to die which is a shame for many reasons. The biggest shame for us is that since 2011 we've used Lanyrd to collect a load of links to videos, slides, write-ups, and relevant git repos. If lanyrd goes away we lose these links.

It's a bit weird to use lanyrd for this anyway, as the canonical artefact for a meeting should probably be the lrug.org page for it. We should:

1. scrape the coverage links from lanyrd while it's still up (is there an API?) so we don't lose them
2. work out some way of attaching them programatically to the meeting pages
3. do any digging neccessary to backfill links for meetings before we used lanyrd

about, speaking (speaking/tips): old pages that now redirect to readme.lrug.org
meeting-calendar and mailing-list: redirects elsewhere

Like #11 probably just some rewrite rules in .htaccess

On the current website there are separate feeds for categories but I don't see the categories set in the new files.
There is also a typo in the new files: creatd_by

The static list of names could probably be more interesting and inviting to people who want to find out about the sort of people they are likely to meet at an LRUG meeting.

At the very least we could pull in some avatars from somewhere (gravatar? twitter?). But perhaps there's a more dynamic source of information we could use to generate the list (attendee info from lanyrd, followers of the lrug twitter account, ???)

Of course, maybe the page is always going to be out of date or off-putting to prospective attendees so we should drop it entirely. It is also currently very out of date so we do need a "recruitment-drive" to update it if we do keep it.

Make book reviews work

The static /sponsors/ page could list the companies that have sponsored individual meetings by iterating through all the meetings to find those that have a sponsors part. We could then do something with it. Or at least linking to each meeting that had a specific sponsor.

Need to have a think about this a bit more. Maybe it's not a great idea, or we'd want the sponsor part to be somewhat more data-driven than the chunk of markdown that it is.

We have the concept of status in frontmatter so it would be nice to create pages as 'Draft' in #18 and have a new task for moving them to 'Published' and setting the published_at timestamp too.

The design of lrug.org is mostly "a dev did it without much thought", we should apply some modern thinking and make it nicer. Things to think about:

• mobile experience (currently no margins and horrid)
• no red dashed borders (so 2006)
• one of those cool webfonts (this one perhaps?)
• &c
• &c

Use same category stuff as meetings, book-reviews, & podcasts

For some reason the december post display is not working correctly. The link from the homepage currently takes us to https://lrug.org/meetings/2023/december/index instead of the normal URL we see with other posts, which would be https://lrug.org/meetings/2023/december . And at the 'index' path it doesn't load it's CSS correctly.

Here: lrug.org/source/meetings/2017/february/index.html.md

In Paul's talk description:

If you've done much programming, you've probably worked with binary, hexadecimal, and perhaps octal in addition to normal decimal numbers. But what about base three? And what about bass base three with a twist, where each digit can be positive or negative? Why would you even want to do that? It really exists, it's called Balanced Ternary, and it has some interesting properties.

Unless it's deliberate and part of the talk?

@h-lame

Pretty much every LRUG meeting has been filmed and the video hosted by Skills Matter. However, we didn't do a great job of populating lanyrd for old meetings (2010 or earlier), nor did we do anything for the period where lanyrd stopped working (2016 onwards). We should be able to scrape the videos from https://skillsmatter.com/groups/3-london-ruby-user-group#past_events and populate video links for all our talks. Might be some manual effort required in linking titles properly.

We've mostly dealt with the Pages and Redirect tabs from the admin interface so far, there's also the "design" and "assets" tabs to check. We've probably pulled everything across, or realised we didn't need it, but we should do a check to see what's there and work out what, if anything, we should do.