I would like to call a vote, to make sure that the general strategy outlined above is agreed upon. I am talking about the structure of the page not the design picture - let us leave that for latter...
I am in favor.
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
External Modules: changed to three separate pages (they are not that full yet...)
About DUNE: removed list of modules and added short text on modular
structure with corresponding links
DUNE gallery: added links to the FEM/PDELab galleries. In addition to the Laplace problem
already on the page, I would at some point like to add a similar example with an FV code.
Features: added a section on discretization modules (not referring to any specific module
Using DUNE: added tutorials from fem and pdelab
Mailing Lists: added FEM/PDELab
Core Modules: added geometry/localfunction and added module dependency -
also added some links to different parts of the Wiki.
used alphabetical ordering as much as possible/reasonable. For the core modules
I used: common/geometry/grid/istl/localfunctions
I also liked to a dune-grid-glue page on the external modules page to make
it look similar to the other modules. I then removed the download instructions and
maintainer names because it is on the linked page and all other module entries
also do not include that information.
In general I would suggest that all modules (grid managers and others)
that we list on the homepage should at least provide a short page giving
the email address of the maintainer (who to ask) a
short list of features and download instructions (if available). I would
rather not have that information on the homepage itself.
This (10 line) page is as far as I could see only missing for
NetworkGrid and FuFem at the moment.
Thanks for these changes.
I'm not sure whether this flyspray task or the wiki page would be the right place for homepage revamp discussions.
But I don't like the module names in uppercase. We used lowercase module names so far, see for example the release notes
Why is a link to the discretization modules on the core modules page? They are prominently linked on the left side but per definition they are not core modules
The /fem subpage should be included asap because now some links are broken
Andreas, you used upper-case module names at coremodules, dune, gallery, publications and doc/index. I don't like that because it is harder to read, is considered as yelling and breaks the style, see for comparison download, releasenotes-2.1 and doc/doxygen.
I would like to make them lower-case and bold like at downloadext and discmodule.
Would you mind if I add at the bottom of the gallery page a DuMuX example and provide a link to www.dumux.org/gallery.html ?
Concerning the font. I do not really care as long as they in some way stand out a bit.
I like small caps (like we used in the dune user meeting proceeding) but could not figure
out how to do that on the web page. So just change the way you like. We can then compare
and always revert.
Concerning the Gallery: from my point of view the more examples we have, showing what is
possible with dune the better. So please add a link - again we can always remove it or
move it somewhere else if somebody objects...
I think it would be beneficial to have links to doxygen documentation for each module listed on coremodules.html
At least I just exspected to find the class documentation there.
BTW: I like the new release notes! with menu on the right hand side. Good job!
We cannot link to the documentation for the stable modules because we only provide the documentation of all core modules together. The sub pages in this documentation are crowded and scaring.
Providing only links to documentation of trunk seems bad to me.
Maybe we should update the stable documentation to 2.1.1 even if virtually nothing changed.
Gallery: fill section Finite Volume scheme on different Grids with content
Who can provide these FV images? If nobody volunteers I'll remove this section.
Installing External Libraries: add entry for Pardiso or remove it completely
Who can provide the installation instructions? If nobody volunteers I'll remove it.
Make decision on dunedesign image
There is an old TODO file from 2009 in dune-web. But I think most entries are outdated.
I do not think we need an entry for it, It is just another maintainance effort and ther should be instructions on the pardiso webpage anyway.
I am actually wondering whether anybody is using it. The last time I talked to Bernd, he told that they stopped using it because of its restrictive licence.
As threatened I removed the section "Finite Volume scheme on different Grids" from the gallery page.
Unless nobody convinces me that Pardiso is a great and necessary tool despite it prohibitive license it'll next to be removed. If you are convincing, I'll write it :-)
I would like to move downloads older than the current release from the page "Core module (stable)" to "Old releases" which contains only the old release notes. Currently the download page is cluttered and the change would reflect the page name better. Does anyone object?
I added links from the "Class documentation" page to the class documentations from dune-FEM and dune-PDELab. For dune-FEM I linked to /doc/html-current/ because the better matching folder /doc/html-trunk is empty. Please correct this, that's not right.
Currently the footer links (small banners) at the bottom of all pages do not what they promise.
Markup validator says: 2 Errors, 1 warning(s)
CSS validator says: "Entschuldigung! Es wurden die folgenden Fehler gefunden (1)"
Our Page Rank "?" is not our actual page rank, it should be 6.
The RSS is broken.
I'll have a look for 1, 2, and 3.
Can we drop 3 and remove it from the page. I think it is kind of old fashioned to show off by the page rank.
If not, could someone with access to the server check whether the Perl Skript from
http://www.fourmilab.ch/webtools/PageRank/
is properly installed?