team-leader: W3C validator code review

git-svn-id: svn+ssh://atelier.inf.usi.ch/home/bevilj/group-1@255 a672b425-5310-4d7a-af5c-997e18724b81
This commit is contained in:
Claudio Maggioni 2018-11-18 20:44:36 +00:00
parent a6515acdb9
commit 2404763b4b
12 changed files with 63 additions and 32 deletions

View File

@ -5,7 +5,7 @@
<div class="fill-space"></div> <div class="fill-space"></div>
<div class="search-box"> <div class="search-box">
<input type="text" id="search-bar" onfocus="document.searching=true" onblur="document.searching=false"> <input type="text" id="search-bar" onfocus="document.searching=true" onblur="document.searching=false">
<label for="search-bar"><img src="/assets/style/search_icon.png"></label> <label for="search-bar"><img alt="search" src="/assets/style/search_icon.png"></label>
<ul id="search-results"></ul> <ul id="search-results"></ul>
</div> </div>
<nav class="nav-menu"> <nav class="nav-menu">

View File

@ -1,5 +1,5 @@
<!DOCTYPE html> <!DOCTYPE html>
<html> <html lang="en">
{% include head.html %} {% include head.html %}
<body onload="typing_shell()" style="background-color:#000;"> <body onload="typing_shell()" style="background-color:#000;">
<header class="spec-header"> <header class="spec-header">
@ -9,7 +9,7 @@
</div> </div>
<div class="fill-space"></div> <div class="fill-space"></div>
<div class="search-box"> <div class="search-box">
<input type="text" id="search-bar"><label for="search-bar"><img src="/assets/style/search_icon.png"></label> <input type="text" id="search-bar"><label for="search-bar"><img alt="search" src="/assets/style/search_icon.png"></label>
<ul id="search-results"></ul> <ul id="search-results"></ul>
</div> </div>
<nav class="nav-menu"> <nav class="nav-menu">

View File

@ -1,5 +1,5 @@
<!DOCTYPE html> <!DOCTYPE html>
<html> <html lang="en">
{% include head.html %} {% include head.html %}
<body id="bdy"> <body id="bdy">
<header class="header"> <header class="header">

View File

@ -8,23 +8,28 @@ title: pass
previous-page: pages/cmd/interm/neofetch.html previous-page: pages/cmd/interm/neofetch.html
next-page: pages/cmd/interm/passwd.html next-page: pages/cmd/interm/passwd.html
--- ---
<p>
The <code>pass</code> command, also known as <i>Password Store</i>, is an The <code>pass</code> command, also known as <i>Password Store</i>, is an
entirely offline password manager that uses <i>GPG</i> for encryption with entirely offline password manager that uses <i>GPG</i> for encryption with
the ability to sync the (entirely encrypted) passwords using <code>git</code>. the ability to sync the (entirely encrypted) passwords using <code>git</code>.
<code>pass</code> works on <i>MacOS</i> (avaliable via <code>pass</code> works on <i>MacOS</i> (avaliable via
<a href="https://brew.sh">Homebrew</a>), <i>Linux</i> and on <a href="https://brew.sh">Homebrew</a>), <i>Linux</i> and on
<i>Android</i> (with a GUI app). Think of it as an entirely FLOSS <i>Android</i> (with a GUI app). Think of it as an entirely FLOSS
alternative to services like <i>Keypass</i> or <i>Dashlane</i>.<br> alternative to services like <i>Keypass</i> or <i>Dashlane</i>.
</p>
<p>
Excluding the initial setup (that requires the creation of a <i>GPG key</i>), Excluding the initial setup (that requires the creation of a <i>GPG key</i>),
<code>pass</code> is very easy and straightforward to use: instead of <code>pass</code> is very easy and straightforward to use: instead of
printing passwords to <i>stdout</i>, <code>pass</code> copies them in the printing passwords to <i>stdout</i>, <code>pass</code> copies them in the
system clipboard, erasing them after a certain number of seconds (usually system clipboard, erasing them after a certain number of seconds (usually
<i>45</i>).<br> <i>45</i>).
</p>
<p>
<code>pass</code> has many unofficial GUI clients and migration scripts from <code>pass</code> has many unofficial GUI clients and migration scripts from
other password managers. For more information, check out other password managers. For more information, check out
<a href=https://www.passwordstore.org/#other">the official website</a>. <a href=https://www.passwordstore.org/">the official website</a>.
</p> </p>
<h3>Setup</h3> <h3>Setup</h3>
@ -35,8 +40,10 @@ to some other useful sets of commands (such as how to migrate the password
repository to another computer) is provided repository to another computer) is provided
in this <a href="https://gist.github.com/flbuddymooreiv/a4f24da7e0c3552942ff"> in this <a href="https://gist.github.com/flbuddymooreiv/a4f24da7e0c3552942ff">
GitHub Gist</a> by <a href="https://github.com/flbuddymooreiv"> GitHub Gist</a> by <a href="https://github.com/flbuddymooreiv">
<i>flbuddymooreiv</i></a>.<br> <i>flbuddymooreiv</i></a>.
</p>
<p>
For more detailed explainations on the setup process or on any commands For more detailed explainations on the setup process or on any commands
please check out the online version of the please check out the online version of the
<a href="https://git.zx2c4.com/password-store/about/">man page</a>, which is <a href="https://git.zx2c4.com/password-store/about/">man page</a>, which is
@ -47,54 +54,71 @@ surprisingly more readable that most of the man pages for other utilities.
<p> <p>
Common <code>pass</code> commands are shown below. For more information refer Common <code>pass</code> commands are shown below. For more information refer
to the documentation linked above.<br> to the documentation linked above.
</p>
<p><b>
Example: Initialize the password repository with a GPG key with id "0DEADBEEF" Example: Initialize the password repository with a GPG key with id "0DEADBEEF"
</b></p>
<pre> <pre>
pass init 0DEADBEEF pass init 0DEADBEEF
</pre> </pre>
<p><b>
Example: Insert a password for <i>example.com</i> with username <i>bob</i> in Example: Insert a password for <i>example.com</i> with username <i>bob</i> in
the password repository interactively the password repository interactively
</b></p>
<pre> <pre>
pass insert example.com/bob pass insert example.com/bob
</pre> </pre>
<p>
Please note that the password <i>name</i> here follows the most common Please note that the password <i>name</i> here follows the most common
naming convention in <code>pass</code>, which is naming convention in <code>pass</code>, which is
<code>{website}/{username}</code>. Passwords can be stored in <code>{website}/{username}</code>. Passwords can be stored in
hierarchical structures (i.e. in nested folders), but the naming is up to the hierarchical structures (i.e. in nested folders), but the naming is up to the
user.<br> user.
</p>
<p><b>
Example: Generate a password for <i>zombo.com</i> of 16 characters and copy it in Example: Generate a password for <i>zombo.com</i> of 16 characters and copy it in
the clipboard the clipboard
</b></p>
<pre> <pre>
pass generate -c zombo.com/bob 16 pass generate -c zombo.com/bob 16
</pre> </pre>
<p><b>
Example: Retrieve the password for <i>google.com</i> and copy it in the system Example: Retrieve the password for <i>google.com</i> and copy it in the system
clipboard (<code>-c</code> flag) clipboard (<code>-c</code> flag)
</b></p>
<pre> <pre>
pass -c google.com/bob@gmail.com pass -c google.com/bob@gmail.com
</pre> </pre>
<p><b>
Example: Edit the password for <i>facebook.com</i> using the default editor Example: Edit the password for <i>facebook.com</i> using the default editor
</b></p>
<pre> <pre>
pass edit facebook.com/bob pass edit facebook.com/bob
</pre> </pre>
<p><b>
Edit: Convert the password repository to a git repository for synchronization Edit: Convert the password repository to a git repository for synchronization
</b></p>
<pre> <pre>
pass git init pass git init
</pre> </pre>
<p>
Every <code>git</code> command on the password repository must be given with Every <code>git</code> command on the password repository must be given with
the prefix <code>pass git</code> (e.g. <code>pass git push</code>). An the prefix <code>pass git</code> (e.g. <code>pass git push</code>). An
automatic commit is performed whenever a password is created, edited or automatic commit is performed whenever a password is created, edited or
deleted. deleted.
</p>

View File

@ -12,20 +12,25 @@ next-page: pages/fs/du.html
<!-- Co-authored with Mirko Ponzio --> <!-- Co-authored with Mirko Ponzio -->
<p> <p>
The <code>cd</code> command is used to change the working directory<br> The <code>cd</code> command is used to change the working directory<br/>
The name stands for <i>Change Directory</i>.<br> The name stands for <i>Change Directory</i>.<br/>
The default cd command syntax is: The default cd command syntax is:
</p>
<pre> <pre>
cd [flags] [path] cd [flags] [path]
</pre> </pre>
<p>
Where [flags] are the cd flags, read below for more info,and [path] is the Where [flags] are the cd flags, read below for more info,and [path] is the
path (absolute or relative), of the directory which we want to make as working directory.<br><br> path (absolute or relative), of the directory which we want to make as working directory.
</p>
<h3>Change the working directory</h3> <h3>Change the working directory</h3>
Let's see how to use the command <code>cd</code> in order to change the working directory <p>
Let's see how to use the command <code>cd</code> in order to change the working directory:
</p>
<pre> <pre>
pwd pwd
@ -35,10 +40,12 @@ pwd
~/Desktop/multimedia ~/Desktop/multimedia
</pre> </pre>
<p>
As you can see, we changed the working directory from ~ (which stands for HOME), As you can see, we changed the working directory from ~ (which stands for HOME),
to "multimedia". Now our Shell will work on the directory "multimedia" to "multimedia". Now our Shell will work on the directory "multimedia"
until a new <code>cd</code> will occour.<br> until a new <code>cd</code> will occour.</p>
<b> Notice:</b> If you want to move to a directory which is not contained in the <p>
<b>Notice:</b> If you want to move to a directory which is not contained in the
current working directory, you <u>MUST</u> use the absolute path. current working directory, you <u>MUST</u> use the absolute path.
</p> </p>

View File

@ -7,31 +7,25 @@ author: Matteo Omenetti
title: About the project title: About the project
--- ---
<img id="time-line" src="../../assets/info/Timeline.jpg" alt="Timeline of the project" width="500px"</img><br> <img id="time-line" src="../../assets/info/Timeline.jpg" alt="Timeline of the project" width="500"/><br/>
This is the final project of the course “Software Atelier 1” hosted by the University of Lugano.<br>
<p>
This is the final project of the course “Software Atelier 1” hosted by the University of Lugano.<br/>
For this project, the informatics students of the first year got divided into two groups, For this project, the informatics students of the first year got divided into two groups,
each made up of 25 students.<br> each made up of 25 students.<br/>
The goal of this project was to put into practice all the skills obtained during the entire The goal of this project was to put into practice all the skills obtained during the entire
duration of this course: Latex, HTML, CSS, Unix Shell and SVN.<br> duration of this course: Latex, HTML, CSS, Unix Shell and SVN.<br/>
The students had about 4 weeks to develop, from the ground up, this 100 pages website.<br/>
The students had about 4 weeks to develop, from the ground up, this 100 pages website.<br>
A great coordination was needed to develop A great coordination was needed to develop
such a big website in such a short time. For this reason some students had to take care of such a big website in such a short time. For this reason some students had to take care of
specific tasks, such as managing the SVN repository and developing the CSS templates.<br> specific tasks, such as managing the SVN repository and developing the CSS templates.<br/>
Our topic (Unix Shell) got divided into three macro sections, each taking care of a Our topic (Unix Shell) got divided into three macro sections, each taking care of a
number of commands based on their advancement level, therefore there is a basic, number of commands based on their advancement level, therefore there is a basic,
intermediate and advance section commands.<br> intermediate and advance section commands.<br/>
Each macro section had its own leader, that was responsible for overseeing the conduct Each macro section had its own leader, that was responsible for overseeing the conduct
of the other team members within his group. of the other team members within his group.
Then each team leader reported back to group leader, that was responsible for the success Then each team leader reported back to group leader, that was responsible for the success
of the entire project.<br> of the entire project.<br/>
The ultimate goal of this website is to provide, to the future first-year students, The ultimate goal of this website is to provide, to the future first-year students,
a useful and human readable guide that can guide a useful and human readable guide that can guide
them through the learning process of this fundamental tool. This website in intended them through the learning process of this fundamental tool. This website in intended

View File

@ -2,4 +2,5 @@
layout: topic layout: topic
category-page: about category-page: about
title: About title: About
author: Frontpage team
--- ---

View File

@ -2,6 +2,7 @@
layout: topic layout: topic
category-page: advanced category-page: advanced
title: Advanced Commands title: Advanced Commands
author: Advanced commands team
--- ---
<!-- Description by Domenico Votta --> <!-- Description by Domenico Votta -->

View File

@ -2,6 +2,7 @@
layout: topic layout: topic
category-page: basic category-page: basic
title: Basic Commands title: Basic Commands
author: Basic commands team
--- ---
<!-- Description by Gianmarco De Vita --> <!-- Description by Gianmarco De Vita -->
<p class="description-section">If you are new to the shell or a beginner who just want to refresh his knowledge this is the section for you. Move your first steps in this interface by learning and trying this selection of basic commands which allow you to do routine operations in a different way.</p> <p class="description-section">If you are new to the shell or a beginner who just want to refresh his knowledge this is the section for you. Move your first steps in this interface by learning and trying this selection of basic commands which allow you to do routine operations in a different way.</p>

View File

@ -2,6 +2,7 @@
layout: topic layout: topic
category-page: intermediate category-page: intermediate
title: Intermediate Commands title: Intermediate Commands
author: Intermediate commands team
--- ---
<!-- Description by Joao Tomazoni --> <!-- Description by Joao Tomazoni -->

View File

@ -2,6 +2,7 @@
layout: topic layout: topic
category-page: fs category-page: fs
title: Filesystem title: Filesystem
author: Filesystem team
--- ---
<!-- Description by Ricardo Vivanco --> <!-- Description by Ricardo Vivanco -->
<p class="description-section">The File System (FS) shell includes various shell-like commands that directly interact with the Hadoop Distributed File System (HDFS) as well as other file systems that Hadoop supports, such as Local FS, HFTP FS, S3 FS, and others. The FS shell is invoked by: <p class="description-section">The File System (FS) shell includes various shell-like commands that directly interact with the Hadoop Distributed File System (HDFS) as well as other file systems that Hadoop supports, such as Local FS, HFTP FS, S3 FS, and others. The FS shell is invoked by:

View File

@ -2,6 +2,7 @@
layout: topic layout: topic
category-page: scripts category-page: scripts
title: Scripting title: Scripting
author: Scripting team
--- ---
<p>Here we will learn the basic of shell scripting...</p> <p>Here we will learn the basic of shell scripting!</p>