Template talk:Regionlist

From Wikivoyage
Jump to navigation Jump to search

Map placement[edit]

The current map placement, which puts the map after the table of regions, is obviously not ideal. However, trying to modify the template so that the map appears next to the region key causes clashes with quickbars, the TOC, and other page elements. If anyone out there has the time and ability to re-work this template to use divs instead of a table it might go a long way towards improving the usability and look of the template... -- (WT-en) Ryan • (talk) • 15:54, 28 May 2007 (EDT)

I think User:(WT-en) NJR ZA is still working on perfecting it, he's just really busy with work at the moment... On California I just moved the map outside of the template for now, which achieves the desired result... until we find a way to do that within the template – (WT-en) cacahuate talk 16:58, 28 May 2007 (EDT)
I'll copy it to a local wiki and have a go at getting it to work correctly. Will report back here. --(WT-en) NJR_ZA 02:00, 29 May 2007 (EDT)

Map size[edit]

How can I shrink down a map within the template? See Sweden(WT-en) cacahuate talk 02:19, 15 October 2007 (EDT)

The template supports a regionmapsize parameter, but it was not documented. I have added it to the template documentation now. See change on Sweden --(WT-en) NJR_ZA 03:32, 15 October 2007 (EDT)
Cool, thanks! The maps don't seem to appear in the Region section any longer, is it intentional that they are forced below the toc now? Not necessarily a complaint, but just noticed the difference – (WT-en) cacahuate talk 13:15, 15 October 2007 (EDT)
Intentional. On many country pages (USA and others) the region map ended up between the TOC and quickbar, leaving an extremely narrow area for text. On Sweden that would actually be OK, 'cause it's a narrow map, but mostly it just did not look good. --(WT-en) NJR_ZA 13:49, 15 October 2007 (EDT)

Number of Items in Regionlist[edit]

Is there a limit of items in the Regionlist Template? I've been working on Germany, which I'm breaking up into 16 regions (for the 16 states, for the time being, since that's how the actual articles are written), and after the 15th item I get an error like ({{{{region159items}}}). I found if I break it into two region lists and start the numbering again at 1, the problem is avoided. Almost definitely not a typo, I'm guessing something with the template code..... Any thoughts appreciated. (WT-en) hokiesvt 16:21, 17 March 2009 (EDT)

Improving our Template:Regionlist[edit]

Swept in from the pub

This is long overdue from six years ago when Ryan perspicaciously said at Template talk:Regionlist:

The current map placement, which puts the map after the table of regions, is obviously not ideal. However, trying to modify the template so that the map appears next to the region key causes clashes with quickbars, the TOC, and other page elements. If anyone out there has the time and ability to re-work this template to use divs instead of a table it might go a long way towards improving the usability and look of the template... -- (WT-en) Ryan • (talk) • 15:54, 28 May 2007 (EDT)

Now the map is alongside the table of regions and often (especially with the small screen widths that are found on laptops and smart phones) the list is squeezed into a worm or under-runs the map. -- Alice 23:21, 27 January 2013 (UTC)

Layout problems[edit]

1. TOC + Regions List + Map all three next to each other takes up too much space on many screens, especially with wide maps (eg Bali).

2. TOC floats left, Regions List flows past bottom of it and jumps left jarringly.

@1, let's put the Map above the Region List. Maybe put <br clear="right"> after the Map in the template to do that. This would give us room for larger maps which would be nice for readability, too. Shall we? --Rogerhc (talk) 21:36, 5 February 2013 (UTC)

@2, the jump left is fussy to prevent with CSS but maybe with some experimentation might be done. --Rogerhc (talk) 21:36, 5 February 2013 (UTC)

If I'm not mistaken, we are going to do away with the left floating ToC in destintion guides in the near future, so we needn't base all design decisions on the problems the current TOC poses. There's still a lot of room for improvement, though, so I hope this comment doesn't suppress new ideas.
I tend to agree that we should feature our maps more prominently (by putting them above the regionlist). Nowadays they're getting to be rather pretty, and are hugely useful. As we (I think) are beginning to introduce image maps, putting the regionlist template right beside them will be less crucial, as they will themselves be a tool for site navigation. --Peter Talk 05:39, 6 February 2013 (UTC)
Most people have more horizontal screen space than vertical. Having the map side-by-side with the legend makes it easier to correlate colors. LtPowers (talk) 18:22, 16 February 2013 (UTC)


I've noticed that only few articles used the various parameters regionXitems (furthermore few of them by mistake use them in place of regionXdescription).

In the past, in the Italian version of this template, I've eliminated them, converging their content into the relevants regionXdescription. In this why is simplified the template and the creation/maintanability of an article.

If you think that this approach can be suitable also for the en:voy version, I can take in change the task to adjust all the involved articles through a bot. Let me know. --Andyrom75 (talk) 15:32, 4 June 2013 (UTC)

No way. United States of America needs them, for sure, and they're useful in many other similar situations. LtPowers (talk) 20:04, 4 June 2013 (UTC)
As you prefer, but take into account that to show those information regionXitem it's not strictly necessary, see it:USA for example. The difference consist just on the way you write regionXdescription. --Andyrom75 (talk) 21:39, 4 June 2013 (UTC)
The items are pretty useful for groupings like with the USA, but even more so for district schemes. Several of our star guides use it, e.g., Washington, D.C.#Districts, Chicago#Districts, etc. One could just list the items in the description, but I think it's cleaner the way it is now. --Peter Talk 21:44, 4 June 2013 (UTC)
Agreed; no offense to the fine editors at it:voy, but I don't think that's a very good way to present that information, either aesthetically or from a usability standpoint. LtPowers (talk) 22:45, 4 June 2013 (UTC)
Ok, no problem. It was just a proposal :-) --Andyrom75 (talk) 23:21, 4 June 2013 (UTC)

Right or left-aligned map caption[edit]

Can we make the map caption ("regionmaptext") left-aligned? Or if there are cases where this would be a bad idea, can we have an optional parameter to make it left-aligned? Captions for ordinary images are left aligned. And the way the map caption always runs up hard against the "enlarge" icon is not pleasing to the eye (IMO), and readers not familiar with the purpose of the icon may assume it relates to the caption, rather than to the map. Nurg (talk) 20:44, 9 July 2013 (UTC)

I kind of wonder why we need text saying, "this is a color coded regions map." Shouldn't that be obvious from the image itself? It seems to me like just a very small bit of wasted vertical space. --Peter Talk 21:51, 9 July 2013 (UTC)
In it:voy I've suppressed the regionmaptext parameter so I show only the image/map without any kind of text below it. If you like this approach just let me know and I can take in charge both the modification of the template and the cleaning of the article through bot. --Andyrom75 (talk) 19:19, 10 July 2013 (UTC)

Alt text for the visually handicapped?[edit]

Does this template in it's current form actually accept parameters for alt text? --W. Franke-mailtalk 19:29, 10 July 2013 (UTC)

Not currently, but it can be easily implemented. In the it:voy version I've used a standard alternative name identical for all the maps but it can be personalized with the regionmaptext that we were discussing above. --Andyrom75 (talk) 23:07, 10 July 2013 (UTC)

Overlaying region descriptions[edit]

With a wide region map (and narrow browser window) the map overlays the region descriptions, sometimes making the text unreadable. See e.g. Southern Finland at window width below 500px (I need some 725px before the layout gets good). The map in that article is quite wide, which allows information on the map to be actually seen, which otherwise is good.

A solution that puts the region list below the map when the text column becomes too narrow would be optimal. Otherwise a parameter for wide region maps ("text_below=true"?) would solve the problem in many cases.

--LPfi (talk) 07:28, 27 April 2016 (UTC)

Is anyone still designing web pages for fewer than 800 pixels anymore? Powers (talk) 17:36, 27 April 2016 (UTC)
Less than 800px may be unusual for desktop and even laptop displays, but a wide display allows having several windows side by side. I am now using a 560px window, which gives about optimal line length where there are images in the margin, somewhat too long lines elsewhere. I would prefer a narrower browser window to avoid it overlapping the editor or a second browser window (the mail client is usually on a separate virtual desk). 800px would be horrible without padding, where such a window is necessary I maximize the window to get essential information and flee elsewhere as soon as possible. --LPfi (talk) 19:40, 27 April 2016 (UTC)
I understand your plight, but my original question remains unanswered. It was my impression that most design assumes about a 600px column width at minimum (that is, 800px minus interface elements), but my information could be out of date. Powers (talk) 21:27, 27 April 2016 (UTC)

Mobile rendering issue[edit]

The table used in this template relies on the default styles of a table.

In mobile all tables have collapsed borders by default so as a result the color of the key appears cramped.

Please can you explicitly add this style to the table to make this render better on mobile?:

    border-collapse: separate;
    border-spacing: 2px;

Jdlrobson (talk) 22:59, 29 August 2016 (UTC)

I think this is now done - the template that needed to be modified was Template:Regionlist/item. Let me know if further changes are necessary. -- Ryan • (talk) • 00:09, 30 August 2016 (UTC)

Use in another language[edit]

How to i use this template in another language's Wikivoyage? —The preceding comment was added by Sony dandiwal (talkcontribs)

You'll need to create a new template on that Wikivoyage language version and write the appropriate template code. You could use this template as a basis, but its parameters would need to be translated, and you have to be careful to maintain attribution. Powers (talk) 00:58, 9 December 2016 (UTC)
okay, thank you Powers - Sony dandiwal (talk) 03:53, 9 December 2016 (UTC)

"Hack" for toggling static and dynamic maps on destination articles[edit]

This template can be "hacked" without listing regions in order to offer both a static map and a dynamic map on city/destination articles without cluttering the article. See Manhattan/Central Park for an example. The code is:

| regionmap=Centralpark map.png
| regionmaptext=Map of Central Park
| regionmapsize=450px
| regionInteractiveMap=map1
| regionmapLat=40.78216
| regionmapLong=-73.96660
| regionmapZoom=14

Nelson Ricardo (talk) 21:23, 5 June 2021 (UTC)

On mobile, when I press the blue link to switch to interactive map, nothing happens. Is that correct? --Comment by Selfie City (talk | contributions) 00:42, 6 June 2021 (UTC)
D'oh! Thanks for pointing that out. I hadn't tried on my smartphone, only on my laptop. Hopefully, someone with the requisite template-editing knowledge can review and fix. It's not just happening when "hacked". Portugal uses the template as an actual region list, and it, too, fails on mobile. Nelson Ricardo (talk) 01:45, 6 June 2021 (UTC)
@Andyrom75, when you get a chance, would you please see why Special:Diff/4073000 isn't working on mobile? Thank you! Nelson Ricardo (talk) 13:01, 6 June 2021 (UTC)
Nelson Ricardo, I discussed this topic time ago in lounge. Is an old wikimedia bug that prevent it to work on mobile. --Andyrom75 (talk) 13:31, 11 June 2021 (UTC)

Using template Regionlist without a map[edit]

Swept in from the pub
  Region 1 name
Region 1 name is ...
  Region 2 name
Region 2 name is ...

When you use the template:Regionlist without a map, you get a result as shown above. But without the map, the colored rectangles have no function. Shouldn't the rectangles be suppressed in this situation, by making some changes to the template? --FredTC (talk) 13:19, 5 June 2021 (UTC)

That makes sense to me. Ground Zero (talk) 14:00, 5 June 2021 (UTC)
I would recommend always including a map for a region list, whether static or dynamic, or both. Which region do you feel doesn't need one? Nelson Ricardo (talk) 17:24, 5 June 2021 (UTC)
Extraregion? --Comment by Selfie City (talk | contributions) 20:00, 5 June 2021 (UTC)
Yes, they should be suppressed in that situation. And I think the answer is when there's a region that doesn't or doesn't yet need subregion articles but has clearly-defined regions that can be effectively described in a "Regions" section. We could say that should be a subsection of "Understand" in that situation, but that doesn't fundamentally change things, I think. Ikan Kekek (talk) 20:09, 5 June 2021 (UTC)
I feel that an extraregion should still include a map, but if you prefer to not have one, perhaps don't use the Regionlist template and just use bullets instead. Nelson Ricardo (talk) 21:11, 5 June 2021 (UTC)
Agree with GZ here. SHB2000 (talk | contribs | en.wikipedia) 21:18, 5 June 2021 (UTC)
I've made an edit to {{Regionlist/item}} that allows the colour box to be bypassed: Add |nocolor= somewhere among the parameters with anything following the "=", and the colour box should be suppressed. It works in a way that doesn't alter any existing regionboxes, so there is no need to worry about that. I also made an attempt to implement that into {{Regionlist}}, but that didn't work out the way I wanted it to. I don't have much free time to put into it right now, so I'll have to leave it at that for now. If anyone wants to try their hand at adding the parameter into Regionlist, be my guest. I should say though, that personally I prefer the look of the white boxes before the text, but be your own judge: {{Regionlist/item|blue|Destination|Items|Description|nocolor=y}}
-- Wauteurz (talk) 12:19, 6 June 2021 (UTC)
Thank you for your effort Wauteurz. Your edit to Regionlist/item works well, but the way Regionlist has to use it, needs some more analysing. In the situation of Southern Russia there is a "call" to Regionlist with a map but also one without a map. In that case, the one without a map must show the color. Another situation is in Amsterdam where a map is not specified with te call to Regionlist, but there is a {{mapframe}} with colored areas used instead. So, there needs to be a way to handle this. I do have an idea for using the regionmap parameter in several situations:
1. | regionmap=The name of the region map
2. | regionmap=
3. | regionmap=same
4. | regionmap=mapframe
In situation 1 a map is displayes and the color are too. In situation 2 no map is displayed and no colors. Situations 3 and 4 have a key word at the place of the map name and do display colors, but no map. Situation 3 is for having more than one call to Regionlist with a map specified at the first call and the rest with same. Situation 4 is for having one call to Regionlist that takes its map from a {{mapframe}}.
Do you think I have covered all situations? If so, is it programmable? --FredTC (talk) 12:32, 7 June 2021 (UTC)
@FredTC: For clarity, I don't intend to automate {{Regionlist}} to check whether colours are needed in the article it gets called in. Disabling colours would be a completely manual process the way I plan to implement it. Southern Russia therefore isn't a problem case. Even if colour detection were automated, you could instead use {{Regionlist/item}} directly for the listing of Crimea there, but again, that isn't a case where there'd be an issue with the changes I have in mind. In any case, the change I have projected is to add in an optional parameter for {{Regionlist}}, which disables colours in every instance of {{Regionlist/item}} within it. The implementations of the template are simply too different from each other to reliably detect them, and the amount of cases where you would want to hide the colours are relatively few. Could you automate it? Without a doubt, but I am in no way capable of automating it. Someone else would have to do so.
Cases such as Amsterdam can be fixed easily. The dynamic map can be called from the {{Regionlist}} instead (and in all honesty, shouldn't all instances of Regionlist be unified somewhat?). If it is wanted, I can make some maintenance categories for Regionlist that throw the article into a category when, for example, there isn't a static map, there isn't a dynamic map, there are both a static and dynamic map (or neither of the two). This would pave the way for either automated or manual editing of these articles to (ideally), be like Portugal, which allows the user to choose between a dynamic and a static map. At the very least this would make documentation for the Mapmaking Expedition and Requests for maps a lot easier.
-- Wauteurz (talk) 19:07, 7 June 2021 (UTC)