taskManeage - Tasks: task #15586, A webpage for Maneage

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #15586: A webpage for Maneage

Submitted by:  Mohammad Akhlaghi <makhlaghi>
Submitted on:  Fri 03 Apr 2020 06:17:02 PM UTC  
 
Should Start On:  Thu 02 Apr 2020 11:00:00 PM UTC Should be Finished on:  Thu 02 Apr 2020 11:00:00 PM UTC
Category:  Software Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  100% Assigned to:  Pedram Ashofteh Ardakani <pedram>
Open/Closed:  Closed Effort:  0.00

( Jump to the original submission)

Thu 14 May 2020 07:51:16 PM UTC, comment #39: 

No problem :-) To future contributors: you can find the repo here.

Cheers!

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Fri 08 May 2020 03:42:26 PM UTC, comment #38: 

Great! Thanks a lot Pedram! Now that everyone (so far!) is already a member of your repo, let's use your repository as the development repository of the webpage.

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Fri 08 May 2020 07:15:22 AM UTC, comment #37: 

My pleasure :-)

Considering what Boud said on GitLab about removing executable permissions from the `index.html` file, I guess we should do the same to the other pages as well.

The funny thing is that my local repo was on the NTFS partition that we already know has problems with handling permissions, but now it is on my ext4 partition.

I also gave you the `maintainer` access to keep steps we need to take for making changes at a minimum. Feel free to add other participants :-)

Cheers

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Thu 07 May 2020 08:54:37 PM UTC, comment #36: 

Thanks for correcting it Pedram, your commit has been merged and uploaded ;-).

Thanks also for looking into the source of the problem, it would indeed be great if we follow best privacy practices.

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Thu 07 May 2020 08:29:30 PM UTC, comment #35: 

No problem! I made a new commit here, feel free to have a look :-).

Yes it is the privacy statement :-) I'll try to check how we can fix this ^_^

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Thu 07 May 2020 08:21:54 PM UTC, comment #34: 

Thanks for explaining the fix Pedram. I have so many thing to do these days that I couldn't go into the CSS and finding the exact cause of the this feature.

When I get the chance, I'll play with it a little and let you know if I make a change ;-).

I am curious, what was the reason it didn't get an "A" by duckduckgo? Is it the privacy statement?

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Thu 07 May 2020 06:24:14 PM UTC, comment #33: 

Thanks, Mohammad and Raul, I'm glad you liked it :-)

> [...] did you try `https://maneage.org'? [...]

Oh, that worked! When I type in `maneage.org` the HTTP is fetched by default for some reason. With HTTPS the website does have an encrypted connection and is rated `B+` by the DuckDuckGo extension.

> So maybe it can be good if we add a small notice at the bottom of the page that we record no information from you (a visitor). Generally, it will be good to add a footer to every page with a small copyright notice, year of publication, and such a statement on privacy.

Sure! Great idea :-)

> Regarding the extra padding [...].

Aha! I guess this is because of the `max-width: 950px` attribute in the `#container` selector :-) This is also the case for the emacs website you shared as an example. I can enlarge or even remove it if you want. Try resizing the window (or use `ctrl+shift+m` in Firefox to enter the responsive design mode) to check if this is actually the reason. I did widen up the page a bit for smaller screens though. If you still find the horizontal spacings too large, feel free to modify the `max-width` attribute in `#container` and `#nav-hamburger-wrap` to get the right looks on it :-)

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Thu 07 May 2020 08:47:01 AM UTC, comment #32: 

I like a lot the web page design. Thanks a lot Pedram, you did a great job!

Raul Infante-Sainz <infantesainz>
Project Member
Thu 07 May 2020 02:51:09 AM UTC, comment #31: 

Thanks Pedram, the two commits have been pushed and uploaded :-).

I like the idea of rotating the three `|'s! It is impressive.

The license notice looks good now, thanks! I wanted you to do this in your own commit ;-).

The two points by DuckDuckGo where interesting, did you try `https://maneage.org'? Probably this will fix the first one. The only problem is that sometimes it doesn't work in some countries.

The point about privacy practices was a good one and related to the analytics point that you mentioned later. Back in the old days, I had added analytics to my page (first Google Analytics, and then Piwik, which is now called Matomo, and was free software). I must say that I only learnt the value of privacy after seeing HOW MUCH information such analytic solutions record from every visitor! So on my new private page, I haven't added analytics and I feel so much much more comfortable: there is a lot of responsibility with all that information from every visitor.

I think its best if we do the same with Maneage's webpage and avoid all the ethical and legal issues with web analytics. So maybe it can be good if we add a small notice at the bottom of the page that we record no information from you (a visitor). Generally, it will be good to add a footer to every page with a small copyright notice, year of publication, and such a statement on privacy.

Regarding the extra padding, I have tried to show it with two thin red lines in the attached screenshot. Essentially the space between the text and the window's border, maybe decreasing it by 25% or 50% would be good so we have a little more space.


Mohammad Akhlaghi <makhlaghi>
Project Administrator
Wed 06 May 2020 10:09:14 PM UTC, comment #30: 

Also, using website analytics could be beneficial in the future. Here are a few good ones.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Wed 06 May 2020 10:06:23 PM UTC, comment #29: 

> Good work! They have been merged into the master branch and have been uploaded to maneage.org.

Yay! It looks great on my phone too `Samsung A7 2017` :-D

> The download sign behind the "Git" isn't showing properly (on the Android Firefox and Chrome). It may be best to remove it.

Yes, unfortunately, the `HTML Unicodes` did not work as expected across all browsers and platforms. Maybe there is a `standard set` of these Unicodes. We can use them if needed later. In fact, I even replaced the `hamburger` Unicode label with three pipe `|` characters and rotated them 90degrees! :-D to get it to work everywhere, and YES, that ... was ... fun! :-D

You can check the latest version here.

> [...] you hadn't put a copyright statement on the CSS file [...]

Thank you! It's taken care of :-). Actually it's my first time writing a license ^_^  Would you mind letting me know if I am following the right licensing conventions?

> Later, can you also add a "People" page where we can put a picture and name of each one of us that have contributed to Maneage.

Good idea!

> Generally, the basic task of setting up a core webpage has been done, but the webpage will be improved and many things will be added shortly when we complete the more urgent things.

Great! For a start, maybe we can add a privacy practice section. I opened up the website and let the DuckDuckGo privacy extension have a look at it, and the website was rated C+. There were two major complaints:
1. Unencrypted Connection
2. No Privacy Practices Found. Privacy practices indicate how much the personal information that you share with a website is protected. The Privacy practices of this website have not been reviewed.

> The space between the text and the sides browser window is a little too much, it can be decreased by around 25%-50% maybe ;-).

Where? Do you mean the nested unordered lists in the tutorial section? Or in general? Could you please send me a screen-shot? It may be some unexpected behavior that I am not aware of :-(.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Tue 05 May 2020 10:54:35 PM UTC, comment #28: 

After uploading the page and checking it on my phone, I noticed two points:

  • The download sign behind the "Git" isn't showing properly (on the Android Firefox and Chrome). It may be best to remove it.
  • The space between the text and the sides browser window is a little too much, it can be decreased by around 25%-50% maybe ;-).
Mohammad Akhlaghi <makhlaghi>
Project Administrator
Tue 05 May 2020 09:58:00 PM UTC, comment #27: 

Good work! They have been merged into the master branch and have been uploaded to maneage.org.

I just noticed one thing: you hadn't put a copyright statement on the CSS files, or added your name as a copyright holder on any of the HTML files (commented at the start of the HTML source, not those in the text, which we should later remove!).

Can you please do this also so I merge and upload it? In the HTML files, please put your copyright above mine (you have done much more work). You have done a lot of good work on this and it should be recognized ;-).

Later, can you also add a "People" page where we can put a picture and name of each one of us that have contributed to Maneage.

It may also be good to put the top "Git" link at the left-end of the line.

Generally, the basic task of setting up a core webpage has been done, but the webpage will be improved and many things will be added shortly when we complete the more urgent things. So I am closing this task, but ofcourse, we can continue basic followup discussions here, it doesn't matter if its closed ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Tue 05 May 2020 03:24:54 PM UTC, comment #26: 

At last! I'm happy to announce that it's almost ready! I hope it looks good now.

About the Perl script, yes I had to polish the results outside the Perl script file. I'll look for the patterns and write a fitting add-on. I guess it's because of the slight difference in the way GitLab interprets the Markdown language. Stuff such as:

```shell
```

and so on.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Sun 03 May 2020 01:24:22 PM UTC, comment #25: 

By the way, I like the fact that you have added the Perl script to convert markdown to HTML, this is great! But you said you had to do some polishing on its result afterwards. Or did you do those polishings in the actual code?

If its outside, it would be great to add them as a higher-level script. We can then automate it in the upload script so every time we upload the Git repo to the webpage it automatically based on the actual Maneage's Markdown files ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Sun 03 May 2020 01:12:19 PM UTC, comment #24: 

The code parts are perfect now! Good job ;-)

That convention on the CSS commenting, naming and spacing is also very impressive! I didn't know about it, but adopting such conventions is the sign of mastery and is what separates an amateur from a professional! Once you adopt them, don't forget to put a link to that page in the top of the CSS codes so people can see it and understand your nice work better.

I just feel the hyperlink color is still too strong compared to the text: they shouldn't jump out! Ideally, they should hardly be visible to someone who is just looking at the text generally, but only visible while you are reading, so something like 95% black, 5% pink ;-). For example see the links in Gnuastro's book. You hardly see them when seeing the page generally, only when you focus to read, you see the links. This helps in readability. Having the links pop-out in your face in the middle of the text makes the text, discourages reading.

Once you fix the CSS style conventions, I think we are ready to merge it in ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Sun 03 May 2020 10:23:43 AM UTC, comment #23: 

My pleasure :-) You can see my latest push here.

I will implement a standard commenting and spacing in CSS in future commits.

Thanks for the tips :-) Please let me know if you come up with any ideas.

Also, I guess we should add a navigation bar to the `tutorial` and `about` sections. Something like this or even this.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Sat 02 May 2020 06:59:36 PM UTC, comment #22: 

Thanks Pedram, it indeed looks so much better, here are some points:

  • It would help if a standard commenting/spacing is adapted in the CSS file, and a small comment on every part about what it is. We will later want to change things and you may be too busy, so with the comments, people can better understand it ;-).
  • The hyperlink colors are a little too sharp compared to the black font of the rest of the text, it would help if it is a darker shade of pink to help in readability, closer to black than pink, but enough to just show that it is a hyperlink.
  • There is too much padding around the code parts. Have a look at the coloring and padding of the code snippets in Gitlab's rendering of README.md. Also following that style, it helps is the background is even more lighter (closer to white).
Mohammad Akhlaghi <makhlaghi>
Project Administrator
Sat 02 May 2020 08:56:19 AM UTC, comment #21: 

I found this Markdown to HTML converter and downloaded the code to use it offline. It works pretty well. But I had to use regex to gain the perfection we need :-)

As always, thanks for the tips, I've implemented them here. I'm eager to hear your feedback. This is getting better and better :-)

About the favicon, just forget it. I used it since my browser is using a dark theme and because of that the icon is not visible to me. But that's not a big deal for now, we'll find a solution in  future.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Wed 29 Apr 2020 11:59:04 PM UTC, comment #20: 

Thanks Pedram,

A regex for converting Markdown to HTML is **very interesting**! Keep it a separate Git repository, I am sure many people would be interested ;-).

Here are some points:

  • When I fetched your commits, I noticed three branches! But when I ran `git log --oneline --graph --decorate --all', I noticed that they are all after each other in one branch! In such cases, delete the old branch ;-). A branch is only for when there is nothing after it (creating parallel scenarios), but the three branches here are all in series.
  • I wondering what the `img/favicon.svg' is!?! Why not just use the original `img/maneage-logo.svg'? Attached I am sending the view of the icons beside each other in two tabs: the white one is your branch and the one with no background color is the original SVG. I feel that the artificial circle and white background make it unnatural.
  • `index.html' has five items on the top, but the rest have four.
  • Generally, I think there is no need to put the slides on the top bar ;-). We'll later put an image of the first slide and link to it in the main page ;-).
  • In the "About" page, the top "Tutorials" link points to the slides.
  • I feel the code font sizes is a little too large compared to the main text, it would be better if its smaller.
  • Probably it would be better to make the background of the code blobs even lighter (very light purple). While the borders can be just slightly (very slightly!) darker, but still closer to white than black: we don't want the codes to overshadow the text ;-).


Mohammad Akhlaghi <makhlaghi>
Project Administrator
Wed 29 Apr 2020 01:14:04 PM UTC, comment #19: 

OK :-) As always, thanks for the tips!

This is fun. Especially when I tried to convert the Markdown to HTML. I've been experimenting with the `regex` for substituting strings for hours now. It needs a bit more work to look appealing.

But here's what I achieved today.

I do appreciate your comments. They point me in the right direction :-D. Cheers!

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Tue 28 Apr 2020 11:16:52 PM UTC, comment #18: 

Great! Thanks Pedram.

I fetched your new branch and had a look, the progress does look good ;-).

About the `git.maneage.org' page, that is not part of this webpage, so you should specify it with the full URL. Essentially any link to that you make to a file that is version controlled should be relative, but links that aren't under version control should be absolute ;-).

Some small thoughts about the page:

  • It would be good if the background of the code parts are different from the menu links on the bottom and top of the page ;-). Probably it would be good if both are lighter ;-). For example look at the example codes in Gitlab's rendering of README-hacking.md.
  • For the codes, it may be good to also set rounded corners for a more pleasent look ;-).
  • In the "About" part, you can use the contents of `README-hacking.md', especially in the first few sections and make a page for it ;-).
  • In the tutorial page, you already know about the tutorials that Raul has started in task #15591. Maybe you can put them in the HTML format for a tutorial page.
  • You can remove the black link in the middle of the page on "Git Repository", the one at the top is fine ;-).

I think that once a first rendering of the "About" and "Tutorials" pages is done, we'll be able to merge it into master and go into production ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Tue 28 Apr 2020 10:02:57 AM UTC, comment #17: 

I cloned the Maneage webpage repository, now I'm pushing the commits in ped-index branch on my GitLab account.

Thanks for your quick look and the comments. I appreciate all of them.

About referring to an internal page, does `git.maneage.org/etc` refer to `./git/etc` relatively?

Could you check my commits again? It's a bit more colored :-)

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Mon 27 Apr 2020 11:27:18 AM UTC, comment #16: 

Thanks Pedram, I just had a fast look, here are some comments:

  • Can you please move this content to a branch off the Maneage webpage repository? You will loose the current history, so the sooner you do it, the better, its also easier for me to check ;-).
  • After merging a branch into your main branch delete its reference on your local system and on the remote. Generally, a branch is only useful/meaningful when it is not yet merged ;-), otherwise it just pollutes the history and makes it hard to find the important uncompleted work.
  • The page generally looks good. Maybe its best to replace the "Download" button with the Git repository, because Maneage will not be downloaded. "About Maneage" can also be changed to "About" and it should be placed right beside home ;-).
  • By the way, when referring to an internal page, never use its full URL, use its relative URL. So for example "Home" should point to `index.html', not `https://maneage.org'.
  • Also, for future maintenance, generally when dealing with documents that will be processed (HTML or LaTeX for example), its easier to follow the convention of one-sentence-per-line. Otherwise, every time you add/remove a word and re-justify the sentence the whole paragraph will show as changed in Git (which is annoying!).

More comments as you make more progress ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Mon 27 Apr 2020 10:27:31 AM UTC, comment #15: 

Cool! I cloned the webpage. I'll apply the changes to this version you have and upload it in my GitLab repository.

But until then, you can have a look at my current progress. Suggestions are welcome of course :-D.

I'll try to be quick :-). Thanks!

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Fri 24 Apr 2020 09:20:46 AM UTC, comment #14: 

Nicely done. Sure thing!

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Fri 24 Apr 2020 04:43:15 AM UTC, comment #13: 

In the paper, we have mentioned maneage.org, but it didn't point anywhere and that was annoying! So I just built an empty starting page for Maneage to load with some minimal explanation. You can see it here: http://maneage.org or https://maneage.org (the latter has a dedicated SSL certificate).

The repository hosting the webpage is now here: https://gitlab.com/maneage/webpage (under the Maneage group on GitLab). Pedram, later when you are ready for us to look into your designed webpage, it would be good if you move it into a fork of this repository ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Thu 16 Apr 2020 06:23:49 AM UTC, comment #12: 

Great! Your comments sure are helpful and encouraging ;-) I'm on it :-D. Thanks for the tips!

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Thu 16 Apr 2020 02:04:48 AM UTC, comment #11: 

Thanks a lot Pedram, I just had the chance to clone the git project. You are making good progress ;-). Just some minor points:

  • I noticed you are still using the old logo, Raul uploaded a newer Logo, it may be good to switch to that ;-).
  • Generally, its good to have different types of files in different directories, like how you have the `css' directory for the styles. You can do the same with images (and have an `image' or `img' directory).

As you progress with the book, try to implement everything it mentions, even if you don't think it may be useful, and you may want to delete it. However, it will help you play with the structures and get more comfortable with them them, later you'll be surprised how useful it was ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Sun 12 Apr 2020 01:59:02 PM UTC, comment #10: 

This is interesting, thanks Pedram, we will look into it. Ultimately we need a solution that we can host (and move around) ourselves.

For the documentation (or "Wiki") part of the webpage personally prefer lower-level solutions, for example having a Texinfo source (basically TeX, but with an `@' instead of `\') that can produce a beautiful PDF (created in LaTeX), a nice HTML webpage, an `info' manual for the command-line, or just simple plain-text. Similar to all the formats of Gnuastro's main book which you can see on its webpage. The HTML produced by Texinfo is very complete with many tags, giving us full freedom to give it an elegant style with CSS. In the case of Gnuastro, I didn't have much time, so I just opted for a simple CSS which you can see in its doc/style.css.

Anyone who wants to improve the documentation/Wiki, can simply edit its source and push a commit and the webpage maintainer will inspect it and merge it in, having a clean and elegant history, while also not needing any online log-in, and all the complications it brings with it.

But for the time being, let's just stick to static pages and get the webpage started ;-).

I have already started the process of getting an online storage to host the content and hopefully it will be done by the end of this week :-). Do you think you can have a working first webpage structure by then? In a few days I can have a look and help in filling it up with some contents and testing it. It would be great if maneage.org can actually show something from the end of this week ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Sun 12 Apr 2020 06:39:14 AM UTC, comment #9: 

Great! There sure is much to learn from you guys :-).

About adding a WiKi, I looked through some already available websites that provide free service on Wikipedia.

I found Ourproject.org which is based in Madrid as their Wikipedia page puts it. Maybe putting the wiki on third-party websites could save some time and energy.

Although, I'm also eager to help the best way I can.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Sat 11 Apr 2020 06:35:50 PM UTC, comment #8: 

I was just talking to Surena today (his email is added to this task) and he also expressed interest in helping out with the webpage. He is also familiar back-end features in the future (for example adding a Wiki, or a user data base and etc).

For now, a simple static page for maneage.org is enough to start with. As time goes on, we may need things like a wiki. Although I am not too sure if we do actually need it: committing changes to simple static pages in Git, is much more simple then having to use third-party systems (commonly with their own Javascript tools) and maintain a user database (to give permissions to edit the wiki), while being compliant with things like GDPR and etc. Currently I feel that maintaining all these things (user information in particular, then Javascript) will be a nightmare and will take a lot of energy that we could spend on the actual project.

But I am not closed to the idea: if a responsible solution (a good Javascript, with ethical usage of private user information) exists, and it also doesn't take too much energy to maintain, we can consider it. Let's see....

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Sat 11 Apr 2020 11:11:31 AM UTC, comment #7: 

Now I've read more than 50% of the book - 300+ pages. This is the point where things get more visual and decorative. Can't wait to make it look nice!

Oh come on, I did enjoy the simplicity of your page!

Great! I'm looking forward to working with her :-). Cheers!

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Tue 07 Apr 2020 02:35:01 PM UTC, comment #6: 

Thanks Pedram, I am happy to hear you are enjoying it: this is the whole purpose ;-).

Personally, I am terrible with graphic design! You can tell from my own webpage. Please feel totally free in the graphical design concepts/structures and implementation.

In fact, recently another person has also expressed interest in helping with the webpage design, probably you guys can collaborate as you first each start independently. She will hopefully post a comment here shortly to collaborate.

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Tue 07 Apr 2020 09:37:28 AM UTC, comment #5: 

Thanks again Mohammad. I do appreciate your patience, support, and kindness.

I have created a Gitlab repository for a demonstration as you suggested, building a simple HTML5 page from scratch on the dev branch. Also, I've read and implemented about 20% of the book you introduced - 7th edition actually - into an index.html file. It's been almost 6 years since the last time I built a website from scratch! Now I'm eager to learn the new HTML5 & CSS3, and the way they can be used to create modern, minimal, responsive websites. That's why I'm reading the book carefully.

I'd like to know if you have some kind of structure planned for the website?

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Sun 05 Apr 2020 08:46:27 AM UTC, comment #4: 

comment #3

Thanks for the informative links and nice webpages! I got the book you introduced :-). Starting from scratch ;-).

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Fri 03 Apr 2020 10:55:09 PM UTC, comment #3: 

If you are interested, you can start writing the HTML source of a demonstration page (in a separate Git repository), and we can slowly grow it. You can use good pages (like Emacs' page linked before) as a starting reference to play with. But I would recommend to start from scratch ;-)!

Make an empty file and start writing HTML components in it and associating CSS styles to them so they load in the proper place and with the proper display. There are many good books, I personally used the HTML and CSS, Eighth Edition: Visual Quickstart Guide by Elizabeth Castro and Bruce Hyslop, and it helped me a lot in writing/designing my own webpage. You can actually view the HTML source of my page and you will see it is hand-written ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Fri 03 Apr 2020 07:28:26 PM UTC, comment #2: 

comment #1

> [...] a raw, hand-written HTML+CSS page [...]


Keeping things simple and minimal sounds like a nice idea. Sure, if the git history is kept human readable then all the content could be migrated to other templates! So, as far as I know, there's no risk in starting off simple.

Pedram Ashofteh Ardakani <pedram>
Project MemberIn charge of this item.
Fri 03 Apr 2020 06:42:31 PM UTC, comment #1: 

We can also use this task to share pages that visually look modern/good while also having a simple HTML structure. We can use them for inspiration.

The first example is the page for GNU Emacs: https://www.gnu.org/software/emacs .

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Fri 03 Apr 2020 06:17:02 PM UTC, original submission:  

Now that the project is properly names as "Maneage" (management+lineage), its time to setup a webpage for it. Having a webpage was also a promised deliverable for the RDA grant. So I have already registered `maneage.org' for it, although it doesn't point anywhere yet.

I have also talked with IAC and they have agreed to give us space to host the webpage (to link with the `maneage.org' domain).

So we just have to work on the contents. I know its not too "convenient", but I am thinking of a raw, hand-written HTML+CSS page, like my own webpage: akhlaghi.org.

The idea is to avoid all the high-level graphic webpage designers that just make the page sources extremely hard to read, slow to load, and hard to keep a history of. If we have everything in hand-written HTML, the full page can be managed in git and easily loaded on any space and edited and viewed, for example on my own page, you can see the history on Gitlab.

But this is just a suggestion, if someone can suggest a good high-level webpage designing system that is robust and doesn't have too much overhead and dependencies (both in archive-ability, and in publication and loading), we can consider it ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator

 

Attached Files
file #49017:  screenshot.png added by makhlaghi (29KiB - image/png)
file #48969:  webpage-icon.png added by makhlaghi (13KiB - image/png)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by infantesainz (Posted a comment)
  • -email is unavailable- added by makhlaghi
  • -email is unavailable- added by pedram (Posted a comment)
  • -email is unavailable- added by makhlaghi (Submitted the item)
  • -email is unavailable- added by makhlaghi
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 17 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-05-07 makhlaghi Attached File- => Added screenshot.png, #49017
    2020-05-06 pedram StatusIn Progress => Done
        Percent Complete30% => 100%
        Open/ClosedOpen => Closed
    2020-05-06 pedram StatusDone => In Progress
        Percent Complete100% => 30%
        Open/ClosedClosed => Open
    2020-05-05 makhlaghi StatusIn Progress => Done
        Percent Complete30% => 100%
        Open/ClosedOpen => Closed
    2020-05-05 pedram Percent Complete20% => 30%
    2020-04-29 makhlaghi Attached File- => Added webpage-icon.png, #48969
    2020-04-29 pedram Percent Complete10% => 20%
    2020-04-28 makhlaghi Assigned toNone => pedram
    2020-04-11 makhlaghi Carbon-Copy- => Added surenaftm@gmail.com
    2020-04-07 pedram Percent Complete0% => 10%
    2020-04-03 makhlaghi Carbon-Copy- => Added pedramardakani@gmail.com

    Back to the top


    Powered by Savane 3.6