The previous content of this page is found here
- [View source↑]
- [History↑]
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Broken link on the startpage | 1 | 19:59, 14 October 2020 |
| Discussions about enhancements of the Wiki | 7 | 14:29, 16 November 2016 |
| Style-Scripts | 10 | 00:54, 4 April 2015 |
On the main page https://openfoamwiki.net/index.php/Main_Page , you link to Source Code. This link yields 404.
In the new site structure, as logged in editors, we're missing an important "Page Tool", namely: "What Links Here"
I'm asking for this feature, because it's a somewhat important tool when trying to figure out how readers can easily find a particular page or not ;)
I was wondering about the organization of the wiki. What about using namespaces for each OpenFOAM version? This would allow the creation of a sort of a subwiki for each version that could work, without relations with the other version pages, as a reference for that particular version.
This way it would be possible to have same-titled pages but for different namespaces, somehow freezing a common structure for them.
Don't know if you already discussed about that.
Ref: https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces
Actually we already have categories for each version, which allows cross-referencing other versions if needed, e.g.: Category:OpenFOAM_Version_3.0.x - each category page does act as a wiki page.
What I mean is that we already have a very hard-time maintaining the existing content. Creating dedicated namespaces for each version would only make sense up to a point, for example, for keeping documentation on how to go from version A to version B. And still, that should be stored inside something like what we have for OpenFOAM_guide.
That said, if you already have a set of wiki pages that can be used as an example of the structure you have in mind, it will likely make it easier to see what you mean.
Ok. I see your point. Don't have already examples to show. Maybe better to not add more overhead on this. I'll stick with this configuration and focus effort on improving the content.
Thanks in any case! :)
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Thread:Talk:Main Page/Style-Scripts.
Can the text colours be upped a bit on the black ink? I do agree that high contrast text is a pain for the eyes, but too little contrast is also bad :(
You mean something like
p {
color: rgb(50,50,50);
}
instead of the current
p {
color: rgb(119,119,119);
}
To try it out you can use the developer tools built into Firefox. In the "Style"-tab (sorry. My Firefox speaks German so I've got to guess the translation) on top of the list of the included style-sheets there is a "New". After pressing that there is a text-pane where one can add CSS (just copy/paste the above)
I like the idea behind the original CSS to keep the main text light because that way emphasis is more visible. But your opinion is valued. Is 50 enough? I'd still like the text to be lighter
I wouldn't say 50, but 80 seems to the right amount.
p { color: rgb(80,80,80); }
Although I couldn't figure out in which CSS the paragraphs were defined... probably was looking at the code too fast :(
By the way, where can we edit our personal CSS styles? All I could find were the generic ones:
- Chameleon (default | Preview)
- Chick (Preview)
- MySkin (Preview)
- Nostalgia (Preview)
- Simple (Preview)
- Standard (Preview)
- bootstrapskin (Preview)
or did I interpret the news incorrectly or even dreamed about reading them?
No. There is an additional CSS (custom.css I think) that I'll have to add. Directly modifying the CSS you "see" is not a good idea as they are generated on the server and/or are part of the bootstrap framework (which is updated through new package-system of the Wiki-software. So changes would be lost the next time around). I'll implement that change (adding darker fonts) on monday
Thanks for pointing out that the old-school skins (Chick, Nostalgia etc) are enabled. I disabled them on the test installation because the new front-page doesn't look good with them (the old design was one big table. Because of this it didn't "reformat" on mobile devices. The new design is just one long page on non-Bootstrap-Skins). I'll disable these on monday too
The thing for trying other CSS I was referring to in the news was the bookmarklet in http://bootswatch.com/help/. You install that in the bookmark bar of the browser. When you click it you get a drop-down in the upper right corner that lets you select a pre CSS-style. The problem is that this only changes the current page. So I mainly used it to select the current style. Having chameleon with a different CSS is a) on one hand easy: I've only got to add two files. But this changes it for everyone b) in reality hard: if I want the user to choose there must be a second instance of chameleon that the user can choose (which only differs in these two files) and that (the second instance) doesn't play well with the "package manager". Also is the name of the skin hardcoded into the PHP-files of it (this is why I can't solve this with symbolic-link-trickery). My approach was "if somebody comes up with a better color-scheme or disgust about the current one is expressed by a number of people I'll think about 'splicing' the skin"
Another way to override the Wiki-CSS is https://addons.mozilla.org/de/firefox/addon/stylish/#id=2108
I should have looked for the news page again :(
How about having a dummy point on the template for allowing a user-side chosen Javascript to be placed there automatically, which would change the CSS on the client's side only? The Javascript could be something like as follows, which is something I have as a compressed form as a bookmark:
function() { var newSS, styles = '* { background: #E9E9E9 ! important; color: #000000 !important } :link, :link * { color: #3333EE !important } :visited, :visited * { color: #551A8B !important }'; if (document.createStyleSheet) { document.createStyleSheet("javascript:'" + styles + "'"); } else { newSS = document.createElement('link'); newSS.rel = 'stylesheet'; newSS.href = 'data:text/css,' + escape(styles); document.getElementsByTagName("head")[0].appendChild(newSS); } })();
But I guess the template doesn't allow for this kind of hacking :(
Anyway, if and when I get annoyed with the colouring, I'll share a bookmark here for quickly changing only the text colours, since it's hard to please everyone ;)
Sorry for the late reply, but lists weren't affected by this change :(
For example, see this section: FAQ/General#Where_is_FoamX.3F
