Talk:Saint Kitts and Nevis

From Wikivoyage
Jump to navigation Jump to search

Would this source be useful for cruise specific information? (the actual St. Kitts and Nevis article consists of factbook information, but there is some background and general stuff on the website): Sailingahead.com - Explore the World Offshore

Would it be better to have a seprate page for Nevis? I'm living on Nevis for 2 months and would like to add more information about it but most of the page seems to be about St Kitts. July 5th 08

Should Basseterre continue to have its own article?[edit]

Right now, it does, but this article nevertheless has a bunch of specific listings on it. Nevis has a single article. It looks like it would make sense for Saint Kitts to have a single article, but for the article for the entire federation to have no specific listings. What do you think? Ikan Kekek (talk) 09:21, 15 September 2018 (UTC)[reply]

It seems to me that each island has a region and a city article. Should we perhaps remove the island article and have a region article for the whole country, with no listings in it, and then as the destinations underneath have the 2 city articles? --Comment by Selfie City (talk about my contributions) 13:53, 15 September 2018 (UTC)[reply]
I wouldn't really cut it down to one single article for the whole country. I'd suggest one bottom-level article for each island and possibly a separate article for Basseterre. Just as it is now (Charlestown (Saint Kitts and Nevis) redirects to Nevis). ϒpsilon (talk) 14:13, 15 September 2018 (UTC)[reply]
Oh, Charlestown is a redirect. --Comment by Selfie City (talk about my contributions) 14:26, 15 September 2018 (UTC)[reply]
Either way, don't specific listings have to be moved or removed from this article? Ikan Kekek (talk) 15:26, 15 September 2018 (UTC)[reply]
Yes, I think so. --Comment by Selfie City (talk about my contributions) 15:34, 15 September 2018 (UTC)[reply]
Yes, listings should definitely be moved into lower level articles. ϒpsilon (talk) 15:36, 15 September 2018 (UTC)[reply]