Skip to content
Snippets Groups Projects
Commit cf1627b7 authored by Romain PASTORELLI's avatar Romain PASTORELLI
Browse files

premier ajout des fichiers html et css

parent 45c20b63
No related branches found
No related tags found
No related merge requests found
CV.css 0 → 100644
body{
background-color:#181A1B;
color:white;
margin:0px;
display:flex;
line-height: 30px;
font-family: sans serif;
}
aside{
background-color:#8E1401;
height:100%;
}
p, h3, h1, span{
padding-left:20px;
padding-right:20px;
}
aside h3{
background-color:#721001;
}
body section h1{
color:#FE7653;
}
a{
color:white;
}
.chap{
padding-top:5px;
padding-bottom:5px;
text-align:center;
font-size:25px;
}
#etu{
margin-top:0px;
padding-bottom:0px;
font-size:20px;
}
#nom{
margin-bottom:0px;
font-size:30px;
}
aside section{
line-height: 24px;
}
li{
height:63px;
}
.long{
height:90px;
}
.slider-b{
height:15px;
margin-top:0;
background-color: #181A1B;
position:relative;
left:-15px;
margin-top:5px;
margin-bottom:20px;
border-radius:10px 0 0 10px;
}
.slider-r{
height:15px;
margin-top:0;
background-color: #721001;
position:relative;
top:-35px;
margin-top:5px;
margin-bottom:20px;
border-radius:0 10px 10px 0;
}
#full{
width:180px;
border-radius:10px;
}
#qv-b{
width:140px;
}
#qv-r{
width:0;
right:-165px;
}
#sx-b{
width:110px;
}
#sx-r{
width:30px;
right:-135px;
}
#cq-b{
width:90px;
}
#cq-r{
width:80px;
right:-85px;
}
div h1{
width:1005px;
border-top:1px grey solid;
border-bottom:1px grey solid;
font-size:30px;
padding-top:10px;
padding-bottom:10px;
padding-left:0;
margin-left:20px;
}
#xp section, #formation section{
display:flex;
}
#xp p, #formation p{
margin-top:0;
padding-left:0;
}
.dates{
margin-right:0px;
text-align:center;
line-height:20px;
padding-top:6px;
}
#xp strong, #formation strong{
font-size:20px;
}
#formation .dates{
margin-bottom:20px;
}
CV.html 0 → 100644
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<link rel="stylesheet" href="CV.css">
<title>Romain PASTORELLI</title>
</head>
<body>
<aside>
<!-- <p><img src="chemin_relatif" alt="petite descrip° de l'image"></p> -->
<h1 id="nom">Romain PASTORELLI</h1>
<p id="etu">Étudiant</p>
<section>
<h3 class="chap">Coordonnées</h3>
<p><strong>Téléphone</strong><br>
07 82 62 76 61
<br>
<br>
<strong>E-mail</strong><br>
<a href="mailto:pastorelliromain@gmail.com">pastorelliromain@gmail.com</a></p>
</section>
<section>
<h3 class="chap">Compétences</h3>
<ul>
<li class="long">Utilisation générale d'un ordinateur <p class="slider-b" id="full"></p></li>
<li>Travail en équipe <p class="slider-b" id="qv-b"></p><p class="slider-r" id="qv-r"></p></li>
<li>Softskills <p class="slider-b" id="sx-b"></p><p class="slider-r" id="sx-r"></p></li>
</ul>
</section>
<section>
<h3 class="chap">Langues</h3>
<ul>
<li>Français <p class="slider-b" id="full"></p></li>
<li>Anglais <p class="slider-b" id="qv-b"></p><p class="slider-r" id="qv-r"></p></li>
</ul>
</section>
<section>
<h3 class="chap">Informatique</h3>
<ul>
<li>Python <p class="slider-b" id="qv-b"></p><p class="slider-r" id="qv-r"></p></li>
<li>C <p class="slider-b" id="sx-b"></p><p class="slider-r" id="sx-r"></p></li>
<li>Shell Bash <p class="slider-b" id="sx-b"></p><p class="slider-r" id="sx-r"></p></li>
<li>HTML5 et CSS3 <p class="slider-b" id="qv-b"></p><p class="slider-r" id="qv-r"></p></li>
<li class="long">LaTeX / Org Mode / Markdown <p class="slider-b" id="sx-b"></p><p class="slider-r" id="sx-r"></p></li>
<li>Emacs <p class="slider-b" id="cq-b"></p><p class="slider-r" id="cq-r"></p></li>
</ul>
</section>
</aside>
<div>
<section id="profil">
<h1>Profil</h1>
<p>Passionné d'informatique et de sciences en général, je suis très et j'aime m'informer, acquérir de nombreuses connaissances et développer de nouvelles compétences. Depuis toujours j'appends en autodidactie donc j'ai beaucoup développé mon autonomie.
<br>
Je suis capable de prendre des initiatives lorsque c'est nécessaire, je m'adapte rapidemment et j'apprends vite. Je sais travailler aussi bien seul qu'en équipe.
<br>
Je suis aussi respectueux, rigoureux, efficace et sympathique</p>
</section>
<section id="xp">
<h1>Parcours professionnel</h1>
<section>
<span class="dates">08/2022</span>
<p><strong>Runner, dans la restauration</strong>
<br>
<em>Le Campa, Aix-les-Bains, 73100</em>
<br>
En tant que runner dans une équipe de 15 personnes, mon travail était majoritairement constitué de préparation de salle avant les services, de service de plats, de débarassage et rangement de la salle en fin de services. J'ai aussi eu l'occasion de faire un peu de plonge et d'aider le chef cuisinier. Grâce à cette expérience j'ai pu améliorer ma réactivité et mon endurance.</p>
</section>
<section>
<span class="dates">07/2022 <br>et<br> 07/2021</span>
<p><strong>Agent de production agroalimentaire</strong>
<br>
<em>Rochias, Issoire, 63500</em>
<br>
J'ai travaillé dans une équipe de 6 personnes, sur la chaîne de production. Mon rôle consistait à surveiller les machines de transformation, manutentionner des sacs ou caisses d'ingrédients, réaliser des recettes et préparer les commandes à l'export.</p>
</section>
<section>
<span class="dates">06/2021 ~ 07/2018</span>
<p><strong>Professeur particulier en mathématique</strong>
<br>
<em>Domicile de particuliers, Aix-les-Bains, 73100</em>
<br>
Je donnais hebdomadairement des cours de mathématique à des élèves, allant du niveau CM1 à la Première. C'était en majorité de l'aide au devoirs ou des révisions de cours en prévision de contrôles mais j'ai aussi eu l'occasion de créer, pour un enfant, un vrai programme d'apprentissage, s'étallant sur 2 mois, à base de leçons, d'exercices, de petites interro fréquentes et d'un contôle final. Cela m'a permis de développer ma pédagogie, ma patience et mon organisation de travail.</p>
</section>
</section>
<section id="formation">
<h1>Formation</h1>
<section>
<span class="dates">Actuel<br> ~ <br>09/2021</span>
<p><strong>Calsse Préparatoire Intégrée : Mathémathique et Informatique</strong><br>
<em>ISIMA - Clermont-Ferrand</em></p>
</section>
<section>
<span class="dates">06/2021<br> ~ <br>09/2018</span>
<p><strong>Baccalauréat Général</strong><br>
<em>Lycée Général et Technologique Louis Armand - Chambéry</em>
<br>
BAC mention Bien, spécialités Mathémathique et Sciences de l'Ingénieur, option Math Expertes.</p>
</section>
</section>
</div>
</body>
</html>
# CV
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://gitlab.isima.fr/ropastorel/cv.git
git branch -M master
git push -uf origin master
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.isima.fr/ropastorel/cv/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
Just my CV
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment