Talk:World Cruising and Sailing Wiki

From CruisersWiki

Revision as of 15:25, 11 February 2016

Homepage Discussion Page

Suggest new content sections/headings, post questions, general suggestions, etc., below. Click on the "+" sign next to "Edit" (top of page tab) to open a new topic for discussion or "Edit" to add to or comment on existing topics on this page.

• What do you think of having a section at the bottom of the page for "Blog Posts Related To This Location" in which people can post a link to their blog, provided the page referenced is related to the page in question? This would make it very easy for cruisers to get detailed personal impressions, including photos, of the places they are researching? LifePart2 19:10, 5 May 2013 (BST)

Wrong link to Creativecommons.png

There is an img tag on every page here that refers to http://www.cruiserswiki.com/images/f/fe/Creativecommons.png, apparently it should read as http://www.cruiserswiki.org/images/f/fe/Creativecommons.png.

It takes quite a while (c-ca 2.5 min) for this request to time out. Perhaps this is why on page edit a tool bar loads only after such a delay.

--Vadp 11:19, 9 February 2015 (GMT)

The little investigation revealed that the culprit is the MonoBook skin of this wiki: when you switch to some other skin there is no load delay and, for example, google map widgets load up swiftly.

At the very boItom of every page made with this skin there is a link to http://creativecommons.org/licenses/by-nc-sa/2.5/ and the icon for this link is hardcoded to http://www.cruiserswiki.com/images/f/fe/Creativecommons.png:

    <div id="f-copyrightico"><a href="http://creativecommons.org/licenses/by-nc-sa/2.5/">
            <img src="http://www.cruiserswiki.com/images/f/fe/Creativecommons.png" alt="C.C. 3.0 License" width="88" height="31" />
    </a></div>

Apparently a fix this issue could be:

    <img src="/images/f/fe/Creativecommons.png" alt="C.C. 3.0 License" width="88" height="31" />

--Vadp 17:14, 10 February 2015 (GMT)

A workaround has been implemented -- see MediaWiki:Monobook.js. It seems to work fine in Firefox, Chrome and IE v.11 --Vadim 16:13, 19 April 2015 (BST)

A newer workaround was implemented at MediaWiki:Common.js. Although it is not able fully solve the problem for Safari --Vadim 15:25, 11 February 2016 (GMT)

Template:PartOf as a new "Navbar"

Santa Teresa Gallura test has a new feature which looks similar to the old Navbar at the bottom of a page (see Santa Teresa Gallura). In fact it's more than that, as it introduces a true article hierarchy from, say, a marina to a town, region, country, geographic area, the World. This hierarchy: (1) can explored and analysed by an user or an editor, (2) used by some software application, for example, to built a list of POIs for a whole region to be drawn at a chartlet or to allow user to transfer a set POIs to a chartplotter or some other navigation application.

As to it's visual presentation, then my feeling is that the top of the page could be a better location for it: once you open a page you'd be able to grasp some important information about the article at once, without scrolling a page: it's relation with other article, it's contents, then on the left -- links to a home page, wiki contents, etc. --Vadim 16:58, 10 February 2016 (GMT)

As I mentioned before, I am not sure I like the Navbar at the the top of the page. I think that users are by now used to see it at the bottom. Had we not had this history I would preferred it, like you, at the top. Having said that there were many mistakes in the Navbars of older pages. Many Germany pages in the North Sea also claimed to be in the Baltic, so its automatic creation will alleviate this problem.

As far as the Navbar aesthetics and position I propose that we give both arguments to the rest of the registered editors and go by the consensus. What do you think? --Istioploos 18:44, 10 February 2016 (GMT)

As per Istioploos advice the users are able to discuss it here --Vadim 14:17, 11 February 2016 (GMT)

I quite like the position at the top and it is a more logical position (as other editors have observed in the past), but I'd make two points: 1. It needs better graphical treatment, e.g. tabs as it looks like an editing mistake the way it is at present; and 2. I assume that Vadim is willing to apply this change across all the current Wiki pages for consistency. In the absence of either of these my answer would be no. ----Athene of Lymington 14:36, 11 February 2016 (GMT)

No problems, Gordon, with both of you points. Although #2 looks like a bit of challenge, but I wouldn't suggest this change without thinking of how to implement it. My feeling is that {{NavBar}} conversion could be automated, on the other hand I'm not quite sure about "Cruising Wiki Navigation" in its older, table, form. Perhaps categories creation would need some help, for the moment I don't see how to automate this process.

As for it's design, then my concern is not to overdo it. See, for example how it's made at the Wikivoyage. It's very simple there. Any suggestions? --Vadim 15:04, 11 February 2016 (GMT)