| Age | Commit message (Collapse) | Author | Lines |
|---|
|
* Used flex
* Should we add the gobierno-canarias?
|
|
* Got the `IAC` logo in svg
* Compressed all svg files to save bandwidth using the tool on:
https://vecta.io/nano
|
|
* 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
|
|
Problem with local repo. Using `git reset <commit hash>` changes the
HEAD location. And it looks like I have pushed this before. So, there
were some complications. Now, fix it.
|
|
Reduce the margin and padding on top of the paragraphs and below the
headers. Mohammad suggested this on savannah:
* https://savannah.nongnu.org/bugs/?58377#comment0
Also, add a few sentences in the README.md file.
|
|
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.
|
|
Let everyone know where the actual repo is held, and that this repo is
the development stage. Contributors can contact us here, and do
merge-requests or in some cases, push commits in certain branches.
|
|
There weren't any conflicts in this merge.
|
|
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.
|
|
* Add more comments in CSS
* Fill the entire top with nav bar in smaller screens
* Rotate the `burger` menu 180degrees and change color on click
* Replace the `burger` unicode with pipe `|` in other pages too
* Add the licensing info in other pages too
* Increase the page width for more space
|
|
* 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.
|
|
Keep the Maneage logo and header texts next to each other by
vertical-aligning them both at the middle.
|
|
* Clarify selectors and elements with comments
* Delete duplicate styles
* Change ID names to something that makes more sense
|
|
And make the hamburger label white.
NOTE: It may look nicer if the label rotates when the user clicks on it.
|
|
To prevent unwanted word wrapping. Plus, less is more.
|
|
* Fix responsive header width
* Round corners in footer and nav head
* Stick navigation bar to the top
* Add comments to make it dev-friendly, More to come in future commits
* Darken the link colors to ease the reader's experience and keep the
links from jumping out the text
|
|
* Wrap in <footer> tag
* Add ARIA role
* Add ID's so they can be referenced to via anchors
* Fixed typo in head
|
|
* use <span class="comment"># some comment</span>
* remove extra <span> tags
|
|
|
|
Colors:
* links (darker pink)
* visited links (darker - but distinguishable from black)
* link text-shadows (lighter, subtle selecting effect)
* code blob background (pure white)
Padding:
* same as GitLab
* line-height wasn't working because it was inherited from body. Fixed
this by changing the line-height in the parent - which is the <pre> tag
|
|
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.
|
|
|
|
Until now, the links were selected by their parent. That was to
separately change the `Button` links and links in <p>, <li>, etc.
With this commit, only the `Button` links are sepatated with a class.
All other links are decorated the same.
|
|
* Lighter background
* Lighter border
|
|
* Reduce <code> font size
* Increase <body> line-height
|
|
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.
|
|
https://gitlab.com/infantesainz/reproduce-raulfork/-/blob/tutorial/README-tutorial.md
|
|
|
|
Maybe we should create a side navigation toolbar.
|
|
Used the https://daringfireball.net/projects/markdown/ project.
|
|
Used a Perl script to convert Markdown to HTML. This is where it sits.
|
|
|
|
Change background and text colors, round the corners, better control on
text overflow in smaller devices, etc.
I'll try to be more `atomic` in next commits. However, that seems
unnecessary since all these commits have short lives, except the last
`squashed` one.
|
|
CSS will handle the spaces. This is to prevent the users from copying
the extra spaces to their clipboard.
|
|
Created a seperate color section at the beginning of the CSS file, so
one can change colors without moving around the CSS file so much!
Created a `FONTS` section at the top of the CSS file.
Also, moved the `decoration classes` section next to the `colors`
section in the CSS file.
I'll try to tidy up the CSS file further.
|
|
|
|
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.
|
