pyronear / pyronear/pyronear.github.io
Updating the website
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 7
- Forks
- 16
- Avg merge
- 21h 56m
- Merged PRs (30d)
- 1
Description
In overall, our site is not up to date. Before considering a global redesign of the site, it would be nice to have the following features :
-
Updates the presentation of the project
-
Adds a section listing articles where the project is mentioned, events in which Pyronear has participated
non-exhaustive list (discuss on communication channel to be up to date):
- Poster lors de la Participation au PyTorch Ecosystem Day
- Présentation de la solution au dataXdays, Organisé par les équipes de Publicis Sapient
- Enregistrement d’un podcast avec horizonIA
- Article pour le blog de Qarnot
- Interventionau MonthlyMarty de DataForGood
- Intervention au Ministère de la Transition Écologique, lors de la 1ère journée de la donnée au service de la transition écologique
- Others: le parisien / AEFinfo
- podcastdatagen
- hebdo Ardèche
- lauréat Epe
- article TF1 epe
-
Introduces section related "nos partenaires" (SDIS 07, etc)
-
Updates consequently section "ils nous soutiennent " (D4G, Atraksis, Fondation M33)
-
Adds link for donation
-
Presentation of devices / Photos
-
Team photo vs member photos ?
Happy to discuss it ! 😃
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the website repository structure and locating the existing presentation, support, partner, and project-device sections. Review the remaining unchecked items and the listed references before deciding how the content should fit the site. The work is done when the donation link, device photos, and agreed team presentation are added and the site builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, jekyll
- Domain
- content, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100