| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Until now, in the "Merge/Pull requests" of section of the main
webpage, there was no link to the commit guidelines. This would make
it hard for new contributors to know what is expected.
With this commit, a link to Gnuastro's commit guidelines has been
added in the second step of that checklist (that is about committing).
This was proposed by Manuel Solimano.
|
|
Until now, the video in the main webpage was for the RDA meeting of
2020 (which is already two years old!).
With this commit, to avoid making people think that Maneage is no
longer maintained, I just added the recording of the most recent talk
last week in the ESO ROSA2022 workshop.
|
|
Until now, we had only put the names of the Maneage chat rooms. To
guide new users on how to view those chat rooms (without necessarily
logging-in), we had only described the steps they need to take!
With this commit, a direct link to an element-based message room
viewer has been added under each name, so people can simply click on
it and see the latest discussions in that room.
This URL solution was found by Pedram Ashofte Ardakani.
|
|
Until now, the only way we had suggested for interested viewers to get
in touch with us was through Savannah. But that interface can be a
little too technical for some interested people.
With this commit, the Savannah part has been commented (not shown in
the top page), and instead some Matrix-protocol chat rooms have been
introduced to help new users easily contact us.
|
|
Until now, the copyright years were still for 2021!
With this commit, they have been updated to 2022.
|
|
As described in the previous commit, Maneage is now based in CEFCA.
But in the previous commit, I forgot to add the CEFCA logo to the top
of the main page as a supporting organization.
With this commit, the logo has been added.
|
|
From today (September 15th, 2021), I am employed by CEFCA, so it was
necessary to correct the "base" institute of Maneage also. In the
process, I also noticed that we had forgot to update the copyright
year of Maneage in all the pages, so they have also been corrected.
|
|
Until now in the main webpage, we were suggesting to call the new
branch (to start customizing) as 'master' (following the old Git
convention). However, Git has recently changed its default branch name
to 'main'.
With this commit, to be consistent with other newly created Git repos,
we are suggesting to call the main customized branch as 'main'.
|
|
Downloading the video directly is the lowest-level way to view the
presentation, so it was added as a proposed option.
|
|
This commit makes minor copyediting fixes on the note
about what to do if the video doesn't load, due to
http versus https incompatibility.
|
|
Until now, when http://maneage.org was used, the video would not
load. However, when https://maneage.org was used (with a HTTPS), the
video would load. This is because PeerTube uses HTTPS. Boud has
provided a very complete description of the problem in [1].
With this commit, until we find a good/robust solution, a notice has
been added just under the video (in a slightly smaller font), hinting
at the solution for people who can't play the video.
[1] https://savannah.nongnu.org/task/?15654#comment12
|
|
This commit modifies the alternative text (for accessibility,
i.e. people with disabilities) in the `title' parameter for the
2020 20-minute Maneage video, to make it match the human readable
title.
|
|
Until now, a fixed height of 315 was assumed for the 'iframe'. So on a
full screen monitor the video would be too thin and on a smarphone it
would be too thick.
With this commit, I found a good CSS style that conforms to CSS2 for
older browsers also and used it to have varying aspect ratios based on
the size of the browser.
Also, now that people can directly watch the video on Maneage's own
webpage, it was necessary to edit the text above the video.
|
|
This commit replaces the GAFAM (YouTube) [1] location of the two
videos by PeerTube [2] locations, at peertube.stream [3]. There are
other minor corrections, such as correcting from "1 hour" to 80
minutes (and some whitespace changes, sorry).
[1] https://en.wikipedia.org/wiki/GAFAM
[2] https://en.wikipedia.org/wiki/PeerTube
[3] https://peertube.stream
|
|
Maneage was recently featured in Nature Astronomy, so it has been
added righta fter mentioning the RDA grant.
|
|
The "Adoption story" PDF that RDA prepared is a very good introduction
to Maneage, so it put a link to it in the top page.
|
|
I recently presented this ~1 hour talk at CiTIUS and they have
uploaded it on YouTube, so the link was added in the webpage for
interested people.
|
|
Until now, the webpage just linked to the arXiv version of the
paper. But it was finally accepted into CiSE last week and its DOI has
already been set, so the link was defined in the first page.
|
|
In the initial version of the paper, we had this nice figure to show
the file structure of Maneage, so I thought its good to put it in the
page describing Maneage's file architecture.
Also, the long copyright at the end of the page was summarized into
one line and a link to the GPL has been added.
|
|
Until now, the raw link as text wasn't too obvious for a new viewer of
the webpage. So a snapshot was taken from the start of the video
created by RDA of my talk and added in the page to be more prominent
and help new viewers notice it more clearly.
|
|
I recently found out that RDA had published that talk on YouTube, and
it can be good introduction for the viewers of the webpage too.
|
|
Until now, The project-flow SVG image was saved as optimized SVG
with comments saved in it by Inkscape. This made its size about
than 230 KB. The icon of paper in the image was also a simple paper.
With this commit, I modified the icon of the paper and added some
details: a small shape made of a square and circle inside the
text of the paper to look like a figure. Then I saved it as an
optimized SVG file without any comments. This allows us to have
a file with 208KB size.
For putting the image in the website I also decreased its size, so
it was necessary to center it. To do this, I added a general class
'.center' for this job and added it in 'base.css' at the end of
General style section to allow us have everything with this class
in the center.
|
|
This SVG figure was modeled on the slides that present Maneage and
created with Inkscape from scratch. Because converting the EPS/PDF
created by LaTeX would make the SVG around 1Mb, but making the svg
from scratch, it is now 44Kb :-).
|
|
The paper was published on arXiv today, so it was necessary to add it
to the webpage for an interested reader.
|
|
* Resized and relocated logos for a better look
* Moved the copyright comments in `html` files because Firefox was
complaining it could not find the `encoding character set` could not be
found in the first `1024 bytes` of the file
|
|
* Fix line-height problem
* Use lighter link colors
* Add the logo copyrights
|
|
* Used flex
* Should we add the gobierno-canarias?
|
|
* The `People` page will be added later
* This is almost the simplest design possible, we will alter the design
to match the desired and defined look later
|
|
New users don't know where to look for submitting bugs and tasks, so
its good to put a short description in the top page. Later, we should
open a whole page for this.
|
|
This is a tiny security fix. There's no need nor point in making
`index.html` have executable status.
This commit removes executable status for user/group/other from
the top `index.html' file.
|
|
* The `hamburger` label is not showing properly in different browsers.
Maybe that specific html unicode is not supported in all browsers. I
used a trick to fix this issue using the pipe character `|` ;-)
You could read about that here too:
https://stackoverflow.com/a/61645811/6474744
* The `down-arrow` unicode also did not work as expected through some
browsers. It was decided to remove this label totally. Maybe later
we can adopt using `standard` unicode html characters that are
`known` to be widely used across various browsers in different
platforms.
|
|
Thanks to Mohammad for recognizing even the smallest of contributions.
|
|
* Clarify selectors and elements with comments
* Delete duplicate styles
* Change ID names to something that makes more sense
|
|
To prevent unwanted word wrapping. Plus, less is more.
|
|
* Wrap in <footer> tag
* Add ARIA role
* Add ID's so they can be referenced to via anchors
* Fixed typo in head
|
|
Until now, the extra space made the padding look too big.
* Changed this HTML code convention:
```html
<pre><code>
some code
</code></pre>
```
* to this:
```html
<pre><code>some code</code></pre>
```
And the extra space is gone.
|
|
Now, every page has a banner with Maneage logo on it. Fixed the html and
css both.
|
|
Make them identical. Just four items.
|
|
This looks bad in non-dark themes. Maybe we should find another way of
making the logo stick out in dark themed browsers.
|
|
The tutorial still needs clearing up.
|
|
CSS will handle the spaces. This is to prevent the users from copying
the extra spaces to their clipboard.
|
|
|
|
Unitl now, there were almost no decorations introduced to <code> and <a>
tags.
With this commit, the webpage gets a colorful soul.
|
|
|
|
|
|
|
|
Boud had suggested having this on the main page for now, later when we
actually add some graphics and structure to the webpage it will be put
in the proper place.
|
|
Until now there wasn't any explanation of what we mean by "exact
reproducibility", so I added it and also put a click-able link to the
Git repository for easy navigation.
This is indeed just a crude place-holder, but since its live now, and
we have mentioned it in the draft paper, its good to have some
links. It also helps web search tools to already connect this page
with other related pages so by the time the final page is ready, it
can already have a presence in the search results.
|
|
I just setup this repository to host the project on our own servers,
so its better to use it instead of GitLab.
|
|
This is just a place holder that I made in a few minutes after setting
up the `maneage.org' domain. We will fill it up soon.
|
