forked from Deuxfleurs/site
Compare commits
54 commits
mensualUpd
...
main
Author | SHA1 | Date | |
---|---|---|---|
a9d9ab2137 | |||
b903ebe168 | |||
3e6ae0e636 | |||
89c1b2d892 | |||
091f4ddc4a | |||
9ff1b20248 | |||
351931fdeb | |||
31aa58a863 | |||
4978b26ef6 | |||
b75294cc96 | |||
821f38c112 | |||
a007d29a9f | |||
fd276e5dc2 | |||
3a404c162c | |||
b4e50788a6 | |||
a2edf9bde5 | |||
66bb48aaa7 | |||
352c25ed3e | |||
|
c5dd5467a4 | ||
|
6ae76f5b93 | ||
|
469d165852 | ||
|
99b6eaae61 | ||
|
5f67856c95 | ||
|
547235a400 | ||
9a230c545d | |||
|
8619254c73 | ||
68e1e57468 | |||
39228d1b09 | |||
24f2d73ede | |||
eba015111f | |||
0d2b7f2fc1 | |||
ffe96d9c51 | |||
8e64f17016 | |||
6d33f1b765 | |||
40772c46cb | |||
74ae837d07 | |||
354c350375 | |||
|
edb75a5e82 | ||
65e2e2f806 | |||
fd3e318a70 | |||
|
c9d872c614 | ||
|
efcb3742b7 | ||
|
497363b343 | ||
|
ba3fc25ec4 | ||
|
fc7ea5238f | ||
|
4879267924 | ||
|
de58cd9686 | ||
|
b1149c7b90 | ||
|
526acdec1a | ||
|
79be49569f | ||
e3d6200221 | |||
821b2989a1 | |||
ffd5f97997 | |||
517c93d8fb |
19 changed files with 2377 additions and 2892 deletions
21
.editorconfig
Normal file
21
.editorconfig
Normal file
|
@ -0,0 +1,21 @@
|
|||
root = true
|
||||
|
||||
[*]
|
||||
end_of_line = lf
|
||||
trim_trailing_whitespace = true
|
||||
charset = utf-8
|
||||
|
||||
[*.{html,css,js}]
|
||||
indent_style = space
|
||||
indent_size = 2
|
||||
|
||||
[*.{yml,yaml}]
|
||||
indent_style = space
|
||||
indent_size = 2
|
||||
|
||||
[*.json]
|
||||
indent_style = space
|
||||
indent_size = 2
|
||||
|
||||
[*.md]
|
||||
trim_trailing_whitespace = false
|
56
.woodpecker.yaml
Normal file
56
.woodpecker.yaml
Normal file
|
@ -0,0 +1,56 @@
|
|||
steps:
|
||||
- name: HTML syntax check
|
||||
image: debian:12
|
||||
# Debian has tidy 5.6.0, which complains about the "loading" tag in img.
|
||||
# We need a more recent version for now.
|
||||
commands:
|
||||
- DEBIAN_FRONTEND=noninteractive apt update -qq
|
||||
- DEBIAN_FRONTEND=noninteractive apt install -qq -y wget
|
||||
- wget -q https://github.com/htacg/tidy-html5/releases/download/5.8.0/tidy-5.8.0-Linux-64bit.deb
|
||||
- echo "59e594312207234f5a17455683c13c6bc47a89cb7bf994d493acfffb591d9830 tidy-5.8.0-Linux-64bit.deb" | sha256sum -c
|
||||
- DEBIAN_FRONTEND=noninteractive apt install -qq -y ./tidy-5.8.0-Linux-64bit.deb
|
||||
- tidy -q -e --drop-empty-elements no static/index.html
|
||||
|
||||
- name: disable SEO indexing (on preprod only)
|
||||
when:
|
||||
event: [push, pull_request]
|
||||
branch: preprod
|
||||
image: debian:12 # Same as previous step to not have to download 2 images, but it could be any linux
|
||||
commands:
|
||||
- '[ -f static/robots.txt ] && echo "Disallow: /*" >> static/robots.txt'
|
||||
|
||||
- name: upload (preprod)
|
||||
when:
|
||||
event: [push, pull_request]
|
||||
branch: preprod
|
||||
image: plugins/s3
|
||||
settings:
|
||||
bucket: preprod-site
|
||||
endpoint: https://garage.deuxfleurs.fr
|
||||
region: garage
|
||||
access_key:
|
||||
from_secret: aws_access_key_id
|
||||
secret_key:
|
||||
from_secret: aws_secret_access_key
|
||||
source: static/**/*
|
||||
target: /
|
||||
strip_prefix: static/
|
||||
path_style: true
|
||||
|
||||
- name: upload (prod)
|
||||
when:
|
||||
- event: push
|
||||
branch: main
|
||||
image: plugins/s3
|
||||
settings:
|
||||
bucket: deuxfleurs.fr
|
||||
endpoint: https://garage.deuxfleurs.fr
|
||||
region: garage
|
||||
access_key:
|
||||
from_secret: aws_access_key_id
|
||||
secret_key:
|
||||
from_secret: aws_secret_access_key
|
||||
source: static/**/*
|
||||
target: /
|
||||
strip_prefix: static/
|
||||
path_style: true
|
614
LICENSE
614
LICENSE
|
@ -1,614 +0,0 @@
|
|||
GNU AFFERO GENERAL PUBLIC LICENSE
|
||||
|
||||
Version 3, 19 November 2007
|
||||
|
||||
Copyright (C) 2007 Free Software Foundation, Inc. <http s ://fsf.org/>
|
||||
|
||||
Everyone is permitted to copy and distribute verbatim copies of this license
|
||||
document, but changing it is not allowed.
|
||||
|
||||
Preamble
|
||||
|
||||
The GNU Affero General Public License is a free, copyleft license for software
|
||||
and other kinds of works, specifically designed to ensure cooperation with
|
||||
the community in the case of network server software.
|
||||
|
||||
The licenses for most software and other practical works are designed to take
|
||||
away your freedom to share and change the works. By contrast, our General
|
||||
Public Licenses are intended to guarantee your freedom to share and change
|
||||
all versions of a program--to make sure it remains free software for all its
|
||||
users.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not price. Our
|
||||
General Public Licenses are designed to make sure that you have the freedom
|
||||
to distribute copies of free software (and charge for them if you wish), that
|
||||
you receive source code or can get it if you want it, that you can change
|
||||
the software or use pieces of it in new free programs, and that you know you
|
||||
can do these things.
|
||||
|
||||
Developers that use our General Public Licenses protect your rights with two
|
||||
steps: (1) assert copyright on the software, and (2) offer you this License
|
||||
which gives you legal permission to copy, distribute and/or modify the software.
|
||||
|
||||
A secondary benefit of defending all users' freedom is that improvements made
|
||||
in alternate versions of the program, if they receive widespread use, become
|
||||
available for other developers to incorporate. Many developers of free software
|
||||
are heartened and encouraged by the resulting cooperation. However, in the
|
||||
case of software used on network servers, this result may fail to come about.
|
||||
The GNU General Public License permits making a modified version and letting
|
||||
the public access it on a server without ever releasing its source code to
|
||||
the public.
|
||||
|
||||
The GNU Affero General Public License is designed specifically to ensure that,
|
||||
in such cases, the modified source code becomes available to the community.
|
||||
It requires the operator of a network server to provide the source code of
|
||||
the modified version running there to the users of that server. Therefore,
|
||||
public use of a modified version, on a publicly accessible server, gives the
|
||||
public access to the source code of the modified version.
|
||||
|
||||
An older license, called the Affero General Public License and published by
|
||||
Affero, was designed to accomplish similar goals. This is a different license,
|
||||
not a version of the Affero GPL, but Affero has released a new version of
|
||||
the Affero GPL which permits relicensing under this license.
|
||||
|
||||
The precise terms and conditions for copying, distribution and modification
|
||||
follow.
|
||||
|
||||
TERMS AND CONDITIONS
|
||||
|
||||
0. Definitions.
|
||||
|
||||
"This License" refers to version 3 of the GNU Affero General Public License.
|
||||
|
||||
"Copyright" also means copyright-like laws that apply to other kinds of works,
|
||||
such as semiconductor masks.
|
||||
|
||||
"The Program" refers to any copyrightable work licensed under this License.
|
||||
Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals
|
||||
or organizations.
|
||||
|
||||
To "modify" a work means to copy from or adapt all or part of the work in
|
||||
a fashion requiring copyright permission, other than the making of an exact
|
||||
copy. The resulting work is called a "modified version" of the earlier work
|
||||
or a work "based on" the earlier work.
|
||||
|
||||
A "covered work" means either the unmodified Program or a work based on the
|
||||
Program.
|
||||
|
||||
To "propagate" a work means to do anything with it that, without permission,
|
||||
would make you directly or secondarily liable for infringement under applicable
|
||||
copyright law, except executing it on a computer or modifying a private copy.
|
||||
Propagation includes copying, distribution (with or without modification),
|
||||
making available to the public, and in some countries other activities as
|
||||
well.
|
||||
|
||||
To "convey" a work means any kind of propagation that enables other parties
|
||||
to make or receive copies. Mere interaction with a user through a computer
|
||||
network, with no transfer of a copy, is not conveying.
|
||||
|
||||
An interactive user interface displays "Appropriate Legal Notices" to the
|
||||
extent that it includes a convenient and prominently visible feature that
|
||||
(1) displays an appropriate copyright notice, and (2) tells the user that
|
||||
there is no warranty for the work (except to the extent that warranties are
|
||||
provided), that licensees may convey the work under this License, and how
|
||||
to view a copy of this License. If the interface presents a list of user commands
|
||||
or options, such as a menu, a prominent item in the list meets this criterion.
|
||||
|
||||
1. Source Code.
|
||||
|
||||
The "source code" for a work means the preferred form of the work for making
|
||||
modifications to it. "Object code" means any non-source form of a work.
|
||||
|
||||
A "Standard Interface" means an interface that either is an official standard
|
||||
defined by a recognized standards body, or, in the case of interfaces specified
|
||||
for a particular programming language, one that is widely used among developers
|
||||
working in that language.
|
||||
|
||||
The "System Libraries" of an executable work include anything, other than
|
||||
the work as a whole, that (a) is included in the normal form of packaging
|
||||
a Major Component, but which is not part of that Major Component, and (b)
|
||||
serves only to enable use of the work with that Major Component, or to implement
|
||||
a Standard Interface for which an implementation is available to the public
|
||||
in source code form. A "Major Component", in this context, means a major essential
|
||||
component (kernel, window system, and so on) of the specific operating system
|
||||
(if any) on which the executable work runs, or a compiler used to produce
|
||||
the work, or an object code interpreter used to run it.
|
||||
|
||||
The "Corresponding Source" for a work in object code form means all the source
|
||||
code needed to generate, install, and (for an executable work) run the object
|
||||
code and to modify the work, including scripts to control those activities.
|
||||
However, it does not include the work's System Libraries, or general-purpose
|
||||
tools or generally available free programs which are used unmodified in performing
|
||||
those activities but which are not part of the work. For example, Corresponding
|
||||
Source includes interface definition files associated with source files for
|
||||
the work, and the source code for shared libraries and dynamically linked
|
||||
subprograms that the work is specifically designed to require, such as by
|
||||
intimate data communication or control flow between those
|
||||
|
||||
subprograms and other parts of the work.
|
||||
|
||||
The Corresponding Source need not include anything that users can regenerate
|
||||
automatically from other parts of the Corresponding Source.
|
||||
|
||||
The Corresponding Source for a work in source code form is that same work.
|
||||
|
||||
2. Basic Permissions.
|
||||
|
||||
All rights granted under this License are granted for the term of copyright
|
||||
on the Program, and are irrevocable provided the stated conditions are met.
|
||||
This License explicitly affirms your unlimited permission to run the unmodified
|
||||
Program. The output from running a covered work is covered by this License
|
||||
only if the output, given its content, constitutes a covered work. This License
|
||||
acknowledges your rights of fair use or other equivalent, as provided by copyright
|
||||
law.
|
||||
|
||||
You may make, run and propagate covered works that you do not convey, without
|
||||
conditions so long as your license otherwise remains in force. You may convey
|
||||
covered works to others for the sole purpose of having them make modifications
|
||||
exclusively for you, or provide you with facilities for running those works,
|
||||
provided that you comply with the terms of this License in conveying all material
|
||||
for which you do not control copyright. Those thus making or running the covered
|
||||
works for you must do so exclusively on your behalf, under your direction
|
||||
and control, on terms that prohibit them from making any copies of your copyrighted
|
||||
material outside their relationship with you.
|
||||
|
||||
Conveying under any other circumstances is permitted solely under the conditions
|
||||
stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
|
||||
|
||||
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
|
||||
|
||||
No covered work shall be deemed part of an effective technological measure
|
||||
under any applicable law fulfilling obligations under article 11 of the WIPO
|
||||
copyright treaty adopted on 20 December 1996, or similar laws prohibiting
|
||||
or restricting circumvention of such measures.
|
||||
|
||||
When you convey a covered work, you waive any legal power to forbid circumvention
|
||||
of technological measures to the extent such circumvention is effected by
|
||||
exercising rights under this License with respect to the covered work, and
|
||||
you disclaim any intention to limit operation or modification of the work
|
||||
as a means of enforcing, against the work's users, your or third parties'
|
||||
legal rights to forbid circumvention of technological measures.
|
||||
|
||||
4. Conveying Verbatim Copies.
|
||||
|
||||
You may convey verbatim copies of the Program's source code as you receive
|
||||
it, in any medium, provided that you conspicuously and appropriately publish
|
||||
on each copy an appropriate copyright notice; keep intact all notices stating
|
||||
that this License and any non-permissive terms added in accord with section
|
||||
7 apply to the code; keep intact all notices of the absence of any warranty;
|
||||
and give all recipients a copy of this License along with the Program.
|
||||
|
||||
You may charge any price or no price for each copy that you convey, and you
|
||||
may offer support or warranty protection for a fee.
|
||||
|
||||
5. Conveying Modified Source Versions.
|
||||
|
||||
You may convey a work based on the Program, or the modifications to produce
|
||||
it from the Program, in the form of source code under the terms of section
|
||||
4, provided that you also meet all of these conditions:
|
||||
|
||||
a) The work must carry prominent notices stating that you modified it, and
|
||||
giving a relevant date.
|
||||
|
||||
b) The work must carry prominent notices stating that it is released under
|
||||
this License and any conditions added under section 7. This requirement modifies
|
||||
the requirement in section 4 to "keep intact all notices".
|
||||
|
||||
c) You must license the entire work, as a whole, under this License to anyone
|
||||
who comes into possession of a copy. This License will therefore apply, along
|
||||
with any applicable section 7 additional terms, to the whole of the work,
|
||||
and all its parts, regardless of how they are packaged. This License gives
|
||||
no permission to license the work in any other way, but it does not invalidate
|
||||
such permission if you have separately received it.
|
||||
|
||||
d) If the work has interactive user interfaces, each must display Appropriate
|
||||
Legal Notices; however, if the Program has interactive interfaces that do
|
||||
not display Appropriate Legal Notices, your work need not make them do so.
|
||||
|
||||
A compilation of a covered work with other separate and independent works,
|
||||
which are not by their nature extensions of the covered work, and which are
|
||||
not combined with it such as to form a larger program, in or on a volume of
|
||||
a storage or distribution medium, is called an "aggregate" if the compilation
|
||||
and its resulting copyright are not used to limit the access or legal rights
|
||||
of the compilation's users beyond what the individual works permit. Inclusion
|
||||
of a covered work in an aggregate does not cause this License to apply to
|
||||
the other parts of the aggregate.
|
||||
|
||||
6. Conveying Non-Source Forms.
|
||||
|
||||
You may convey a covered work in object code form under the terms of sections
|
||||
4 and 5, provided that you also convey the machine-readable Corresponding
|
||||
Source under the terms of this License, in one of these ways:
|
||||
|
||||
a) Convey the object code in, or embodied in, a physical product (including
|
||||
a physical distribution medium), accompanied by the Corresponding Source fixed
|
||||
on a durable physical medium customarily used for software interchange.
|
||||
|
||||
b) Convey the object code in, or embodied in, a physical product (including
|
||||
a physical distribution medium), accompanied by a written offer, valid for
|
||||
at least three years and valid for as long as you offer spare parts or customer
|
||||
support for that product model, to give anyone who possesses the object code
|
||||
either (1) a copy of the Corresponding Source for all the software in the
|
||||
product that is covered by this License, on a durable physical medium customarily
|
||||
used for software interchange, for a price no more than your reasonable cost
|
||||
of physically performing this conveying of source, or (2) access to copy the
|
||||
Corresponding Source from a network server at no charge.
|
||||
|
||||
c) Convey individual copies of the object code with a copy of the written
|
||||
offer to provide the Corresponding Source. This alternative is allowed only
|
||||
occasionally and noncommercially, and only if you received the object code
|
||||
with such an offer, in accord with subsection 6b.
|
||||
|
||||
d) Convey the object code by offering access from a designated place (gratis
|
||||
or for a charge), and offer equivalent access to the Corresponding Source
|
||||
in the same way through the same place at no further charge. You need not
|
||||
require recipients to copy the Corresponding Source along with the object
|
||||
code. If the place to copy the object code is a network server, the Corresponding
|
||||
Source may be on a different server (operated by you or a third party) that
|
||||
supports equivalent copying facilities, provided you maintain clear directions
|
||||
next to the object code saying where to find the Corresponding Source. Regardless
|
||||
of what server hosts the Corresponding Source, you remain obligated to ensure
|
||||
that it is available for as long as needed to satisfy these requirements.
|
||||
|
||||
e) Convey the object code using peer-to-peer transmission, provided you inform
|
||||
other peers where the object code and Corresponding Source of the work are
|
||||
being offered to the general public at no charge under subsection 6d.
|
||||
|
||||
A separable portion of the object code, whose source code is excluded from
|
||||
the Corresponding Source as a System Library, need not be included in conveying
|
||||
the object code work.
|
||||
|
||||
A "User Product" is either (1) a "consumer product", which means any tangible
|
||||
personal property which is normally used for personal, family, or household
|
||||
purposes, or (2) anything designed or sold for incorporation into a dwelling.
|
||||
In determining whether a product is a consumer product, doubtful cases shall
|
||||
be resolved in favor of coverage. For a particular product received by a particular
|
||||
user, "normally used" refers to a typical or common use of that class of product,
|
||||
regardless of the status of the particular user or of the way in which the
|
||||
particular user actually uses, or expects or is expected to use, the product.
|
||||
A product is a consumer product regardless of whether the product has substantial
|
||||
commercial, industrial or non-consumer uses, unless such uses represent the
|
||||
only significant mode of use of the product.
|
||||
|
||||
"Installation Information" for a User Product means any methods, procedures,
|
||||
authorization keys, or other information required to install and execute modified
|
||||
versions of a covered work in that User Product from a modified version of
|
||||
its Corresponding Source. The information must suffice to ensure that the
|
||||
continued functioning of the modified object code is in no case prevented
|
||||
or interfered with solely because modification has been made.
|
||||
|
||||
If you convey an object code work under this section in, or with, or specifically
|
||||
for use in, a User Product, and the conveying occurs as part of a transaction
|
||||
in which the right of possession and use of the User Product is transferred
|
||||
to the recipient in perpetuity or for a fixed term (regardless of how the
|
||||
transaction is characterized), the Corresponding Source conveyed under this
|
||||
section must be accompanied by the Installation Information. But this requirement
|
||||
does not apply if neither you nor any third party retains the ability to install
|
||||
modified object code on the User Product (for example, the work has been installed
|
||||
in ROM).
|
||||
|
||||
The requirement to provide Installation Information does not include a requirement
|
||||
to continue to provide support service, warranty, or updates for a work that
|
||||
has been modified or installed by the recipient, or for the User Product in
|
||||
which it has been modified or installed. Access to a network may be denied
|
||||
when the modification itself materially and adversely affects the operation
|
||||
of the network or violates the rules and protocols for communication across
|
||||
the network.
|
||||
|
||||
Corresponding Source conveyed, and Installation Information provided, in accord
|
||||
with this section must be in a format that is publicly documented (and with
|
||||
an implementation available to the public in source code form), and must require
|
||||
no special password or key for unpacking, reading or copying.
|
||||
|
||||
7. Additional Terms.
|
||||
|
||||
"Additional permissions" are terms that supplement the terms of this License
|
||||
by making exceptions from one or more of its conditions. Additional permissions
|
||||
that are applicable to the entire Program shall be treated as though they
|
||||
were included in this License, to the extent that they are valid under applicable
|
||||
law. If additional permissions apply only to part of the Program, that part
|
||||
may be used separately under those permissions, but the entire Program remains
|
||||
governed by this License without regard to the additional permissions.
|
||||
|
||||
When you convey a copy of a covered work, you may at your option remove any
|
||||
additional permissions from that copy, or from any part of it. (Additional
|
||||
permissions may be written to require their own removal in certain cases when
|
||||
you modify the work.) You may place additional permissions on material, added
|
||||
by you to a covered work, for which you have or can give appropriate copyright
|
||||
permission.
|
||||
|
||||
Notwithstanding any other provision of this License, for material you add
|
||||
to a covered work, you may (if authorized by the copyright holders of that
|
||||
material) supplement the terms of this License with terms:
|
||||
|
||||
a) Disclaiming warranty or limiting liability differently from the terms of
|
||||
sections 15 and 16 of this License; or
|
||||
|
||||
b) Requiring preservation of specified reasonable legal notices or author
|
||||
attributions in that material or in the Appropriate Legal Notices displayed
|
||||
by works containing it; or
|
||||
|
||||
c) Prohibiting misrepresentation of the origin of that material, or requiring
|
||||
that modified versions of such material be marked in reasonable ways as different
|
||||
from the original version; or
|
||||
|
||||
d) Limiting the use for publicity purposes of names of licensors or authors
|
||||
of the material; or
|
||||
|
||||
e) Declining to grant rights under trademark law for use of some trade names,
|
||||
trademarks, or service marks; or
|
||||
|
||||
f) Requiring indemnification of licensors and authors of that material by
|
||||
anyone who conveys the material (or modified versions of it) with contractual
|
||||
assumptions of liability to the recipient, for any liability that these contractual
|
||||
assumptions directly impose on those licensors and authors.
|
||||
|
||||
All other non-permissive additional terms are considered "further restrictions"
|
||||
within the meaning of section 10. If the Program as you received it, or any
|
||||
part of it, contains a notice stating that it is governed by this License
|
||||
along with a term that is a further restriction, you may remove that term.
|
||||
If a license document contains a further restriction but permits relicensing
|
||||
or conveying under this License, you may add to a covered work material governed
|
||||
by the terms of that license document, provided that the further restriction
|
||||
does not survive such relicensing or conveying.
|
||||
|
||||
If you add terms to a covered work in accord with this section, you must place,
|
||||
in the relevant source files, a statement of the additional terms that apply
|
||||
to those files, or a notice indicating where to find the applicable terms.
|
||||
|
||||
Additional terms, permissive or non-permissive, may be stated in the form
|
||||
of a separately written license, or stated as exceptions; the above requirements
|
||||
apply either way.
|
||||
|
||||
8. Termination.
|
||||
|
||||
You may not propagate or modify a covered work except as expressly provided
|
||||
under this License. Any attempt otherwise to propagate or modify it is void,
|
||||
and will automatically terminate your rights under this License (including
|
||||
any patent licenses granted under the third paragraph of section 11).
|
||||
|
||||
However, if you cease all violation of this License, then your license from
|
||||
a particular copyright holder is reinstated (a) provisionally, unless and
|
||||
until the copyright holder explicitly and finally terminates your license,
|
||||
and (b) permanently, if the copyright holder fails to notify you of the violation
|
||||
by some reasonable means prior to 60 days after the cessation.
|
||||
|
||||
Moreover, your license from a particular copyright holder is reinstated permanently
|
||||
if the copyright holder notifies you of the violation by some reasonable means,
|
||||
this is the first time you have received notice of violation of this License
|
||||
(for any work) from that copyright holder, and you cure the violation prior
|
||||
to 30 days after your receipt of the notice.
|
||||
|
||||
Termination of your rights under this section does not terminate the licenses
|
||||
of parties who have received copies or rights from you under this License.
|
||||
If your rights have been terminated and not permanently reinstated, you do
|
||||
not qualify to receive new licenses for the same material under section 10.
|
||||
|
||||
9. Acceptance Not Required for Having Copies.
|
||||
|
||||
You are not required to accept this License in order to receive or run a copy
|
||||
of the Program. Ancillary propagation of a covered work occurring solely as
|
||||
a consequence of using peer-to-peer transmission to receive a copy likewise
|
||||
does not require acceptance. However, nothing other than this License grants
|
||||
you permission to propagate or modify any covered work. These actions infringe
|
||||
copyright if you do not accept this License. Therefore, by modifying or propagating
|
||||
a covered work, you indicate your acceptance of this License to do so.
|
||||
|
||||
10. Automatic Licensing of Downstream Recipients.
|
||||
|
||||
Each time you convey a covered work, the recipient automatically receives
|
||||
a license from the original licensors, to run, modify and propagate that work,
|
||||
subject to this License. You are not responsible for enforcing compliance
|
||||
by third parties with this License.
|
||||
|
||||
An "entity transaction" is a transaction transferring control of an organization,
|
||||
or substantially all assets of one, or subdividing an organization, or merging
|
||||
organizations. If propagation of a covered work results from an entity transaction,
|
||||
each party to that transaction who receives a copy of the work also receives
|
||||
whatever licenses to the work the party's predecessor in interest had or could
|
||||
give under the previous paragraph, plus a right to possession of the Corresponding
|
||||
Source of the work from the predecessor in interest, if the predecessor has
|
||||
it or can get it with reasonable efforts.
|
||||
|
||||
You may not impose any further restrictions on the exercise of the rights
|
||||
granted or affirmed under this License. For example, you may not impose a
|
||||
license fee, royalty, or other charge for exercise of rights granted under
|
||||
this License, and you may not initiate litigation (including a cross-claim
|
||||
or counterclaim in a lawsuit) alleging that any patent claim is infringed
|
||||
by making, using, selling, offering for sale, or importing the Program or
|
||||
any portion of it.
|
||||
|
||||
11. Patents.
|
||||
|
||||
A "contributor" is a copyright holder who authorizes use under this License
|
||||
of the Program or a work on which the Program is based. The work thus licensed
|
||||
is called the contributor's "contributor version".
|
||||
|
||||
A contributor's "essential patent claims" are all patent claims owned or controlled
|
||||
by the contributor, whether already acquired or hereafter acquired, that would
|
||||
be infringed by some manner, permitted by this License, of making, using,
|
||||
or selling its contributor version, but do not include claims that would be
|
||||
infringed only as a consequence of further modification of the contributor
|
||||
version. For purposes of this definition, "control" includes the right to
|
||||
grant patent sublicenses in a manner consistent with the requirements of this
|
||||
License.
|
||||
|
||||
Each contributor grants you a non-exclusive, worldwide, royalty-free patent
|
||||
license under the contributor's essential patent claims, to make, use, sell,
|
||||
offer for sale, import and otherwise run, modify and propagate the contents
|
||||
of its contributor version.
|
||||
|
||||
In the following three paragraphs, a "patent license" is any express agreement
|
||||
or commitment, however denominated, not to enforce a patent (such as an express
|
||||
permission to practice a patent or covenant not to s ue for patent infringement).
|
||||
To "grant" such a patent license to a party means to make such an agreement
|
||||
or commitment not to enforce a patent against the party.
|
||||
|
||||
If you convey a covered work, knowingly relying on a patent license, and the
|
||||
Corresponding Source of the work is not available for anyone to copy, free
|
||||
of charge and under the terms of this License, through a publicly available
|
||||
network server or other readily accessible means, then you must either (1)
|
||||
cause the Corresponding Source to be so available, or (2) arrange to deprive
|
||||
yourself of the benefit of the patent license for this particular work, or
|
||||
(3) arrange, in a manner consistent with the requirements of this License,
|
||||
to extend the patent
|
||||
|
||||
license to downstream recipients. "Knowingly relying" means you have actual
|
||||
knowledge that, but for the patent license, your conveying the covered work
|
||||
in a country, or your recipient's use of the covered work in a country, would
|
||||
infringe one or more identifiable patents in that country that you have reason
|
||||
to believe are valid.
|
||||
|
||||
If, pursuant to or in connection with a single transaction or arrangement,
|
||||
you convey, or propagate by procuring conveyance of, a covered work, and grant
|
||||
a patent license to some of the parties receiving the covered work authorizing
|
||||
them to use, propagate, modify or convey a specific copy of the covered work,
|
||||
then the patent license you grant is automatically extended to all recipients
|
||||
of the covered work and works based on it.
|
||||
|
||||
A patent license is "discriminatory" if it does not include within the scope
|
||||
of its coverage, prohibits the exercise of, or is conditioned on the non-exercise
|
||||
of one or more of the rights that are specifically granted under this License.
|
||||
You may not convey a covered work if you are a party to an arrangement with
|
||||
a third party that is in the business of distributing software, under which
|
||||
you make payment to the third party based on the extent of your activity of
|
||||
conveying the work, and under which the third party grants, to any of the
|
||||
parties who would receive the covered work from you, a discriminatory patent
|
||||
license (a) in connection with copies of the covered work conveyed by you
|
||||
(or copies made from those copies), or (b) primarily for and in connection
|
||||
with specific products or compilations that contain the covered work, unless
|
||||
you entered into that arrangement, or that patent license was granted, prior
|
||||
to 28 March 2007.
|
||||
|
||||
Nothing in this License shall be construed as excluding or limiting any implied
|
||||
license or other defenses to infringement that may otherwise be available
|
||||
to you under applicable patent law.
|
||||
|
||||
12. No Surrender of Others' Freedom.
|
||||
|
||||
If conditions are imposed on you (whether by court order, agreement or otherwise)
|
||||
that contradict the conditions of this License, they do not excuse you from
|
||||
the conditions of this License. If you cannot convey a covered work so as
|
||||
to satisfy simultaneously your obligations under this License and any other
|
||||
pertinent obligations, then as a consequence you may
|
||||
|
||||
not convey it at all. For example, if you agree to terms that obligate you
|
||||
to collect a royalty for further conveying from those to whom you convey the
|
||||
Program, the only way you could satisfy both those terms and this License
|
||||
would be to refrain entirely from conveying the Program.
|
||||
|
||||
13. Remote Network Interaction; Use with the GNU General Public License.
|
||||
|
||||
Notwithstanding any other provision of this License, if you modify the Program,
|
||||
your modified version must prominently offer all users interacting with it
|
||||
remotely through a computer network (if your version supports such interaction)
|
||||
an opportunity to receive the Corresponding Source of your version by providing
|
||||
access to the Corresponding Source from a network server at no charge, through
|
||||
some standard or customary means of facilitating copying of software. This
|
||||
Corresponding Source shall include the Corresponding Source for any work covered
|
||||
by version 3 of the GNU General Public License that is incorporated pursuant
|
||||
to the following paragraph.
|
||||
|
||||
Notwithstanding any other provision of this License, you have permission to
|
||||
link or combine any covered work with a work licensed under version 3 of the
|
||||
GNU General Public License into a single combined work, and to convey the
|
||||
resulting work. The terms of this License will continue to apply to the part
|
||||
which is the covered work, but the work with which it is combined will remain
|
||||
governed by version 3 of the GNU General Public License.
|
||||
|
||||
14. Revised Versions of this License.
|
||||
|
||||
The Free Software Foundation may publish revised and/or new versions of the
|
||||
GNU Affero General Public License from time to time. Such new versions will
|
||||
be similar in spirit to the present version, but may differ in detail to address
|
||||
new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the Program specifies
|
||||
that a certain numbered version of the GNU Affero General Public License "or
|
||||
any later version" applies to it, you have the option of following the terms
|
||||
and conditions either of that numbered version or of any later version published
|
||||
by the Free Software Foundation. If the Program does not specify a version
|
||||
number of the GNU Affero General Public License, you may choose any version
|
||||
ever published by the Free Software Foundation.
|
||||
|
||||
If the Program specifies that a proxy can decide which future versions of
|
||||
the GNU Affero General Public License can be used, that proxy's public statement
|
||||
of acceptance of a version permanently authorizes you to choose that version
|
||||
for the Program.
|
||||
|
||||
Later license versions may give you additional or different permissions. However,
|
||||
no additional obligations are imposed on any author or copyright holder as
|
||||
a result of your choosing to follow a later version.
|
||||
|
||||
15. Disclaimer of Warranty.
|
||||
|
||||
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
|
||||
LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
|
||||
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
|
||||
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
|
||||
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
||||
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
|
||||
PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
|
||||
CORRECTION.
|
||||
|
||||
16. Limitation of Liability.
|
||||
|
||||
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
|
||||
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM
|
||||
AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
|
||||
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO
|
||||
USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
|
||||
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
|
||||
PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
|
||||
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
|
||||
|
||||
17. Interpretation of Sections 15 and 16.
|
||||
|
||||
If the disclaimer of warranty and limitation of liability provided above cannot
|
||||
be given local legal effect according to their terms, reviewing courts shall
|
||||
apply local law that most closely approximates an absolute waiver of all civil
|
||||
liability in connection with the Program, unless a warranty or assumption
|
||||
of liability accompanies a copy of the Program in return for a fee. END OF
|
||||
TERMS AND CONDITIONS
|
||||
|
||||
How to Apply These Terms to Your New Programs
|
||||
|
||||
If you develop a new program, and you want it to be of the greatest possible
|
||||
use to the public, the best way to achieve this is to make it free software
|
||||
which everyone can redistribute and change under these terms.
|
||||
|
||||
To do so, attach the following notices to the program. It is safest to attach
|
||||
them to the start of each source file to most effectively state the exclusion
|
||||
of warranty; and each file should have at least the "copyright" line and a
|
||||
pointer to where the full notice is found.
|
||||
|
||||
<one line to give the program's name and a brief idea of what it does.>
|
||||
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This program is free software: you can redistribute it and/or modify it under
|
||||
the terms of the GNU Affero General Public License as published by the Free
|
||||
Software Foundation, either version 3 of the License, or (at your option)
|
||||
any later version.
|
||||
|
||||
This program is distributed in the hope that it will be useful, but WITHOUT
|
||||
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
||||
FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
|
||||
details.
|
||||
|
||||
You should have received a copy of the GNU Affero General Public License along
|
||||
with this program. If not, see <http s ://www.gnu.org/licenses/>.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
If your software can interact with users remotely through a computer network,
|
||||
you should also make sure that it provides a way for users to get its source.
|
||||
For example, if your program is a web application, its interface could display
|
||||
a "Source" link that leads users to an archive of the code. There are many
|
||||
ways you could offer source, and different solutions will be better for different
|
||||
programs; see section 13 for the specific requirements.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or school,
|
||||
if any, to sign a "copyright disclaimer" for the program, if necessary. For
|
||||
more information on this, and how to apply and follow the GNU AGPL, see <http
|
||||
s ://www.gnu.org/licenses/>.
|
16
README.md
16
README.md
|
@ -37,10 +37,20 @@ Fabriquons un internet convivial ⤵
|
|||
|
||||
Pas maintenant.
|
||||
|
||||
## Déployer
|
||||
## Déployer en pré-production
|
||||
|
||||
⚠️ NE FAITES PAS `--delete` car il est fort probable que des trucs qui doivent rester dans le bucket
|
||||
ne sont pas copiés ici
|
||||
Fait automatiquement via Woodpecker sur la branche `preprod`.
|
||||
|
||||
Le site en pré-production est ensuite accessible sur <https://preprod-site.web.deuxfleurs.fr/>
|
||||
|
||||
## Déployer en production
|
||||
|
||||
Fait automatiquement via Woodpecker sur la branche `main`.
|
||||
|
||||
## Déployer en production à la main (pas recommandé)
|
||||
|
||||
En cas de déploiement manuel : ⚠️ NE FAITES PAS `--delete` car il est fort probable
|
||||
que des trucs qui doivent rester dans le bucket ne sont pas copiés ici.
|
||||
|
||||
```
|
||||
aws s3 sync static/ s3://deuxfleurs.fr
|
||||
|
|
36
rapport.md
Normal file
36
rapport.md
Normal file
|
@ -0,0 +1,36 @@
|
|||
# DeuxFleurs, un site accessible ? -- Sommaire exécutif
|
||||
|
||||
_Lundi 12 février 2024, par Adrian Rosin & Adrien Luxey-Bitri_
|
||||
|
||||
## Des principes solides
|
||||
|
||||
Dans l’ensemble, deuxfleurs a posé des bases solides en termes d’accessibilité. Le code est correctement structuré et pensé pour garantir une accessibilité maximale. Il met en pratique les principaux standards d’accessibilité issus de W3C, ce qui témoigne de la qualité du travail réalisé. Il faut également noter que pour chaque élément du site, des recherches ont été réalisées, rien n'a été laissé au hasard et une attention méticuleuse quant à l'accessibilité a été pensée.
|
||||
|
||||
Par conséquent, on s’aperçoit que deuxfleurs, avant même de passer des tests fonctionnels, valide la plupart des principes d’accessibilité sur le web. Le site valide par exemple les instructions que met à disposition Access42 (https://access42.net/ressources/site-web-accessible/), une coopérative française qui réalise des audits sur l’accessibilité numérique et dont les critères post-audit permettent dans un premier temps de savoir si un site est sur la bonne direction ou non.
|
||||
|
||||
## Tests fonctionnels
|
||||
|
||||
Si l’on passe le site sur des outils permettant de vérifier l’accessibilité (ADA, WCAG, WCAG2, … Pour plus d'informations, voir https://www.w3.org/WAI/ER/tools//index.html), celui-ci passe plus des trois quarts des tests concernant l’accessibilité. Les tests critiques passant dans l’intégralité. Les seuls tests non validés sont des erreurs potentielles sujettes à interprétation, qui résultent d'un choix conscient chez Deuxfleurs (commande artistique).
|
||||
|
||||
Pour donner des exemples de suggestions d'améliorations d'accéssibilité que l'on peut proposer après une première analyse du site :
|
||||
l’utilisation de balises `svg` à la place de balises préformatées `pre` pour gérer l’ASCII art en terme d’image et non en terme de texte ;
|
||||
l'affichage des calendriers en tant qu’objet (`table`) plutôt qu’en texte sous balise préformatée ;
|
||||
l'augmentation du contraste texte/fond…
|
||||
|
||||
En deuxième analyse, on comprend que les idées ci-dessus ont été analysées, et que les solutions retenues résultent d'un compromis entre accessibilité et démarche artistique.
|
||||
|
||||
## Commande artistique
|
||||
|
||||
Il a été demandé à la créatrice du site de concevoir un site simple et léger (sans image sauf l'illustration de Ronce).
|
||||
De plus, le code HTML se lit comme un journal, où ASCII art et textes se succèdent sans friction.
|
||||
On comprend mieux alors, que l'usage de `svg` contredit l'esprit recherché, puisqu'il ajoute une lourdeur inutile au code source.
|
||||
|
||||
## En pratique
|
||||
|
||||
Le site dans son ensemble actuel peut être considéré comme accessible. Lorsque le site est utilisé avec un narrateur, tout le contenu est décrit de manière simple et fluide assurant une bonne compréhension de celui-ci pour tous les utilisateurs. Malgré cela, le résultat obtenu diffère en fonction du système d’exploitation, du narrateur utilisé ou même du paramétrage de celui-ci.
|
||||
|
||||
A ce titre, une expérience à plus grande échelle impliquant des personnes directement concernées par les lecteurs d’écran pourrait nous en apprendre davantage quant à l’accessibilité de deuxfleurs.
|
||||
|
||||
## Nous contacter
|
||||
|
||||
Si vous souhaitez nous faire des retours concernant l’accessibilité du site deuxfleurs, vous pouvez nous contacter [ici](https://matrix.to/#/#accessibilite:deuxfleurs.fr) ou via coucou _chez_ deuxfleurs.fr
|
|
@ -1,8 +1,9 @@
|
|||
<!DOCTYPE html><html lang="fr"><head><meta charset="utf-8"><title>💮💮 deuxfleurs - deuxfleurs</title><link rel="stylesheet" href="/css/main.css"><meta name="viewport" content="width=device-width, initial-scale=1.0"></head><body><aside><header><a class="mobile_inline" id="menu" href="#"><svg viewBox="0 0 100 80" width="40" height="40"><rect width="100" height="20"></rect><rect y="30" width="100" height="20"></rect><rect y="60" width="100" height="20"></rect></svg></a><h1><a href="/">deuxfleurs</a></h1><nav class="computer_block"><section class="center"><img alt="emoji fleur" src="/img/flower.svg" width="40"> <img alt="emoji fleur" src="/img/flower.svg" width="40"></section><ul><li><a href="https://plume.deuxfleurs.fr/timeline/1">Actualités</a></li><li><a href="https://man.deuxfleurs.fr">Wiki</a></li><li><a href="https://guichet.deuxfleurs.fr">Mon compte</a></li></ul><hr><ul><li><a href="/CGU.html">CGU</a></li><li><a href="/Gestion des risques.html">Gestion des risques</a></li><li><a href="/Mentions légales.html">Mentions légales</a></li><li><a href="/Sources.html">Sources</a></li></ul></nav></header></aside><main><section><h1>404 - Page non trouvée</h1><p>La page que vous cherchez n'existe pas sur ce site web.</p><p>Si vous pensez que c'est une erreur, les informations pour nous contacter sont disponibles sur notre page d'accueil.</p></section></main><script>(_ => {
|
||||
const hamburger = document.getElementById('menu')
|
||||
hamburger.onclick = _ => {
|
||||
const nav = document.querySelector('body > aside > header > nav')
|
||||
console.log(nav.style.display)
|
||||
nav.style.display = nav.style.display != 'block' ? 'block' : 'none'
|
||||
}
|
||||
})()</script></body></html>
|
||||
<!DOCTYPE html><html lang="fr"><head><meta charset="utf-8"><title>💮💮 deuxfleurs</title></head>
|
||||
<body>
|
||||
<p>Erreur 404 - page non trouvée, cette page n'existe pas (ou a été déplacée, j'en sais rien moi !)</p>
|
||||
<p>Est-ce que tu cherches la <a href="https://deuxfleurs.fr/">page d'accueil</a> ?
|
||||
Le <a href="https://guide.deuxfleurs.fr/">guide</a> ?
|
||||
Le <a href="https://guichet.deuxfleurs.fr/">guichet</a> ?
|
||||
Les <a href="https://plume.deuxfleurs.fr/">big news de l'espace</a> ?</p>
|
||||
<p>Si tu es toujours paumé⋅e, viens nous parler sur Matrix ou écris à <code>coucou@deuxfleurs.fr</code>!</p>
|
||||
</body></html>
|
||||
|
|
|
@ -1,8 +0,0 @@
|
|||
<!DOCTYPE html><html lang="fr"><head><meta charset="utf-8"><title>💮💮 deuxfleurs - Visioconférence</title><link rel="stylesheet" href="/css/main.css"><meta name="viewport" content="width=device-width, initial-scale=1.0"></head><body><aside><header><a class="mobile_inline" id="menu" href="#"><svg viewBox="0 0 100 80" width="40" height="40"><rect width="100" height="20"></rect><rect y="30" width="100" height="20"></rect><rect y="60" width="100" height="20"></rect></svg></a><h1><a href="/">deuxfleurs</a></h1><nav class="computer_block"><section class="center"><img alt="emoji fleur" src="/img/flower.svg" width="40"> <img alt="emoji fleur" src="/img/flower.svg" width="40"></section><ul><li><a href="https://plume.deuxfleurs.fr/timeline/1">Actualités</a></li><li><a href="https://wiki.deuxfleurs.fr">Wiki</a></li><li><a href="https://guichet.deuxfleurs.fr">Mon compte</a></li></ul><hr><ul><li><a href="/CGU.html">CGU</a></li><li><a href="/Gestion des risques.html">Gestion des risques</a></li><li><a href="/Mentions légales.html">Mentions légales</a></li></ul></nav></header></aside><main><h4 class="spacing"> Cette page a changé d'adresse : <a href="/Guide/Visioconférence.html">cliquez ici pour être redirigé</a></h4></main><script>(_ => {
|
||||
const hamburger = document.getElementById('menu')
|
||||
hamburger.onclick = _ => {
|
||||
const nav = document.querySelector('body > aside > header > nav')
|
||||
console.log(nav.style.display)
|
||||
nav.style.display = nav.style.display != 'block' ? 'block' : 'none'
|
||||
}
|
||||
})()</script></body></html>
|
|
@ -1,13 +0,0 @@
|
|||
<!DOCTYPE html><html lang="fr"><head><meta charset="utf-8"><title>💮💮 deuxfleurs - Gestion des risques</title><link rel="stylesheet" href="/css/main.css"><meta name="viewport" content="width=device-width, initial-scale=1.0"></head><body><aside><header><a class="mobile_inline" id="menu" href="#"><svg viewBox="0 0 100 80" width="40" height="40"><rect width="100" height="20"></rect><rect y="30" width="100" height="20"></rect><rect y="60" width="100" height="20"></rect></svg></a><h1><a href="/">deuxfleurs</a></h1><nav class="computer_block"><section class="center"><img alt="emoji fleur" src="/img/flower.svg" width="40"> <img alt="emoji fleur" src="/img/flower.svg" width="40"></section><ul><li><a href="https://plume.deuxfleurs.fr/timeline/1">Actualités</a></li><li><a href="https://man.deuxfleurs.fr">Wiki</a></li><li><a href="https://guichet.deuxfleurs.fr">Mon compte</a></li></ul><hr><ul><li><a href="/CGU.html">CGU</a></li><li><a class="selected" href="/Gestion des risques.html">Gestion des risques</a></li><li><a href="/Mentions légales.html">Mentions légales</a></li><li><a href="/Sources.html">Sources</a></li></ul></nav></header></aside><main><section><h1>Gestion des risques</h1><p>Un risque se définit par la combinaison d'un danger, c'est à dire un évènement redouté, et sa probabilité d'occurence.
|
||||
La gestion des risques consiste à minimiser les risques en les évaluant et en mettant en place des solutions pour réduire leur impact.</p><h2>🧰 Risques matériels</h2><h3>Panne de composants informatiques</h3><p><b>Définition du risque</b>: Un serveur est composé d'un ensemble de pièces avec une durée de vie limitée. La panne d'une de ces pièces cause une interruption de service et possiblement une perte de données (comme dans le cas d'un disque dur par exemple). La probabilité de ces pannes est importante car certains composants ont une durée de vie limité, comme les disques durs, et de plus nous utilisons du matériel reconditionné qui a donc déjà été utilisé.</p><p><b>Mesure mise en place</b>: Nous avons à disposition des pièces de rechange pour pouvoir réparer rapidement nos serveurs. De plus, nous avons en permanence plusieurs machines en production de sorte que lorsque l'une d'elle tombe en panne, les services qu'elle gérait sont automatiquement basculés sur les autres machines fonctionnelles. Les données sont répliquées sur 3 disques durs différents, de sorte que si un disque dur tombe en panne, cette dernière est toujours disponible sur 2 autres disques.</p><h3>Bug logiciel</h3><p><b>Définition du risque</b>: Un bug logiciel peut rendre un service indisponible voire impliquer une perte de données. Cette indisponibilité et cette perte de donnée, contrairement à une panne matériel, peut se propager à l'ensemble de nos serveurs.</p><p><b>Mesure mise en place</b>: Les données, en plus d'être répliquées automatiquement, sont périodiquement sauvegardées via un logiciel indépendant sur une période d'au moins 2 mois sur un site distant (Suresnes), de sorte que le logiciel qui fournisse le service n'ait pas accès aux données de sauvegardes et ne puisse donc pas les effacer. Les services quant à eux sont définis déclarativement, dans chaque modification est archivée, de sorte qu'il est possible de revenir sur une version antérieure du service qui soit stable.</p><h3>Panne du réseau électrique ou internet</h3><p><b>Définition du risque</b>: Nous faisons appel à des prestataires externe pour l'électricité (eg. EDF) et la connexion Internet (eg. Free). Lors de travaux dans la rue, de tension sur le réseau (eg. froid ou confinement), ou simplement d'erreur de gestion, ces réseaux peuvent être coupés localement ou au niveau national. En résulte une indisponibilité des services pendant la coupure.</p><p><b>Mesure mise en place</b>: Notre infrastructure est répartie sur des zones éloignées géographiquement (aujourd'hui Rennes et Orsay), de sorte qu'une panne locale ne nécessitera que de migrer les services d'une zone à l'autre. Pour le cas d'une panne au niveau national, nous acceptons ce risque : il est très faible et, la plupart du temps, le service est rétabli en quelques heures.</p><h3>Panne des autres prestataires et tiers-parties</h3><p> <b>Définition du risque</b>: Deuxfleurs fait appel à un certains nombre de prestataires et tiers parties pour fournir ses services : bureau d'enregistrement DNS (Gandi), Hébergeur DNS (Gandi), certificats X.509 (Let's Encrypt), système d'exploitation (NixOS, Debian), logiciels (Docker Hub, Github, etc.). La panne ou le blocage par une de ces tiers-parties impacteraient les services de Deuxfleurs.</p><p><b>Mesure mise en place</b>: Nous essayons de limiter le nombre de prestataires que nous utilisons et évitons de verrouiller fortement nos choix technologiques vis à vis d'un fournisseur particulier.
|
||||
En dehors de ces points, nous acceptons ces risques.</p><h2>😵 Risques humains</h2><h3>Erreur d'administration</h3><p><b>Définition du risque</b>: Une erreur d'administration des services peut aboutir à une interruption de services et à une perte de données sur l'ensemble de nos serveurs. Elle peut également générer beaucoup de stress pour la personne en charge de l'administration.</p><p><b>Mesure mise en place</b>: Les données, en plus d'être répliquées automatiquement, sont périodiquement sauvegardées via un logiciel indépendant sur une période d'au moins 2 mois sur un site distant (Suresnes), de sorte que le logiciel qui fournisse le service n'ait pas accès aux données de sauvegardes et ne puisse donc pas les effacer. Les services quant à eux sont définis déclarativement, dans chaque modification est archivée, de sorte qu'il est possible de revenir sur une version antérieure du service qui soit stable. En cas d'erreur, la personne en charge de l'administration doit demander un accompagnement ou un relai pour limiter les risques d'aggravement de la situation et ne pas avoir à supporter cette situation stressante seule.</p><h3>Absence d'astreinte</h3><p><b>Définition du risque</b>: Que ce soit dans les datacenters au niveau matériel, ou dans les services informatiques, au niveau logiciel, de nombreuses organisations mettent en place des astreintes.
|
||||
Autrement dit, une ou plusieurs personnes identifiées doivent se rendre disponible sur des périodes données pour pouvoir intervenenir rapidement sur les serveurs.
|
||||
Dans le cas de Deuxfleurs, une astreinte empêcherait une personne de quitter son domicile pour des vacances ou même rendre visite à sa famille !</p><p><b>Mesure mise en place</b>: Nous faisons en sorte d'avoir des serveurs chez des membres différents et d'avoir plusieurs personnes en mesure de réaliser une même opération de maintenance.
|
||||
Si un problème devait arriver pendant l'absence de la personne concernée, un autre membre devrait pouvoir prendre le relai dans les heures ou les jours qui viennent, par exemple en migrant les services chez lui ou en le réparant à distance.</p><h3>Perte d'expertise</h3><p><b>Définition du risque</b>: L'infrastructure que nous avons déployée demande des connaissances avancées en informatique détenues par une fraction des membres de l'association. Si cette fraction venait à quitter l'association, la maintenance de ses services pourrait ne plus être réalisée par les membres restants, mettant en péril sa pérennité.</p><p><b>Mesure mise en place</b>: Nous essayons d'avoir toujours au moins deux personnes en mesure de réaliser une tâche. Nous essayons de documenter et standardiser notre infrastructure.</p><h3>Risques juridiques</h3><p><b>Définition du risque</b>: Deuxfleurs pourrait enfreindre la loi et voir sa pérennité engagée en cas de procès.</p><p><b>Mesure mise en place</b>: Nous faisons une veille juridique concernant les hébergeurs. Nous mitigeons aussi ce risque via la co-optation qui permet de contrôler notre croissance et les personnes qui nous rejoignent.</p><h2>👿 Malveillance</h2><h3>Attaque informatique</h3><p><b>Définition du risque</b>: Une attaque informatique, venant d'un·e administrateur·ice ou d'une personne extérieure, peut aboutir à l'indisponibilité de nos services, à une perte de données, mais aussi à la fuite de ces dernières.</p><p><b>Mesure mise en place</b>: Pour se protéger d'un·e administrateur·ice malveillant·e, le groupe d'administrateur·ices existant ne recrute que de nouvelles personnes sur cooptation et après avoir jugé cette personne de confiance. Nous prévoyions également de chiffrer de plus en plus de données côté client, de sorte qu'une personne en charge de l'administration ne soit pas en mesure de lire le contenu stocké sur les serveurs. Pour se protéger d'une personne extérieure, nous maintenons notre système à jour et avons entamé une démarche de défense en profondeur.</p><h3>Vol du matériel</h3><p><b>Définition du risque</b>: Une personne entrant par effraction chez un de nos membres pourrait voler les ordinateurs. Cet évènement peut impacter la disponibilité de nos services, l'intégrité de nos données, mais aussi la confidentialité de ces dernières.</p><p><b>Mesure mise en place</b>: Nous acceptons ce risque pour le moment. Le chiffrement côté client, pour les services le supportant, permet de protéger la confidentialité des données. Nous prévoyions à terme de chiffrer les disques durs à froid en plus.</p><h3>Abus des services</h3><p><b>Définition du risque</b>: Une personne ayant des accès au service, où se les aillant fait voler, peut opérer un déni de service sur notre infrastructure, ou alors nuire à la réputation de notre service sur un réseau fédéré (eg. spam via email). Cela entraine une indisponibilité des services et/ou une dégradation plus ou moins durable de la qualité de ces derniers.</p><p><b>Mesure mise en place</b>: Nous mitigeons actuellement ce risque via la cooptation, où nous faisons confiance aux nouveaux membres et les invitons à bien gérer leurs identifiants. </p></section></main><script>(_ => {
|
||||
const hamburger = document.getElementById('menu')
|
||||
hamburger.onclick = _ => {
|
||||
const nav = document.querySelector('body > aside > header > nav')
|
||||
console.log(nav.style.display)
|
||||
nav.style.display = nav.style.display != 'block' ? 'block' : 'none'
|
||||
}
|
||||
})()</script></body></html>
|
File diff suppressed because one or more lines are too long
|
@ -1,38 +0,0 @@
|
|||
<!DOCTYPE html><html lang="fr"><head><meta charset="utf-8"><title>💮💮 deuxfleurs - Sources</title><link rel="stylesheet" href="/css/main.css"><meta name="viewport" content="width=device-width, initial-scale=1.0"></head><body><aside><header><a class="mobile_inline" id="menu" href="#"><svg viewBox="0 0 100 80" width="40" height="40"><rect width="100" height="20"></rect><rect y="30" width="100" height="20"></rect><rect y="60" width="100" height="20"></rect></svg></a><h1><a href="/">deuxfleurs</a></h1><nav class="computer_block"><section class="center"><img alt="emoji fleur" src="/img/flower.svg" width="40"> <img alt="emoji fleur" src="/img/flower.svg" width="40"></section><ul><li><a href="https://plume.deuxfleurs.fr/timeline/1">Actualités</a></li><li><a href="https://man.deuxfleurs.fr">Wiki</a></li><li><a href="https://guichet.deuxfleurs.fr">Mon compte</a></li></ul><hr><ul><li><a href="/CGU.html">CGU</a></li><li><a href="/Gestion des risques.html">Gestion des risques</a></li><li><a href="/Mentions légales.html">Mentions légales</a></li><li><a class="selected" href="/Sources.html">Sources</a></li></ul></nav></header></aside><main><section><h1>Accéder aux sources des logiciels utilisés</h1><p>Deuxfleurs utilise exclusivement des logiciels libres dans le cadre de son activité. Vous pouvez retrouver ici la liste des sources des logiciels utilisés.</p><ul>
|
||||
<li><a href="https://packages.debian.org/">Debian</a></li>
|
||||
<li><a href="https://github.com/NixOS">NixOS</a></li>
|
||||
<li><a href="https://github.com/hashicorp/nomad">Nomad</a></li>
|
||||
<li><a href="https://github.com/hashicorp/consul/">Consul</a></li>
|
||||
<li><a href="https://git.deuxfleurs.fr/Deuxfleurs/garage">Garage</a></li>
|
||||
<li><a href="https://git.deuxfleurs.fr/Deuxfleurs/tricot">Tricot</a></li>
|
||||
<li><a href="https://git.deuxfleurs.fr/Deuxfleurs/bottin/">Bottin</a></li>
|
||||
<li><a href="https://git.deuxfleurs.fr/Deuxfleurs/guichet/">Guichet</a></li>
|
||||
<li><a href="https://git.deuxfleurs.fr/Deuxfleurs/diplonat/">Diplonat</a></li>
|
||||
<li><a href="https://github.com/sorintlab/stolon">Stolon</a></li>
|
||||
<li><a href="https://github.com/moby/moby">Docker</a></li>
|
||||
<li><a href="https://github.com/ansible/ansible">Ansible</a></li>
|
||||
<li><a href="https://github.com/harness/drone">Drone</a></li>
|
||||
<li><a href="https://github.com/restic/restic">Restic</a></li>
|
||||
<li><a href="https://github.com/xwiki-labs/cryptpad">Cryptpad</a></li>
|
||||
<li><a href="https://github.com/inverse-inc/sogo">Sogo</a></li>
|
||||
<li><a href="git.deuxfleurs.fr/Deuxfleurs/alps">alps</a></li>
|
||||
<li><a href="https://github.com/matrix-org/synapse">Synapse</a></li>
|
||||
<li><a href="https://github.com/vector-im/element-web">Element</a></li>
|
||||
<li><a href="https://github.com/jitsi">Jitsi</a></li>
|
||||
<li><a href="https://github.com/Plume-org/Plume">Plume</a></li>
|
||||
<li><a href="https://github.com/FiloSottile/age">age</a></li>
|
||||
<li><a href="https://github.com/minio/minio">Minio</a></li>
|
||||
<li><a href="https://git.proxmox.com/">Proxmox</a></li>
|
||||
<li><a href="https://github.com/grafana/grafana">Grafana</a></li>
|
||||
<li><a href="https://github.com/prometheus/prometheus">Prometheus</a></li>
|
||||
<li><a href="https://git.deuxfleurs.fr/Deuxfleurs/infrastructure">Infra (legacy)</a></li>
|
||||
<li><a href="git.deuxfleurs.fr/Deuxfleurs/nixcfg">Infra (next)</a></li>
|
||||
</ul>
|
||||
</section></main><script>(_ => {
|
||||
const hamburger = document.getElementById('menu')
|
||||
hamburger.onclick = _ => {
|
||||
const nav = document.querySelector('body > aside > header > nav')
|
||||
console.log(nav.style.display)
|
||||
nav.style.display = nav.style.display != 'block' ? 'block' : 'none'
|
||||
}
|
||||
})()</script></body></html>
|
|
@ -591,5 +591,3 @@ _ ` ^ ¨ · _ - " ` * - ; - _
|
|||
<script src="script-bon.js"></script>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
||||
|
|
|
@ -6,13 +6,7 @@ main {
|
|||
grid-template-columns: [col-start] repeat(12, calc(100% / 12) [col-sep]);
|
||||
grid-template-rows:
|
||||
[row-start] auto [jardin-end]
|
||||
repeat(3,
|
||||
var(--big_margin)
|
||||
[title-start] auto [title-end]
|
||||
var(--med_margin)
|
||||
[illu-start] auto [illu-end] auto [illu-extended-end]
|
||||
var(--med_margin)
|
||||
[txt-start] auto [txt-end])
|
||||
repeat(3, var(--big_margin) [title-start] auto [title-end] var(--med_margin) [illu-start] auto [illu-end] auto [illu-extended-end] var(--med_margin) [txt-start] auto [txt-end])
|
||||
var(--big_margin)
|
||||
[title-start-contact] auto [title-end-contact]
|
||||
var(--med_margin)
|
||||
|
@ -37,6 +31,7 @@ div#jardin p{
|
|||
h2#infras {
|
||||
background-color: var(--infras);
|
||||
grid-area: title-start 1 / col-sep 1 / title-end 1 / col-sep 12;
|
||||
padding-bottom: 10px; /* Ajoutez de l'espace en dessous du texte */
|
||||
}
|
||||
|
||||
div#rennes {
|
||||
|
@ -70,6 +65,8 @@ section#liste_outils{
|
|||
|
||||
section#liste_outils > a > div > p {
|
||||
text-align: center;
|
||||
text-decoration: underline;
|
||||
color: darkgreen;
|
||||
}
|
||||
|
||||
section#liste_outils > a {
|
||||
|
@ -126,7 +123,8 @@ div#calendrier{
|
|||
overflow: hidden;
|
||||
}
|
||||
|
||||
.mois_actuel, .mois_suivant{
|
||||
.mois_actuel,
|
||||
.mois_suivant {
|
||||
overflow: hidden;
|
||||
}
|
||||
|
||||
|
@ -146,7 +144,8 @@ section#liste_valeurs{
|
|||
var(--small_margin)
|
||||
[line2-start] auto [line2-end]
|
||||
var(--small_margin)
|
||||
[suivre-start] auto [suivre-end];
|
||||
[suivre-start] auto [suivre-end]
|
||||
;
|
||||
}
|
||||
|
||||
p#coop {
|
||||
|
@ -176,7 +175,10 @@ p#suivre {
|
|||
text-align: center;
|
||||
}
|
||||
|
||||
#coop, #autonomie, #solidarite, #liberte{
|
||||
#coop,
|
||||
#autonomie,
|
||||
#solidarite,
|
||||
#liberte {
|
||||
padding: 2rem;
|
||||
border: 1px dashed black;
|
||||
text-align: center;
|
||||
|
@ -198,7 +200,6 @@ div#ordinateur {
|
|||
grid-area: illu-start 2 / col-start / illu-end 2 / col-sep 7;
|
||||
}
|
||||
|
||||
|
||||
div#discussion {
|
||||
background-color: var(--lightgrey);
|
||||
grid-area: line1-start / col-start / line1-end / col-mid-left;
|
||||
|
@ -222,7 +223,6 @@ div#emails {
|
|||
div#collaboration {
|
||||
background-color: var(--lightgrey);
|
||||
grid-area: line2-start / col-mid-right / line2-end / col-end;
|
||||
|
||||
}
|
||||
|
||||
div#blog {
|
||||
|
@ -230,7 +230,6 @@ div#blog {
|
|||
grid-area: line3-start / col-mid-right / line3-end / col-end;
|
||||
}
|
||||
|
||||
|
||||
/*GESTION DES MEDIA QUERIES*/
|
||||
|
||||
/*Tablettes et petits ordinateurs*/
|
||||
|
@ -261,14 +260,16 @@ div#blog {
|
|||
margin-left: 0.5rem;
|
||||
}
|
||||
|
||||
div#rennes, div#orsay{
|
||||
div#rennes,
|
||||
div#orsay {
|
||||
border: 1px solid black;
|
||||
border-radius: 5px;
|
||||
}
|
||||
|
||||
div#rennes pre.center, div#orsay pre.center{
|
||||
div#rennes pre.center,
|
||||
div#orsay pre.center {
|
||||
margin-top: -5px;
|
||||
margin-bottom: -5px
|
||||
margin-bottom: -5px;
|
||||
}
|
||||
|
||||
div#orsay pre.center {
|
||||
|
@ -305,7 +306,6 @@ div#blog {
|
|||
margin-top: var(--med_margin);
|
||||
}
|
||||
|
||||
|
||||
section#liste_outils {
|
||||
display: grid;
|
||||
grid-template-columns: 1fr 1fr 1fr;
|
||||
|
@ -339,7 +339,6 @@ div#blog {
|
|||
div#collaboration {
|
||||
background-color: var(--lightgrey);
|
||||
grid-area: line2-start / col-tiers2-start / line2-end / col-tiers2-end;
|
||||
|
||||
}
|
||||
|
||||
div#blog {
|
||||
|
@ -358,7 +357,8 @@ div#blog {
|
|||
justify-content: center;
|
||||
}
|
||||
|
||||
#mois_actuel, #mois_suivant{
|
||||
#mois_actuel,
|
||||
#mois_suivant {
|
||||
overflow: hidden;
|
||||
}
|
||||
|
||||
|
@ -366,10 +366,8 @@ div#blog {
|
|||
margin-bottom: 0px;
|
||||
margin-right: 2rem;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
|
||||
/*Smartphones*/
|
||||
@media (max-width: 800px) {
|
||||
h2#infras {
|
||||
|
@ -446,7 +444,9 @@ div#blog {
|
|||
font-size: 0.95rem;
|
||||
}
|
||||
|
||||
#txt_infras, #txt_outils, #txt_connaissance{
|
||||
#txt_infras,
|
||||
#txt_outils,
|
||||
#txt_connaissance {
|
||||
text-align: left;
|
||||
hyphens: none;
|
||||
margin-top: 0;
|
||||
|
@ -499,7 +499,10 @@ div#blog {
|
|||
padding: 0px;
|
||||
}
|
||||
|
||||
#coop, #autonomie, #solidarite, #liberte{
|
||||
#coop,
|
||||
#autonomie,
|
||||
#solidarite,
|
||||
#liberte {
|
||||
padding: 1rem;
|
||||
margin: 0px;
|
||||
}
|
||||
|
@ -533,7 +536,6 @@ div#blog {
|
|||
text-align: center;
|
||||
margin-bottom: 12rem;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
/* En vrac */
|
||||
|
@ -545,15 +547,11 @@ div#calendrier > pre.center{
|
|||
margin-bottom: 1rem;
|
||||
}
|
||||
|
||||
#mois_actuel, #mois_suivant{
|
||||
#mois_actuel,
|
||||
#mois_suivant {
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.highlight{
|
||||
color: var(--day-highlight-color);
|
||||
background-color: var(--day-highlight-bg);
|
||||
}
|
||||
|
||||
#txt_connaissance li {
|
||||
margin-bottom: 1rem;
|
||||
}
|
||||
|
@ -562,8 +560,9 @@ div#calendrier > pre.center{
|
|||
margin-top: 0px;
|
||||
}
|
||||
|
||||
|
||||
#txt_infras, #txt_outils, #txt_connaissance{
|
||||
#txt_infras,
|
||||
#txt_outils,
|
||||
#txt_connaissance {
|
||||
line-height: 1.3rem;
|
||||
text-align: justify;
|
||||
text-justify: inter-character;
|
||||
|
|
|
@ -29,10 +29,14 @@
|
|||
--calendrier: darkkhaki;
|
||||
--footer: deeppink;
|
||||
--lightgrey: lightgrey;*/
|
||||
|
||||
}
|
||||
|
||||
/* PAR DEFAUT */
|
||||
|
||||
h1 > .decoration:last-of-type:before, h2 > .decoration:last-of-type:before{
|
||||
content: '\A____________________________________\A""""""""""""""""""""""""""""""""""""';
|
||||
}
|
||||
|
||||
html, body, main {
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
|
@ -59,17 +63,12 @@ a{
|
|||
color: darkgreen;
|
||||
}
|
||||
|
||||
|
||||
nav ul {
|
||||
list-style: none;
|
||||
padding: 0px;
|
||||
margin: 0px;
|
||||
}
|
||||
|
||||
h1:after, h2:after{
|
||||
content:'\A___________________________________\A"""""""""""""""""""""""""""""""""""';
|
||||
}
|
||||
|
||||
h2, h1 {
|
||||
font-size: 1rem;
|
||||
font-weight: normal;
|
||||
|
@ -92,13 +91,25 @@ img{
|
|||
overflow: hidden;
|
||||
}
|
||||
|
||||
.highlight {
|
||||
color: var(--day-highlight-color);
|
||||
background-color: var(--day-highlight-bg);
|
||||
}
|
||||
|
||||
.underline {
|
||||
text-decoration-line: underline;
|
||||
}
|
||||
|
||||
/*GESTION DE LA GRILLE DU DOCUMENT*/
|
||||
div#container {
|
||||
display: grid;
|
||||
grid-template-columns: [main-col-start] repeat(12, calc(100% / 12) [main-col-sep]);
|
||||
grid-template-rows:
|
||||
[main-row-debut] var(--med_margin) [header-start] auto [header-end] var(--big_margin) [core-start] auto [main-row-fin]
|
||||
var(--big_margin)
|
||||
[main-row-debut] var(--med_margin)
|
||||
[header-start] auto
|
||||
[header-end] var(--big_margin)
|
||||
[core-start] auto
|
||||
[main-row-fin] var(--big_margin)
|
||||
[footer-start] auto [footer-end]
|
||||
;
|
||||
}
|
||||
|
@ -106,6 +117,7 @@ div#container{
|
|||
/* EN-TETE */
|
||||
header {
|
||||
grid-area: header-start / main-col-sep 1 / header-end / main-col-sep 12;
|
||||
z-index: 1; /* Pour le mettre au dessus de l'illustration jardin et que l'on puisse sélectionner son contenu */
|
||||
}
|
||||
|
||||
/* PIED DE PAGE */
|
||||
|
@ -116,7 +128,7 @@ footer {
|
|||
|
||||
#liens {
|
||||
text-align: center;
|
||||
margin-bottom: var(--med_margin)
|
||||
margin-bottom: var(--med_margin);
|
||||
}
|
||||
|
||||
/* MENU */
|
||||
|
@ -190,7 +202,8 @@ pre.center > a{
|
|||
/* RESPONSIVE */
|
||||
/* Tablettes */
|
||||
@media (max-width: 1500px) and (min-width: 801px) {
|
||||
h2, h1{
|
||||
h2,
|
||||
h1 {
|
||||
font-size: 1rem;
|
||||
font-weight: normal;
|
||||
margin: 0px;
|
||||
|
@ -209,15 +222,15 @@ pre.center > a{
|
|||
--small_margin: 5px;
|
||||
}
|
||||
|
||||
h1:before, h1:after{
|
||||
content: '';
|
||||
h1 > .decoration:last-of-type:before {
|
||||
content: "";
|
||||
}
|
||||
|
||||
h2:before{
|
||||
h2 > .decoration:first-of-type:before{
|
||||
content: '______________________________________________________________________\A""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""\A* ';
|
||||
}
|
||||
|
||||
h2:after{
|
||||
h2 > .decoration:last-of-type:before{
|
||||
content: ' *\A______________________________________________________________________\A""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""';
|
||||
}
|
||||
|
||||
|
@ -231,7 +244,6 @@ pre.center > a{
|
|||
white-space: pre;
|
||||
overflow: hidden;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
/* THEME SOMBRE */
|
||||
|
@ -259,5 +271,7 @@ pre.center > a{
|
|||
div#ronce, #coop, #autonomie, #solidarite, #liberte, nav#menu, div#rennes, div#orsay {
|
||||
border-color: var(--txt-night);
|
||||
}
|
||||
section#liste_outils > a > div > p:nth-child(n){
|
||||
color: var(--txt-night);
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
@ -16,5 +16,3 @@ main {
|
|||
grid-area: core-start / main-col-start / main-row-fin / main-col-sep 12;
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
|
|
|
@ -81,3 +81,37 @@
|
|||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 6 février 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/infra">Réunion mensuelle d'infrastructure</a> en ligne, <span class="highlight">le 21 février 2024 à 20h00</span>.<br>Point mensuel en visioconférence où l'on aborde toutes les questions techniques qui méritent notre attention, concernant notre infrastructure ou nos services.</li>
|
||||
<li role="none"><a href="#">Permanence associative autour du Libre</a> au Café Citoyen à Lille, <span class="highlight">le 27 février 2024 à 19h30</span>.<br>La permanence associative autour du Libre est une manifestation conviviale, ouverte à toutes et tous, organisée le dernier mardi de chaque mois, et regroupant les collectifs Chtinux, Raoull, Deuxfleurs, Mycélium, CLX et Cliss XXI.</li>
|
||||
<!-- Mars 2024 -->
|
||||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 5 mars 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li role="none"><a href="https://bbb.paquerette.eu/b/dom-67q-irl-nfc">Réunion mensuelle du collectif CHATONS</a> en ligne, <span class="highlight">le 12 mars 2024 à 20h00</span>.<br>Une fois par mois a lieu une réunion entre les membres du collectif <a href=https://www.chatons.org/>CHATONS</a>.</li>
|
||||
<li role="none"><a href="#">Barcamp Interne</a> au Couvent des Clarisses à Roubaix, <span class="highlight">le 15, 16 et 17 mars</span>.<br> Les membres de Deuxfleurs prennent le temps de se retrouver et de discuter de l'association. N'hésitez pas à nous contacter pour passer nous voir le samedi soir.</li>
|
||||
<!-- Avril 2024 -->
|
||||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 2 avril 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/infra">Réunion mensuelle d'infrastructure</a> en ligne, <span class="highlight">le 17 avril 2024 à 20h00</span>.<br>Point mensuel en visioconférence où l'on aborde toutes les questions techniques qui méritent notre attention, concernant notre infrastructure ou nos services.</li>
|
||||
<li role="none"><a href="#">Permanence associative autour du Libre</a> au Café Citoyen à Lille, <span class="highlight">le 30 avril 2024 à 19h30</span>.<br> La permanence associative autour du Libre est une manifestation conviviale, ouverte à toutes et tous, organisée le dernier mardi de chaque mois, et regroupant les collectifs Chtinux, Raoull, Deuxfleurs, Mycélium, CLX et Cliss XXI.</li>
|
||||
|
||||
|
||||
<!-- Mai 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 7 mai 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/infra">Réunion mensuelle d'infrastructure</a> en ligne, <span class="highlight">le 22 mai 2024 à 20h00</span>.<br>Point mensuel en visioconférence où l'on aborde toutes les questions techniques qui méritent notre attention, concernant notre infrastructure ou nos services.</li>
|
||||
<li><a href="https://cis.cnrs.fr/netgouv24/">#NetGouv24</a> à Paris, <span class="highlight">le 29 mai 2024</span>.<br>Première conférence annuelle du groupe de travail Gouvernance et Régulation d'Internet. L'ensemble de la communauté scientifique intéressée par ces sujets s'y retrouvera pour une journée de présentations et de discussion.</li>
|
||||
<li><a href="https://passageenseine.fr/">Pas Sage en Seine</a> à Choisy-le-Roi, <span class="highlight">le 31 mai, 1 et 2 juin</span>.<br>Festival annuel gratuit dédié au logiciel libre. De nombreuses présentations sur des sujets techniques ou non y sont faites.</li>
|
||||
<!-- Juin 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 4 juin 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/infra">Réunion d'infrastructure</a> en ligne, <span class="highlight">le 5 juin 2024 à 19h15</span>.<br>Point en visioconférence sur les nouveaux sites géographiques à mettre en place pour pouvoir mieux résister aux pannes.</li>
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/infra">Réunion mensuelle d'infrastructure</a> en ligne, <span class="highlight">le 19 juin 2024 à 20h00</span>.<br>Point mensuel en visioconférence où l'on aborde toutes les questions techniques qui méritent notre attention, concernant notre infrastructure ou nos services.</li>
|
||||
<li><em>Barcamp Interne</em> en Auvergne, <span class="highlight">les 21, 22 et 23 juin</span>.<br> Les membres de Deuxfleurs prennent le temps de se retrouver et de discuter de l'association.</li>
|
||||
<!-- Juillet 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 2 juillet 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li><a href="https://www.agendadulibre.org/events/30240">Quadrapéro</a>, au Garage de la Quadrature du Net à Paris, <span class="highlight">le 5 juillet 2024 à 19h00</span>.<br>Apéritif convivial pour discuter des divers enjeux en cours autour des droits et libertés numériques, en présence de membres de la Quadrature du Net et de bien autres intéressés. Vous y verrez Vincent.</li>
|
||||
<li><a href="https://bbb.paquerette.eu/b/dom-67q-irl-nfc">Réunion mensuelle du collectif CHATONS</a> en ligne, <span class="highlight">le 9 juillet 2024 à 20h00</span>.<br>Une fois par mois a lieu une réunion entre les membres du collectif <a href=https://www.chatons.org/>CHATONS</a>, à laquelle nous participons.</li>
|
||||
<li><a href="https://libreto.sans-nuage.fr/campchatons2024/">Camp CHATONS</a> à Sévérac, <span class="highlight">du 11 au 15 juillet</span>.<br>Chaque année, les membres du collectif CHATONS se réunissent en présentiel pour aborder les grands sujets à son propos et partager des moments conviviaux. Vous y verrez Adrien.</li>
|
||||
<li><a href="#">Permanence associative autour du Libre</a> au Café Citoyen à Lille, <span class="highlight">le 30 juillet 2024 à 19h30</span>.<br>La permanence associative autour du Libre est une manifestation conviviale, ouverte à toutes et tous, organisée le dernier mardi de chaque mois, et regroupant les collectifs Chtinux, Raoull, Deuxfleurs, Mycélium, CLX et Cliss XXI.</li>
|
||||
|
||||
<!-- Août 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle « au coin du feu »</a> en ligne, <span class="highlight">le 6 août 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<!-- Septembre 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle « au coin du feu »</a> en ligne, <span class="highlight">le 3 septembre 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li><a href="https://www.agendadulibre.org/events/30486">Numérique libre à la Braderie de Lille</a> au village associatif du Café Citoyen, <span class="highlight">du 14 septembre 2024 à 10h au 15 à 18h</span>.<br>Le spot le plus cool durant la Braderie de Lille, c'est le Café Citoyen (ses spectacles qualitatifs y surpassent de loin les articles vendus trop chers par les brocanteurs que vous trouverez ailleurs). Le spot le plus cool au Café Citoyen, c'est son village associatif. Mais alors la cerise sur le gâteau, c'est sans doute le stand sur les libertés numériques tenu par les collectifs de Chtinux (Raoull, Deuxfleurs, Mycélium, CLX et Cliss XXI...). Venez dire bonjour, vous serez bien reçu⋅e !</li>
|
||||
<li><a href="https://fete.humanite.fr/">Fête de l'Humanité</a> à la base 217 à Bretigny-sur-Orge, <span class="highlight">le 14 et 15 septembre 2024</span>.<br>Plus qu'un festival de musique, la fête de l'Humanité est un rendez-vous important des forces militantes sur un peu tous les sujets. Si vous souhaitez y rencontrer Vincent, n'hésitez pas à nous contacter par courriel auparavant pour que l'on s'organise et que l'on ne se rate pas.</li>
|
||||
<li><a href="https://www.agendadulibre.org/events/30485">Permanence associative autour du Libre</a> au Café Citoyen à Lille, <span class="highlight">le 24 septembre 2024 à 19h30</span>.<br>La permanence associative autour du Libre est une manifestation conviviale, ouverte à toutes et tous, organisée le dernier mardi de chaque mois, et regroupant les collectifs de Chtinux (Raoull, Deuxfleurs, Mycélium, CLX, Cliss XXI...).</li>
|
||||
|
|
|
@ -46,8 +46,8 @@
|
|||
<body>
|
||||
|
||||
<nav role="navigation" aria-label="menu d'accès" id="menu">
|
||||
<ul aria-label="menu principal" role="menubar" aria-orientation="vertical">
|
||||
<li role="none">
|
||||
<ul aria-label="menu principal" role="menubar">
|
||||
<li>
|
||||
<a href="https://guichet.deuxfleurs.fr/" role="menuitem" aria-label="compte" class="icone">
|
||||
<pre aria-hidden="true">
|
||||
(COMPTE)
|
||||
|
@ -63,7 +63,7 @@
|
|||
||_||__| </pre>
|
||||
</a>
|
||||
</li>
|
||||
<li role="none">
|
||||
<li>
|
||||
<a href="https://guide.deuxfleurs.fr/" role="menuitem" aria-label="wiki" class="icone">
|
||||
<pre aria-hidden="true">
|
||||
((((((()
|
||||
|
@ -79,7 +79,7 @@
|
|||
|______| </pre>
|
||||
</a>
|
||||
</li>
|
||||
<li role="none">
|
||||
<li>
|
||||
<a href="https://plume.deuxfleurs.fr/" role="menuitem" aria-label="blog" class="icone">
|
||||
<pre aria-hidden="true">
|
||||
|¨¨¨¨|
|
||||
|
@ -489,7 +489,7 @@
|
|||
</div>
|
||||
<p>Fabriquons un internet convivial ⤵</p>
|
||||
</div>
|
||||
<h2 id="infras">Avec nos propres infrastructures</h2>
|
||||
<h2 id="infras"><span class="decoration" aria-hidden="true"></span>Avec nos propres infrastructures<span class="decoration" aria-hidden="true"></span></h2>
|
||||
<div id="rennes" role="img" aria-label="illustration de trois serveurs informatiques rangés dans la bibliothèque d'un salon">
|
||||
<!--diode qui clignote ?-->
|
||||
<pre class="center">/¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨\
|
||||
|
@ -721,8 +721,8 @@
|
|||
\___________`_______________________________________________________`___________/</pre>
|
||||
</div>
|
||||
<p id="txt_infras" lang="fr">Nous fournissons des services numériques garantis "sans datacenter". À la place, nous utilisons moins d'une dizaine de vieux ordinateurs reconditionnés à nos domiciles qui peuvent fournir des services numériques à plusieurs dizaines de milliers de personnes. Actuellement ces ordinateurs sont situés à Orsay, Lille et Bruxelles. Nous avons également des machines à Suresnes pour les sauvegardes. <a href="https://guide.deuxfleurs.fr/infrastructures/">En savoir plus</a>. <br><br>Cette infrastructure atypique nous mène à développer de nouveaux logiciels libres. Si vous êtes dans la technique, vous pourriez être intéressé·e par <a href="https://garagehq.deuxfleurs.fr/">Garage</a>, <a href="https://bottin.eu">Bottin</a>, <a href="https://git.deuxfleurs.fr/lx/tricot">Tricot</a>, <a href="https://git.deuxfleurs.fr/Deuxfleurs/diplonat">Diplonat</a> et nos <a href="https://git.deuxfleurs.fr/Deuxfleurs">autres projets</a>.</p>
|
||||
<h2 id="outils">Avec nos services sobres</h2>
|
||||
<div id="ordinateur">
|
||||
<h2 id="outils"><span class="decoration" aria-hidden="true"></span>Avec nos services sobres<span class="decoration" aria-hidden="true"></span></h2>
|
||||
<div id="ordinateur" role="img" aria-label="image d'un ordinateur portable et deux fleurs à côté">
|
||||
<pre class="center" aria-hidden="true">
|
||||
|
||||
|
||||
|
@ -847,9 +847,9 @@
|
|||
<p>Envie de faire entendre votre voix sur Internet ? Nous mettons à disposition plusieurs outils de publication sur le web allant de la plateforme de blog partagée à la publication de sites web en autonomie.</p>
|
||||
<p>Prenez contact avec nous, nous vous aiderons à identifier les outils dont vous avez besoin et nous vous accompagnerons dans votre transition. ⤵</p>
|
||||
</div>
|
||||
<h2 id="valeurs">Avec des valeurs fortes</h2>
|
||||
<h2 id="valeurs"><span class="decoration" aria-hidden="true"></span>Avec des valeurs fortes<span class="decoration" aria-hidden="true"></span></h2>
|
||||
<div id="ronce">
|
||||
<img src="./ronce.webp" loading="lazy" alt="Deux personnages qui regardent et s'avancent vers une maison cabane perchée dans un arbre, illustrant notre envie d'un internet plus éthique.">
|
||||
<img loading="lazy" src="./ronce.webp" alt="Deux personnages qui regardent et s'avancent vers une maison cabane perchée dans un arbre, illustrant notre envie d'un internet plus éthique.">
|
||||
</div>
|
||||
<section id="liste_valeurs">
|
||||
<p id="coop">La coopération <span class="description">- eg. promouvoir l'intéropérabilité, les communs, le libre, et les formats de données ouverts </span></p>
|
||||
|
@ -858,22 +858,19 @@
|
|||
<p id="liberte">La liberté <span class="description">- eg. permettre à toutes et tous de s'exprimer, respecter la vie privée</span></p>
|
||||
<p id="suivre"><a href="https://plume.deuxfleurs.fr/timeline/1">Suivez notre actualité, réflexions et analyses sur notre blog Plume</a></p>
|
||||
</section>
|
||||
<h2 id="connaissance">Faisons connaissance</h2>
|
||||
<h2 id="connaissance"><span class="decoration" aria-hidden="true"></span>Faisons connaissance<span class="decoration" aria-hidden="true"></span></h2>
|
||||
<div id="txt_connaissance">
|
||||
<p lang="fr">L'accès à nos services est à prix libre. Nous estimons leur coût à 15€/an/compte pour leur maintien en fonctionnement et recommandons le double pour permettre à l'association de se développer. Il est conditionné par les ressources disponibles, à la fois matérielles et humaines.</p>
|
||||
<p lang="fr">Pour accéder à nos services ou simplement discuter avec nous, écrivez à <span style="text-decoration: underline;">coucou[@]deuxfleurs.fr</span>, rejoignez-nous sur le salon Matrix <span style="text-decoration: underline;">#deuxfleurs:deuxfleurs.fr</span> ou rencontrez-nous à : </p>
|
||||
<p lang="fr">Pour accéder à nos services ou simplement discuter avec nous, écrivez à <span class="highlight">coucou[@]deuxfleurs.fr</span>, rejoignez-nous sur le salon Matrix <span class="highlight">#deuxfleurs:deuxfleurs.fr</span> ou rencontrez-nous à : </p>
|
||||
<ul>
|
||||
<!-- L'historique des événements passés est sur evenements_passes.html -->
|
||||
<!-- Mars 2024 -->
|
||||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 5 mars 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li role="none"><a href="https://bbb.paquerette.eu/b/dom-67q-irl-nfc">Réunion mensuelle du collectif CHATONS</a> en ligne, <span class="highlight">le 12 mars 2024 à 20h00</span>.<br>Une fois par mois a lieu une réunion entre les membres du collectif <a href=https://www.chatons.org/>CHATONS</a>.</li>
|
||||
<li role="none"><a href="#">Barcamp Interne</a> au Couvent des Clarisses à Roubaix, <span class="highlight">le 15, 16 et 17 mars</span>.<br> Les membres de Deuxfleurs prennent le temps de se retrouver et de discuter de l'association. N'hésitez pas à nous contacter pour passer nous voir le samedi soir.</li>
|
||||
<!-- Avril 2024 -->
|
||||
<li role="none"><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle «au coin du feu»</a> en ligne, <span class="highlight">le 2 avril 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
|
||||
<li role="none"><a href="#">Permanence associative autour du Libre</a> au Café Citoyen à Lille, <span class="highlight">le 30 avril 2024 à 19h30</span>.<br> La permanence associative autour du Libre est une manifestation conviviale, ouverte à toutes et tous, organisée le dernier mardi de chaque mois, et regroupant les collectifs Chtinux, Raoull, Deuxfleurs, Mycélium, CLX et Cliss XXI.
|
||||
<!-- Octobre 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle « au coin du feu »</a> en ligne, <span class="highlight">le 1 octobre 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li><a href="https://forumdepartementaldessciences.fr/evenements/exposition-numerique-en-eaux-troubles/">Vernissage de l'exposition « Numérique en eaux troubles »</a>, au forum des sciences à Villeneuve-d'Ascq, <span class="highlight">le 11 octobre 2024 à 17h00</span>.<br>Inauguration de cette exposition abordant l'impact des divers aspects du numérique sur les ressources en eau. Parmis ses responsables scientifiques, vous y verrez Adrien.</li>
|
||||
<!-- Novembre 2024 -->
|
||||
<li><a href="https://jitsi.deuxfleurs.fr/r%C3%A9union_mensuelle_deuxfleurs">Réunion mensuelle « au coin du feu »</a> en ligne, <span class="highlight">le 5 novembre 2024 à 19h00</span>.<br>Une fois par mois nous organisons une réunion en ligne informelle. C'est le bon moment pour venir faire un coucou si vous voulez parler à des gens de vive voix numérique.</li>
|
||||
<li><a href="https://capitoledulibre.org">Capitole du libre</a>, à l'ENSEEIHT à Toulouse, <span class="highlight">le 16 et 17 novembre 2024</span>.<br>Conférence annuelle dédiée au logiciel libre et à sa communauté, ouverte à tout public, et ceci gratuitement. N'hésitez pas à venir discuter avec Vincent.</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
<div id="calendrier">
|
||||
<!--
|
||||
|
@ -882,40 +879,39 @@
|
|||
-->
|
||||
<div id="mois_actuel" role="img" aria-label="calendrier de nos jours de permanence prévus pour ce mois-ci">
|
||||
<pre aria-hidden="true">.——————————————————————————————————————.
|
||||
| CALENDRIER MARS 2024 |
|
||||
| CALENDRIER OCTOBRE 2024 |
|
||||
|——————————————————————————————————————|
|
||||
| ———— ———— ———— ———— ———— ———— |
|
||||
| |<span class="highlight"> 01 </span>| 02 | 03 | 04 | 05 | 06 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 07 | 08 | 09 | 10 |<span class="highlight"> 11 </span>| 12 | 13 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 14 | 15 | 16 | 17 | 18 | 19 | 20 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 21 | 22 | 23 | 24 | 25 | 26 | 27 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 28 | 29 | 30 | 31 | |
|
||||
| ———— ———— ———— ———— |
|
||||
|______________________________________|</pre>
|
||||
</div>
|
||||
<div id="mois_suivant" role="img" aria-label="calendrier de nos jours de permanence prévus pour le mois prochain">
|
||||
<pre aria-hidden="true">.——————————————————————————————————————.
|
||||
| CALENDRIER NOVEMBRE 2024 |
|
||||
|——————————————————————————————————————|
|
||||
| ———— ———— ———— |
|
||||
| | 01 | 02 | 03 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 04 |<span class="highlight"> 05 </span>| 06 | 07 | 08 | 09 | 10 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 11 |<span class="highlight"> 12 </span>| 13 | 14 |<span class="highlight"> 15 </span>|<span class="highlight"> 16 </span>|<span class="highlight"> 17 </span>| |
|
||||
| | 11 | 12 | 13 | 14 | 15 |<span class="highlight"> 16 | 17 </span>| |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 18 | 19 | 20 | 21 | 22 | 23 | 24 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 25 | 26 | 27 | 28 | 29 | 30 | 31 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
|______________________________________|</pre>
|
||||
|
||||
</div>
|
||||
<div id="mois_suivant" role="img" aria-label="calendrier de nos jours de permanence prévus pour le mois prochain">
|
||||
<pre aria-hidden="true">.——————————————————————————————————————.
|
||||
| CALENDRIER AVRIL 2024 |
|
||||
|——————————————————————————————————————|
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 01 |<span class="highlight"> 02 </span>| 03 | 04 | 05 | 06 | 07 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 08 | 09 | 10 | 11 | 12 | 13 | 14 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 15 | 16 | 17 | 18 | 19 | 20 | 21 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 22 | 23 | 24 | 25 | 26 | 27 | 28 | |
|
||||
| ———— ———— ———— ———— ———— ———— ———— |
|
||||
| | 29 |<span class="highlight"> 30 </span>| |
|
||||
| ———— ———— |
|
||||
| | 25 | 26 | 27 | 28 | 29 | 30 | |
|
||||
| ———— ———— ———— ———— ———— ———— |
|
||||
|______________________________________|</pre>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</main>
|
||||
<footer class="noscroll" aria-label="pied de page et liens vers CGU, mentions, sources et risques">
|
||||
<div id="parterre" role="img" aria-label="image d'un parterre de fleurs qui fleurit">
|
||||
|
@ -1389,7 +1385,7 @@ _ ` ^ ¨ · _ - " ` * - ; - _
|
|||
</pre>
|
||||
</div>
|
||||
<div id="liens">
|
||||
<a href="https://guide.deuxfleurs.fr/vie_associative/cgu/">CGU</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/vie_associative/gestion-des-risques/">Gestion des risques</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/vie_associative/mentions-legales">Mentions légales</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/operations/sources">Sources</a>
|
||||
<a href="https://guide.deuxfleurs.fr/vie_associative/cgu/">CGU</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/vie_associative/gestion-des-risques/">Gestion des risques</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/vie_associative/mentions-legales">Mentions légales</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/operations/sources">Sources</a><span role="separator"> · </span><a href="https://guide.deuxfleurs.fr/vie_associative/nous-rejoindre/">Nous rejoindre</a>
|
||||
</div>
|
||||
</footer>
|
||||
</div>
|
||||
|
|
|
@ -38,7 +38,10 @@ function updateAnimation(id, frames, totalFrames) {
|
|||
|
||||
}
|
||||
|
||||
animate("illustration-accueil", 500);
|
||||
animate("rennes", 1000);
|
||||
animate("orsay", 2000);
|
||||
// If the user have a setting on their device to minimize the amount of non-essential motion
|
||||
const preferReduceMotion = window.matchMedia("(prefers-reduced-motion)").matches;
|
||||
|
||||
animate("illustration-accueil", preferReduceMotion ? 1500 : 500); // Reduce framerate if use preference is to reduce motion
|
||||
animate("rennes", preferReduceMotion ? 3000 : 1000); // Reduce framerate if use preference is to reduce motion
|
||||
animate("orsay", preferReduceMotion ? 4000 : 2000); // Reduce framerate if use preference is to reduce motion
|
||||
animate("parterre", 1500);
|
Loading…
Reference in a new issue