Thanks a lot to the great work by Henil @henilp105 in his GSoC project!
If you find something missing, let us know, the old page is still around on the GH pages URL: Home - Fortran Programming Language. All URLs and bookmarks should continue to work as expected and send you to the right place on the new page, if not please let us know, we will add a redirect to the new location.
One remark: maybe I had not noticed that before (on the old page) but I find it somewhat weird that the word Fortran does not appear in any of heading-like line, only in the ordinary paragraph text. So if anybody comes to this page by chance, sees a High performance parallel language but what a language is that?
I hate to do this but compare Julia main page: Full name in logo, Julia in the header “window” and Julia again in the first subheading (Julia in a nutshell)
We should make a full version of the Fortran logo. For most projects where I have a logo I now tend to make two versions, a small quadratic one and a full one, usually sharing the same shape and color scheme (like for TOML Fortran).
To add to the discussion: I would suggest adding some words explaining “Modern Fortran” in terms of the “new features or attracting features” in the very beginning (it helps the newcomer to feel the strength of the language).
Probably the new or attractive features might be:
array declaration and handling (it is really easy to declare array variables like python)
OO concept originating from derived types etc …
do concurrent use to speed up the computation (not in detail but just to highlight and display what is there for the newcomer from the modern Fortran)
Similar points to show the strengths of the "New avatar of Fortran or coming Fortran enhancements etc.
These are the few things in my personal opinion that MUST be highlighted in First page of the Fortran website.
I have spotted one funny: if I translate the site to Welsh, possibly using Google chrome’s build in service, I get the whole page translated, but if I ask for German on the top left drop down, only the central panel translates and the left and right panels stay in English.
Please do not read anything into my first two attempts being German and Welsh!
So going forward, which markdown is to be used with documents in the Learn
section? RST is typically used with Sphinx, but I see (artifacts?) things that make me
think it could be others. If more than one is supported, what is preferred?
@urbanjost Sir, for site we have only used myst-markdown (extensively for the entire site except the intrinsics ) and kramdown ( for intrinsics) . Please feel free to use any one of them for adding the documentation.
I don’t think we actually had used po-files for our initial translation of the jekyll served page. The first attempt was using string replacement via keys or complete page replacement, if I recall correctly. The translated strings are of course usable, but I don’t think there is a way to automate the import due to the non-standard format.
Yes, it was string replacement in a _i18n subdirectory.
I have kept a copy of that site but I have problems running jekyll on my Ubuntu, probably a version problem (ruby 3.0). Anyway, I can access the code of the files. I am not sure it will be faster than working from the automatic translations proposed by weblate.