The Great Ball Contraption Wiki
avatar 40.77.167.31

Category talk:Something needed

From The Great Ball Contraption Wiki
← $1

Catch-All List[edit]

Some things that are needed (all open for discussion, unless otherwise indicated). If special skills or roles are required to make the change, it is added parenthetically (like this):

  • Remove tables from the mechanism pages, making the example modules pages on their own.
  • Figure out why so many special pages are not being refreshed (sysop).
  • Figure out why the WikiForum on the main page is not being refreshed, except when the Main_page is edited (sysop).
    • Cache. It will refresh over time or when the page is purged. --ToaMeiko (talk) 01:41, 2 August 2015 (UTC)
  • Perhaps move this page to the GBC namespace?
    • I support this idea. --ToaMeiko (talk) 01:41, 2 August 2015 (UTC)
  • Add more Terms.
  • Create a template for terms? Template needed Done. ALITTLESlow: t/c 00:18, 12 July 2015 (UTC)
  • Create a rating system for modules to guide new builders. (advanced editor)
  • Set up the Extension:SocialProfile gifts (sysop). ALITTLESlow: t/c 00:18, 12 July 2015 (UTC)
    • Any ideas of what kinds of gifts we'd make? --ToaMeiko (talk) 18:32, 2 August 2015 (UTC)
  • A bot to delete outdated events from Upcoming GBC Events (programmer). ALITTLESlow: t/c 16:03, 13 July 2015 (UTC)
  • Amend site-wide CSS so that whitespace next to contents tables isn't so severe. See Talk:Conveyor. (sysop) Captainowie (talk) 08:35, 1 August 2015 (UTC)
    • While looking at the CSS, can you tweak the <pre> style so that it word-wraps on Firefox? (sysop) Captainowie (talk) 08:35, 1 August 2015 (UTC) Done. ALITTLESlow: t/c 19:42, 26 August 2015 (UTC)
  • Use Semantic Media Wiki inline queries instead of Category pages. If I hear no objections to this I might start making these changes myself. Captainowie (talk) 08:35, 1 August 2015 (UTC)
    • Actually, we can probably do away with using categories at all if we make full use of SMW. Does anyone know if anything uses it at the moment? It'd probably take a little bit of thought to decide exactly what and how we'd want to mark up, but it could be quite handy once everything's marked up. Captainowie (talk) 08:22, 2 August 2015 (UTC)
      • Can you say more about how this would replace the functionality of categories? I i skimmed the semantic-MediWiki page and it wasn't obvious. How would it affect:
        • someone who is casually brushing through categories?
        • someone who is trying to drill down to answer a specific question?
        • editors?

ALITTLESlow: t/c 20:06, 2 August 2015 (UTC)

Owen's thoughts on SMW[edit]

Weak SMW Proposal[edit]

So, at the moment we use Category tags for logical groupings of content: Terms into a dictionary, etc. which is fine - that's what they're for. But often we use the category page as an article, so that, for example, we talk about lifting mechanisms generally, then have a list of lifting mechanism articles on this site. There are a couple of (admittedly not crucial) problems with this approach:

  • We have to deal with Category:page_name for everything, which is a bit ugly (both in making links to the category 'article', and in the heading of the page itself)
  • We can't have any text after the list of articles
  • Breaking up the list by letter of the alphabet doesn't make much sense when there are only a handful of items.

The easy way around these is to use ordinary articles for things that should be articles (like lifting mechanisms generally), and use SMW to include in those articles a list of other articles that are tagged with the category. For example, this could be the page about widgets, and I could include here a list of the other widget articles like so:

This list was generated with {{#ask:[[Category:Widget]]|format=ul}}. I will call this the Weak SMW Proposal. It neatly solves all the issues listed above, though I don't know if it introduces other issues. Maybe it's drastically harder on the server, maybe there's no way to nicely manage a large list, I don't know.

Strong SMW Proposal[edit]

Of course, we aren't limited to #ask-ing about categories. Anything that SMW knows about is fair game. I'm not sure what things it knows about by default (like Categories), but we can tell SMW pretty much anything we like. For example, for an article about a specific module, we can write [[Builder::Joe Bloggs]][[Parts::357]], and on some other page (or even use the Special:Ask page for interactive queries) have a list of all modules built by Joe Bloggs with fewer than 400 parts (that have instructions, and that were displayed at BrickShow '14 or '15, and ...). In order to do that we'd need to put effort into getting everything marked up. I'll call this the Strong SMW Proposal. It is a fair bit more work, but gives us a lot of flexibility.

So, to answer the "how would it affect" questions:

  • Casual browsers - Weak: It'd look neater; Strong: It'd look neater
  • Searchers - Weak: It'd look neater; Strong: Could potentially get their answer in one hit, if the right things were marked up
  • Editors - Weak: Once the transition has been made (and I'm willing to do the bulk of that), minimal impact; Strong: We'd need to decide what things to mark up, and everyone would need to be vigilant in applying that markup. Templates should help here.

Thoughts? Captainowie (talk) 13:44, 5 August 2015 (UTC)

I agree with the weaknesses pointed out in the current way of doing things. Although having just a few things in the alphabetic list doesn't bother me. Nonetheless the Weak proposal seems to address all these issues and doesn't break categories, so it's sounds good to me. "Strong" doesn't sound like an all-or-nothing approach. We can be strong on some things and weak on everything else. I don't think every editor would have to be vigilant on markup as long as enough are vigilant and willing to follow-up to fix edits. I would say go for it on the Weak proposal and propose Strong markups on a case-by-case basis. And we should update the Manual_of_style accordingly. ALITTLESlow: t/c 02:44, 11 August 2015 (UTC)
Right, I'll get started on the Weak version when I have some spare time. Captainowie (talk) 09:40, 12 August 2015 (UTC)

Ok, I think I've successfully implemented the Weak SMW Proposal. Let me know if there's anything that doesn't look right in any page that used to be a Category (An admin will have to change the links on the Main page to point at Lift mechanism and widget instead of their categories. Captainowie (talk)
Having done this, I'm certain that the Strong SMW proposal (or at least some elements of it - as mentioned, we don't need to go strong for everything) are the way to go for articles about individual modules. Now is the time to bring this in, because we've only got one such article, and that's LEGO GBC Stair Lift, so we won't need to go changing a lot that's already done. I've added to that page some of the markup that I think would be useful. All we need to do is ensure that these elements are in the template for future Module articles, and we're all set. We can even use this to generate the tables that are in the current lift mechanism pages, as I've done (roughly) on the step feeder page. Captainowie (talk) 09:11, 23 August 2015 (UTC)