feat(tutorials): add guides for scheduling and managing appointments
- Created a new tutorial on how to schedule an appointment with a user in a support pathway. - Added a guide detailing possible actions on an appointment, including adding documents, transforming to exchanges, editing, canceling, and deleting appointments. - Introduced an index page for tutorials to improve navigation. - Updated the configuration to support multiple languages (French, English, Dutch) and added corresponding menu items. - Added various images to enhance the visual representation of the tutorials.
This commit is contained in:
Boris Waaub
@@ -1,170 +0,0 @@
|
||||
---
|
||||
title: "Content Management in Hugo: Best Practices"
|
||||
date: 2023-07-24
|
||||
author: "Michael Park"
|
||||
description: "Learn effective strategies for managing content in Hugo, from organizing your content structure to implementing taxonomies and creating dynamic content relationships."
|
||||
categories: ["Content"]
|
||||
tags: ["hugo", "content-management", "organization", "workflow"]
|
||||
featured_image: "/images/blog/blog-5.jpg"
|
||||
---
|
||||
|
||||
{{< toc >}}
|
||||
|
||||
## Introduction
|
||||
|
||||
Effective content management is crucial for maintaining a scalable Hugo site. This guide covers best practices for organizing and managing your content.
|
||||
|
||||
## Content Organization
|
||||
|
||||
### Directory Structure
|
||||
|
||||
Create a logical content hierarchy:
|
||||
|
||||
{{< code text "Content Structure" >}}
|
||||
content/
|
||||
├── blog/
|
||||
│ ├── tech/
|
||||
│ ├── tutorials/
|
||||
│ └── news/
|
||||
├── products/
|
||||
├── about/
|
||||
└── docs/
|
||||
{{< /code >}}
|
||||
|
||||
### Front Matter Templates
|
||||
|
||||
Use archetypes to standardize content:
|
||||
|
||||
{{< code yaml "archetypes/blog.md" >}}
|
||||
---
|
||||
title: "{{ replace .Name "-" " " | title }}"
|
||||
date: {{ .Date }}
|
||||
draft: true
|
||||
categories: []
|
||||
tags: []
|
||||
featured_image: ""
|
||||
description: ""
|
||||
author: ""
|
||||
---
|
||||
|
||||
{{</* toc */>}}
|
||||
|
||||
## Introduction
|
||||
|
||||
[Your introduction here]
|
||||
|
||||
## Main Content
|
||||
|
||||
[Your content here]
|
||||
{{< /code >}}
|
||||
|
||||
## Content Types
|
||||
|
||||
### Page Bundles
|
||||
|
||||
Organize related content together:
|
||||
- Group images with content
|
||||
- Manage page resources
|
||||
- Maintain content hierarchy
|
||||
|
||||
### Taxonomies
|
||||
|
||||
Create meaningful content relationships:
|
||||
|
||||
{{< code toml "config.toml" >}}
|
||||
[taxonomies]
|
||||
category = "categories"
|
||||
tag = "tags"
|
||||
series = "series"
|
||||
author = "authors"
|
||||
{{< /code >}}
|
||||
|
||||
## Content Workflow
|
||||
|
||||
### Draft Management
|
||||
|
||||
1. **Creating Drafts**
|
||||
```bash
|
||||
hugo new blog/my-draft-post.md
|
||||
```
|
||||
|
||||
2. **Preview Drafts**
|
||||
```bash
|
||||
hugo server -D
|
||||
```
|
||||
|
||||
3. **Publishing Content**
|
||||
- Update front matter
|
||||
- Review content
|
||||
- Deploy changes
|
||||
|
||||
### Content Updates
|
||||
|
||||
Maintain content freshness:
|
||||
|
||||
1. **Regular Reviews**
|
||||
- Check for outdated information
|
||||
- Update screenshots
|
||||
- Verify external links
|
||||
|
||||
2. **Version Control**
|
||||
- Track content changes
|
||||
- Collaborate with team
|
||||
- Maintain history
|
||||
|
||||
## Dynamic Content
|
||||
|
||||
### Related Content
|
||||
|
||||
{{< code html "layouts/partials/related.html" >}}
|
||||
{{ $related := .Site.RegularPages.Related . | first 3 }}
|
||||
{{ with $related }}
|
||||
<h3>Related Posts</h3>
|
||||
<ul>
|
||||
{{ range . }}
|
||||
<li><a href="{{ .RelPermalink }}">{{ .Title }}</a></li>
|
||||
{{ end }}
|
||||
</ul>
|
||||
{{ end }}
|
||||
{{< /code >}}
|
||||
|
||||
### Content Reuse
|
||||
|
||||
Create reusable content snippets:
|
||||
|
||||
{{< code html "layouts/shortcodes/notice.html" >}}
|
||||
<div class="notice notice-{{ .Get 0 }}">
|
||||
{{ .Inner | markdownify }}
|
||||
</div>
|
||||
{{< /code >}}
|
||||
|
||||
## SEO and Metadata
|
||||
|
||||
1. **Title Optimization**
|
||||
2. **Meta Descriptions**
|
||||
3. **URL Structure**
|
||||
4. **Image Alt Text**
|
||||
|
||||
## Content Backup
|
||||
|
||||
### Backup Strategies
|
||||
|
||||
1. **Version Control**
|
||||
- Git repository
|
||||
- Regular commits
|
||||
- Remote backups
|
||||
|
||||
2. **External Storage**
|
||||
- Cloud storage
|
||||
- Local backups
|
||||
- Asset management
|
||||
|
||||
## Conclusion
|
||||
|
||||
Good content management practices are essential for maintaining a successful Hugo site. By following these guidelines, you can create an efficient and scalable content workflow.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Hugo Content Management Documentation](https://gohugo.io/content-management/)
|
||||
- [Hugo Archetypes Guide](https://gohugo.io/content-management/archetypes/)
|
||||
- [Hugo Taxonomies Documentation](https://gohugo.io/content-management/taxonomies/)
|
||||
@@ -1,121 +0,0 @@
|
||||
---
|
||||
title: "Customizing Your Hugo Theme: A Deep Dive"
|
||||
date: 2023-07-21
|
||||
author: "Jane Smith"
|
||||
description: "Learn how to customize your Hugo theme to create a unique website that matches your brand and requirements."
|
||||
categories: ["Development"]
|
||||
tags: ["hugo", "themes", "customization", "web-design"]
|
||||
featured_image: "/images/blog/blog-2.webp"
|
||||
---
|
||||
|
||||
{{< toc >}}
|
||||
|
||||
## Introduction
|
||||
|
||||
While Hugo comes with many beautiful themes, you'll often want to customize them to match your specific needs. This guide will walk you through the process of customizing your Hugo theme effectively.
|
||||
|
||||
## Understanding Hugo's Theme Structure
|
||||
|
||||
Before diving into customization, it's important to understand how Hugo themes are structured.
|
||||
|
||||
## Basic Theme Customization
|
||||
|
||||
### 1. Colors and Typography
|
||||
|
||||
The easiest way to start customizing your theme is by modifying the CSS:
|
||||
|
||||
{{< code css "assets/scss/main.scss" >}}
|
||||
:root {
|
||||
--primary-color: #007bff;
|
||||
--secondary-color: #6c757d;
|
||||
--font-family: 'Inter', sans-serif;
|
||||
}
|
||||
|
||||
body {
|
||||
font-family: var(--font-family);
|
||||
color: #333;
|
||||
}
|
||||
{{< /code >}}
|
||||
|
||||
### 2. Layout Modifications
|
||||
|
||||
You can override any layout file from the theme by creating a matching file in your site's layouts directory.
|
||||
|
||||
## Advanced Customization Techniques
|
||||
|
||||
### Creating Custom Shortcodes
|
||||
|
||||
Shortcodes are a powerful way to add custom functionality:
|
||||
|
||||
{{< code html "layouts/shortcodes/custom-alert.html" >}}
|
||||
<div class="alert alert-{{ .Get 0 }}">
|
||||
{{ .Inner | markdownify }}
|
||||
</div>
|
||||
{{< /code >}}
|
||||
|
||||
### Working with Partials
|
||||
|
||||
Partials help keep your code DRY and maintainable:
|
||||
|
||||
{{< code html "layouts/partials/custom-header.html" >}}
|
||||
<header class="site-header">
|
||||
<nav>
|
||||
{{ range .Site.Menus.main }}
|
||||
<a href="{{ .URL }}">{{ .Name }}</a>
|
||||
{{ end }}
|
||||
</nav>
|
||||
</header>
|
||||
{{< /code >}}
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Don't Edit Theme Files Directly**
|
||||
- Create overrides in your site directory
|
||||
- Use Hugo's lookup order to your advantage
|
||||
|
||||
2. **Maintain Compatibility**
|
||||
- Test your customizations across different devices
|
||||
- Keep accessibility in mind
|
||||
|
||||
3. **Performance Considerations**
|
||||
- Optimize images and assets
|
||||
- Minimize CSS and JavaScript
|
||||
|
||||
## Common Customization Examples
|
||||
|
||||
### Custom Homepage Layout
|
||||
|
||||
{{< code html "layouts/index.html" >}}
|
||||
{{ define "main" }}
|
||||
<div class="homepage">
|
||||
{{ partial "hero.html" . }}
|
||||
{{ partial "featured-posts.html" . }}
|
||||
{{ partial "newsletter.html" . }}
|
||||
</div>
|
||||
{{ end }}
|
||||
{{< /code >}}
|
||||
|
||||
### Custom Taxonomy Pages
|
||||
|
||||
{{< code html "layouts/taxonomy/category.html" >}}
|
||||
{{ define "main" }}
|
||||
<div class="category-page">
|
||||
<h1>{{ .Title }}</h1>
|
||||
<div class="posts-grid">
|
||||
{{ range .Pages }}
|
||||
{{ partial "post-card.html" . }}
|
||||
{{ end }}
|
||||
</div>
|
||||
</div>
|
||||
{{ end }}
|
||||
{{< /code >}}
|
||||
|
||||
## Conclusion
|
||||
|
||||
Customizing your Hugo theme allows you to create a unique website that stands out. By understanding Hugo's structure and following best practices, you can make modifications that are both effective and maintainable.
|
||||
|
||||
## Further Resources
|
||||
|
||||
- [Hugo Documentation](https://gohugo.io/documentation/)
|
||||
- [Hugo Forums](https://discourse.gohugo.io/)
|
||||
- [Hugo Theme Components](https://themes.gohugo.io/tags/components/)
|
||||
@@ -1,101 +0,0 @@
|
||||
---
|
||||
title: "Deploying Hugo Sites: A Complete Guide"
|
||||
date: 2023-07-22
|
||||
author: "Alex Johnson"
|
||||
description: "Learn how to deploy your Hugo site to various platforms including Netlify, Vercel, and GitHub Pages."
|
||||
categories: ["Deployment"]
|
||||
tags: ["hugo", "deployment", "netlify", "vercel", "github-pages"]
|
||||
featured_image: "/images/blog/blog-3.webp"
|
||||
---
|
||||
|
||||
{{< toc >}}
|
||||
|
||||
## Introduction
|
||||
|
||||
Once you've built your Hugo site, the next step is deploying it to make it accessible to the world. This guide covers various deployment options and best practices.
|
||||
|
||||
## Popular Deployment Platforms
|
||||
|
||||
### 1. Netlify
|
||||
|
||||
Netlify offers a seamless deployment experience:
|
||||
|
||||
{{< code bash "terminal" >}}
|
||||
# Create netlify.toml
|
||||
[build]
|
||||
publish = "public"
|
||||
command = "hugo --gc --minify"
|
||||
|
||||
[build.environment]
|
||||
HUGO_VERSION = "0.95.0"
|
||||
{{< /code >}}
|
||||
|
||||
### 2. Vercel
|
||||
|
||||
Vercel provides excellent performance and analytics.
|
||||
|
||||
### 3. GitHub Pages
|
||||
|
||||
Perfect for project sites and personal blogs:
|
||||
|
||||
{{< code yaml "github-workflow.yml" >}}
|
||||
name: GitHub Pages
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Setup Hugo
|
||||
uses: peaceiris/actions-hugo@v2
|
||||
{{< /code >}}
|
||||
|
||||
## Deployment Best Practices
|
||||
|
||||
1. **Use Version Control**
|
||||
- Track your changes
|
||||
- Collaborate effectively
|
||||
- Enable automated deployments
|
||||
|
||||
2. **Optimize Assets**
|
||||
- Compress images
|
||||
- Minify CSS/JS
|
||||
- Enable caching
|
||||
|
||||
3. **Configure CI/CD**
|
||||
- Automate builds
|
||||
- Run tests
|
||||
- Deploy automatically
|
||||
|
||||
## Performance Considerations
|
||||
|
||||
1. **Page Load Speed**
|
||||
- Optimize images
|
||||
- Minimize HTTP requests
|
||||
- Use CDN
|
||||
|
||||
2. **SEO**
|
||||
- Configure meta tags
|
||||
- Create sitemap
|
||||
- Enable robots.txt
|
||||
|
||||
## Security Measures
|
||||
|
||||
1. **Enable HTTPS**
|
||||
2. **Configure Headers**
|
||||
3. **Implement CSP**
|
||||
|
||||
## Conclusion
|
||||
|
||||
Choosing the right deployment platform and following best practices ensures your Hugo site is fast, secure, and reliable.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Hugo Deployment Documentation](https://gohugo.io/hosting-and-deployment/)
|
||||
- [Netlify Documentation](https://docs.netlify.com/)
|
||||
- [Vercel Documentation](https://vercel.com/docs)
|
||||
@@ -1,81 +0,0 @@
|
||||
---
|
||||
title: "Getting Started with Hugo: A Beginner's Guide"
|
||||
date: 2023-07-20
|
||||
author: "John Doe"
|
||||
description: "Learn how to build your first website with Hugo, the world's fastest framework for building websites."
|
||||
categories: ["Tutorials"]
|
||||
tags: ["hugo", "static-site", "web-development", "beginners"]
|
||||
featured_image: "/images/blog/blog-1.jpg"
|
||||
---
|
||||
|
||||
{{< toc >}}
|
||||
|
||||
## Introduction
|
||||
|
||||
Hugo is one of the most popular open-source static site generators. With its amazing speed and flexibility, Hugo makes building websites fun again.
|
||||
|
||||
## Why Choose Hugo?
|
||||
|
||||
Here are some compelling reasons to choose Hugo for your next project:
|
||||
|
||||
1. Lightning Fast
|
||||
2. Easy to Learn
|
||||
3. Highly Flexible
|
||||
4. Great Community
|
||||
|
||||
## Setting Up Your First Hugo Site
|
||||
|
||||
Let's walk through creating your first Hugo site:
|
||||
|
||||
{{< code bash "terminal" >}}
|
||||
# Create a new Hugo site
|
||||
hugo new site my-awesome-site
|
||||
cd my-awesome-site
|
||||
|
||||
# Initialize git and add a theme
|
||||
git init
|
||||
git submodule add https://github.com/theNewDynamic/gohugo-theme-ananke themes/ananke
|
||||
|
||||
# Add the theme to your configuration
|
||||
echo "theme = 'ananke'" >> config.toml
|
||||
|
||||
# Create your first post
|
||||
hugo new posts/my-first-post.md
|
||||
{{< /code >}}
|
||||
|
||||
## Working with Content
|
||||
|
||||
Hugo makes content creation straightforward. Here's how to organize your content effectively.
|
||||
|
||||
## Advanced Features
|
||||
|
||||
Hugo comes with many advanced features out of the box:
|
||||
|
||||
1. **Taxonomies**: Categories and tags
|
||||
2. **Shortcodes**: Easy way to add complex content
|
||||
3. **Custom Outputs**: JSON, AMP, etc.
|
||||
4. **Asset Processing**: SASS/SCSS, PostCSS
|
||||
|
||||
## Code Examples
|
||||
|
||||
Here's an example of a simple Hugo template:
|
||||
|
||||
{{< code html "layouts/_default/single.html" >}}
|
||||
{{ define "main" }}
|
||||
<article>
|
||||
<h1>{{ .Title }}</h1>
|
||||
<time>{{ .Date.Format "2006-01-02" }}</time>
|
||||
{{ .Content }}
|
||||
</article>
|
||||
{{ end }}
|
||||
{{< /code >}}
|
||||
|
||||
## Conclusion
|
||||
|
||||
Hugo provides an excellent foundation for building modern websites. Its combination of speed, flexibility, and ease of use makes it a great choice for projects of any size.
|
||||
|
||||
## Next Steps
|
||||
|
||||
- Explore Hugo's [official documentation](https://gohugo.io/documentation/)
|
||||
- Join the [Hugo community](https://discourse.gohugo.io/)
|
||||
- Check out some [Hugo themes](https://themes.gohugo.io/)
|
||||
@@ -1,119 +0,0 @@
|
||||
---
|
||||
title: "Optimizing Hugo Performance: Speed Up Your Site"
|
||||
date: 2023-07-23
|
||||
author: "Sarah Chen"
|
||||
description: "Learn advanced techniques to optimize your Hugo site for better performance, faster load times, and improved user experience."
|
||||
categories: ["Performance"]
|
||||
tags: ["hugo", "optimization", "performance", "seo"]
|
||||
featured_image: "/images/blog/blog-4.jpg"
|
||||
---
|
||||
|
||||
{{< toc >}}
|
||||
|
||||
## Introduction
|
||||
|
||||
Performance is crucial for user experience and SEO. In this guide, we'll explore various techniques to optimize your Hugo site for maximum performance.
|
||||
|
||||
## Asset Optimization
|
||||
|
||||
### Image Optimization
|
||||
|
||||
Images often contribute the most to page weight. Here's how to optimize them:
|
||||
|
||||
{{< code html "layouts/shortcodes/optimized-image.html" >}}
|
||||
{{ $image := .Page.Resources.GetMatch (printf "%s" (.Get "src")) }}
|
||||
{{ $options := dict "targetWidth" 800 "quality" 85 }}
|
||||
{{ $processed := $image.Process "resize 800x webp q85" }}
|
||||
<img src="{{ $processed.RelPermalink }}"
|
||||
alt="{{ .Get "alt" }}"
|
||||
loading="lazy"
|
||||
class="rounded-lg shadow-lg">
|
||||
{{< /code >}}
|
||||
|
||||
### CSS and JavaScript
|
||||
|
||||
Minimize your asset footprint:
|
||||
- Minify CSS and JavaScript
|
||||
- Bundle assets appropriately
|
||||
- Remove unused code
|
||||
|
||||
## Caching Strategies
|
||||
|
||||
1. **Browser Caching**
|
||||
- Set appropriate cache headers
|
||||
- Use versioned assets
|
||||
- Implement service workers
|
||||
|
||||
2. **Hugo Caching**
|
||||
- Use `.Scratch` for expensive operations
|
||||
- Cache partial results
|
||||
- Implement memoization
|
||||
|
||||
## Content Delivery
|
||||
|
||||
### CDN Setup
|
||||
|
||||
{{< code toml "config.toml" >}}
|
||||
[params.cdn]
|
||||
enable = true
|
||||
provider = "cloudfront"
|
||||
domain = "cdn.example.com"
|
||||
{{< /code >}}
|
||||
|
||||
### Edge Computing
|
||||
|
||||
Leverage edge computing for faster content delivery:
|
||||
- Deploy to multiple regions
|
||||
- Use edge functions when needed
|
||||
- Implement geo-routing
|
||||
|
||||
## Performance Monitoring
|
||||
|
||||
### Key Metrics
|
||||
|
||||
1. **Core Web Vitals**
|
||||
- Largest Contentful Paint (LCP)
|
||||
- First Input Delay (FID)
|
||||
- Cumulative Layout Shift (CLS)
|
||||
|
||||
2. **Additional Metrics**
|
||||
- Time to First Byte (TTFB)
|
||||
- First Contentful Paint (FCP)
|
||||
- Total Blocking Time (TBT)
|
||||
|
||||
## Advanced Optimization Techniques
|
||||
|
||||
### Resource Hints
|
||||
|
||||
{{< code html "layouts/partials/head.html" >}}
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preload" href="/fonts/main.woff2" as="font" type="font/woff2" crossorigin>
|
||||
{{< /code >}}
|
||||
|
||||
### Critical CSS
|
||||
|
||||
Inline critical styles for faster rendering:
|
||||
|
||||
{{< code html "layouts/partials/critical-css.html" >}}
|
||||
<style>
|
||||
/* Critical CSS here */
|
||||
.hero { /* ... */ }
|
||||
.nav { /* ... */ }
|
||||
</style>
|
||||
{{< /code >}}
|
||||
|
||||
## SEO Optimization
|
||||
|
||||
1. **Structured Data**
|
||||
2. **XML Sitemaps**
|
||||
3. **Meta Tags**
|
||||
|
||||
## Conclusion
|
||||
|
||||
Optimizing your Hugo site is an ongoing process. Regular monitoring and adjustments ensure your site maintains peak performance.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Hugo Performance Documentation](https://gohugo.io/documentation/)
|
||||
- [Web.dev Performance Guide](https://web.dev/performance/)
|
||||
- [PageSpeed Insights](https://pagespeed.web.dev/)
|
||||
105
content/tutorials/Comment-créer-des-plages-de-disponibilité_.md
Normal file
105
content/tutorials/Comment-créer-des-plages-de-disponibilité_.md
Normal file
@@ -0,0 +1,105 @@
|
||||
---
|
||||
title: "Comment créer des plages de disponibilité?"
|
||||
date: 2026-01-28
|
||||
author: "Champs-Libres"
|
||||
description: "Ce guide explique comment créer des plages de disponibilité pour fixer par la suite des rendez-vous."
|
||||
categories: ["Rendez-vous"]
|
||||
tags: ["disponibilité", "rendez-vous"]
|
||||
featured_image: "/images/tutorials/65077ad2-e882-491a-bb79-123cc45c365d-thumb-UecjtYQCiB7aYk8HOo6U375Pdj21j5.png"
|
||||
---
|
||||
|
||||
==========================================
|
||||
|
||||
Ce guide explique comment créer des plages de disponibilité pour fixer par la suite des rendez-vous.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Accéder au menu principal
|
||||
-------------------------
|
||||
|
||||
Cliquez sur le menu Bienvenue
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ouvrir le sous-menu Mes rendez-vous
|
||||
-----------------------------------
|
||||
|
||||
Cliquez sur le sous menu Mes rendez-vous
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Sélectionner le lieu du rendez-vous
|
||||
-----------------------------------
|
||||
|
||||
Sélectionnez le lieu du rendez-vous dans le menu déroulant
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Sélectionner la durée des créneaux
|
||||
----------------------------------
|
||||
|
||||
Sélectionnez la durée des créneaux de rendez-vous en utilisant le menu déroulant.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Personnaliser l'affichage de l'agenda
|
||||
-------------------------------------
|
||||
|
||||
Personnalisez l'affichage de l'agenda en incluant les WE oui ou non, en passant d'un mode vue journalière (jour) ou hebdomadaire (semaine).
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser les plages de disponibilité sans RDV
|
||||
-----------------------------------------------
|
||||
|
||||
Cette vue vous permet de voir toutes les plages de disponibilités enregistrées dans l'agenda avec le créneau horaire et le lieu. Ces plages de disponibilités sont encore libres et sans RDV de planifié.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ajouter une plage de disponibilité
|
||||
----------------------------------
|
||||
|
||||
Pour ajouter une plage de disponibilité, sélectionnez une heure de départ et une heure de fin. La plage de disponibilité s'affichera ensuite avec les détails d'horaire ainsi que le lieu.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Modifier le lieu d'une plage de disponibilité
|
||||
---------------------------------------------
|
||||
|
||||
Pour modifier un lieu, cliquez sur la plage de disponibilité et choisissez un autre lieu, puis enregistrez.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Supprimer une plage de disponibilité
|
||||
------------------------------------
|
||||
|
||||
Pour supprimer une plage de disponibilité, cliquez sur la petite croix.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Copier les plages de disponibilité
|
||||
----------------------------------
|
||||
|
||||
Il est possible de copier les plages de disponibilité d'un jour/semaie à l'autre via la barre du dessous.
|
||||
|
||||
* * *
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
title: "Comment créer ou inviter un autre utilisateur à un rendez-vous ?"
|
||||
date: 2026-01-28
|
||||
author: "Champs-Libres"
|
||||
description: "Ce guide décrit comment créer un rendez-vous dans l'agenda d'un autre utilisateur ou comment inviter un autre utilisateur à un rendez-vous."
|
||||
categories: ["Rendez-vous"]
|
||||
tags: ["rendez-vous", "invitation"]
|
||||
featured_image: "/images/tutorials/112365c2-b075-4dcd-90d8-c1edb2234839-thumb-DctkSrpXioN66cYOgVvldIKcG1HbcN.png"
|
||||
---
|
||||
Comment créer ou inviter un autre utilisateur à un rendez-vous ?
|
||||
==============================================================================================================
|
||||
|
||||
Ce guide décrit comment créer un rendez-vous dans l'agenda d'un autre utilisateur OU comment inviter un autre utilisateur à un rendez-vous?
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ouvrir le menu Rendez-vous dans le parcours de l'usager
|
||||
-------------------------------------------------------
|
||||
|
||||
Cliquez sur "créer" pour créer un nouveau rendez-vous pour un utilisateur qui est différent du référent.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Choisir l'utilisateur principal
|
||||
-------------------------------
|
||||
|
||||
Choisissez l'utilisateur principal du rendez-vous. C'est l'agenda de cette personne qui s'affichera en-dessous.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ajouter les parties concernées
|
||||
------------------------------
|
||||
|
||||
Dans les parties concernées, ajouter l'usager concerné.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Sélectionner un créneau horaire
|
||||
-------------------------------
|
||||
|
||||
L'agenda de l'utilisateur principal s'affiche avec ses plages de disponibilité (+le lieu). Sélectionnez-en une. Attention, vous ne pouvez pas fixer des rendez-vous en-dehors des plages de disponibilité créés par l'utilisateur principal. Si vous cliquez en-dehors de ces plages horaires, le logiciel vous demandera si vous souhaitez redevenir l'utilisateur principal. Deux agendas s'afficheront dès lors avec les disponibilités de l'utilisateur principal ainsi que les vôtres.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ajouter des personnes concernées
|
||||
--------------------------------
|
||||
|
||||
Si vous souhaitez ajouter des personnes à votre RDV, vous pouvez les ajouter dans les parties concernées. Leurs agendas ainsi que leurs disponibilités s'afficheront. Attention, pour que les plages de disponibilité CHILL s'affichent, il faut que le petit bouton Disponibilités soit enclenché (ce qui n'est pas le cas dans l'impression d'écran). Bien les activer (voir impression d'écran suivante).
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser les disponibilités CHILL et l'agenda externe
|
||||
-------------------------------------------------------
|
||||
|
||||
Les disponibilités CHILL s'affichent si le bouton de gauche est activé. Les rendez-vous des agendas externes s'affichent si le bouton de droite est activé. Dans cet exemple, les disponibilités CHILL de "Seforme" ainsi que son agenda externe seront visibles. Les disponibilités CHILL de 'écoute" ne seront pas visibles mais bien son agenda externe (si synchronisé).
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser les invitations des personnes concernées
|
||||
---------------------------------------------------
|
||||
|
||||
Les personnes concernées qui ont été invitées à un RENDEZ-VOUS verront s'afficher dans leur profil un sous menu "mes invitations" avec le nombre d'invitation en attente. Dans cet exemple, 1 invitation est en attente.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Accepter l'invitation à un rendez-vous
|
||||
--------------------------------------
|
||||
|
||||
Le détail du rendez-vous s'affiche. Pour répondre, cliquez sur répondre. Plusieurs options sont disponibles: accepter, refuser ou accepter provisoirement.
|
||||
|
||||
* * *
|
||||
@@ -0,0 +1,114 @@
|
||||
---
|
||||
title: "Comment fixer un rendez-vous avec un usager dans un parcours?"
|
||||
date: 2026-01-28
|
||||
author: "Champs-Libres"
|
||||
description: "Ce guide décrit comment fixer un rendez-vous pour soi-même (référent) avec un usager dans le contexte d'un parcours d'accompagnement."
|
||||
categories: ["Rendez-vous"]
|
||||
tags: ["rendez-vous", "parcours"]
|
||||
featured_image: "/images/tutorials/35510882-6d53-461f-8ac3-e659efc181e3-thumb-FUWhHNyUS7ZR9UlHPzIQ3LeII8WiFS.png"
|
||||
---
|
||||
Comment fixer un rendez-vous avec un usager dans un parcours?
|
||||
=============================================================
|
||||
|
||||
Ce guide décrit comment fixer un rendez-vous pour soi-même (référent) avec un usager dans le contexte d'un parcours d'accompagnement.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Entrer dans le menu RENDEZ\_VOUS
|
||||
--------------------------------
|
||||
|
||||
Cliquez sur le menu RENDEZ-VOUS à droite lorsque vous êtes dans l'univers parcours de l'usager.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Choisir une option de création
|
||||
------------------------------
|
||||
|
||||
Si vous souhaitez fixer un RDV dans votre agenda, cliquez sur créer pour le référent
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Sélectionner les parties concernées
|
||||
-----------------------------------
|
||||
|
||||
Ajoutez l'usager concerné, les tiers et toutes autres personnes concernées par le Rendez-vous.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Choisir le lieu du rendez-vous
|
||||
------------------------------
|
||||
|
||||
Confirm or select the location for the exchange by interacting with the 'Localisation de l'échange' field, which currently shows 'Gembloux (Implantations)'.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Afficher l'agenda
|
||||
-----------------
|
||||
|
||||
Deux options d'affichage existent: montrer l'agenda CHILL du référent (et donc ses plages de disponibilités indiquées dans son profil) et montrer l'agenda pro du référent (Outlook ou autre). A savoir que cet agenda s'affichera uniquement si la synchronisation avec CHILL a été effectuée dans les deux sens.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Planifier un rendez-vous
|
||||
------------------------
|
||||
|
||||
Si l'heure et le lieu vous conviennent, cliquez sur la plage horaire pour réserver la plage horaire. La case s'affichera dès lors en bleu foncé avec le texte "rendez-vous fixé". Attention, il n'est actuellement pas possibile de modifier l'heure du rendez-vous. Si vous souhaitez modifier l'heure, il faudra repasser par le profil de l'utilisateur concerné.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Envoyer un SMS à l'usager
|
||||
-------------------------
|
||||
|
||||
Il est possible de configurer l'envoi d'un SMS à l'usager concerné par le rendez-vous. Le SMS sera envoyé 48h avant le rendez-vous avec le lieu et l'heure du rendez-vous.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Finaliser la création du rendez-vous
|
||||
------------------------------------
|
||||
|
||||
Finalisez la création du rendez-vous en cliquant soit sur créer ou sur "créer et ajouter un document". En choisissant cette option, vous pourrez ajouter un document au rendez-vous. Il est possible d'ajouter plusieurs documents à un rendez-vous. Il est également possible de rajouter le document après sa création.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser le rendez-vous créé dans le parcours de l'usager
|
||||
-----------------------------------------------------------
|
||||
|
||||
Une fois le RDV créé, il s'affichera en accédant au menu rendez-vous dans le parcours de l'usager. Plusieurs actions sont possibles à cette étape: ajouter un document, transformer le rdv en échange, éditer le rendez-vous, l'annuler ou le supprimer (voir le manuel s'y rapportant).
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser le rendez-vous crée dans le profil de l'utilisateur
|
||||
--------------------------------------------------------------
|
||||
|
||||
Pour visualiser tous ses rendez-vous créés, il suffit d'aller dans son profil utilisateur, section mes rendez-vous. Le nom de l'usager s'affichera dans l'agenda CHILL. Il est possible d'accéder au rendez-vous dans le parcours et de le modifier en cliquant dessus.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser le rendez-vous dans les résultats de recherche
|
||||
---------------------------------------------------------
|
||||
|
||||
Les rendez-vous pris avec l'usager sont visibles en-dessous du parcours sous le titre 'prochains rendez-vous'
|
||||
|
||||
* * *
|
||||
@@ -0,0 +1,96 @@
|
||||
---
|
||||
title: "Quelles sont les actions possibles sur un rendez-vous?"
|
||||
date: 2026-01-28
|
||||
author: "Champs-Libres"
|
||||
description: "Ce guide décrit les différentes actions possibles sur un rendez-vous : ajouter un document, transformer en échange, éditer, annuler, supprimer."
|
||||
categories: ["Rendez-vous"]
|
||||
tags: ["rendez-vous", "actions"]
|
||||
featured_image: "/images/tutorials/78e7a782-c985-411b-8175-b697c171acf7-thumb-EXPSXMUJqjhf6BMFIsaKqPot59dz0R.png"
|
||||
---
|
||||
Quelles sont les actions possibles sur un rendez-vous?
|
||||
======================================================
|
||||
|
||||
Ce guide décrit les différentes actions possibles sur un rendez-vous: ajouter un document, transformer en échange, éditer, annuler, supprimer.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ajouter un document
|
||||
-------------------
|
||||
|
||||
Pour ajouter un document, cliquez sur ajouter un document.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Ajouter le titre et le document
|
||||
-------------------------------
|
||||
|
||||
Donnez un titre au document, déposez le document et enregistrez. Le document sera ensuite visible dans le rendez-vous.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Transformer un rendez-vous en échange
|
||||
-------------------------------------
|
||||
|
||||
Transformez le rendez-vous en échange en cliquant sur "transformer en échange". Il vous suffit ensuite de choisir le type d'échange et de compléter la page d'échange.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Visualiser le document et l'échange
|
||||
-----------------------------------
|
||||
|
||||
Une fois le document ajouté et l'échange enregistré, ils seront visibles dans le rendez-vous.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Supprimer un rendez-vous
|
||||
------------------------
|
||||
|
||||
Il est possible de supprimer totalement un rendez-vous en cliquant sur la petite poubelle et ensuite de confirmer la suppression.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Annuler un rendez-vous
|
||||
----------------------
|
||||
|
||||
Pour annuler un rendez-vous, cliquez sur "annuler".
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Choisir un motif d'annulation
|
||||
-----------------------------
|
||||
|
||||
Choisissez ensuite le motif d'annulation (configurables dans l'admin) et cliquez sur enregistrer.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Le rendez-vous est annulé
|
||||
-------------------------
|
||||
|
||||
Le rendez-vous ainsi que son motif d'annulation sera visible dans la liste des rendez-vous. Attention, cette plage de disponibilité sera totalement supprimée de l'agenda de l'utilisateur.
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
|
||||
Supprimer un rendez-vous
|
||||
------------------------
|
||||
|
||||
Pour supprimer un rendez-vous, cliquez sur la petite poubelle et confirmer la suppression. Dans ce cas-ci, la plage de disponibilité redeviendra disponible dans le planning de l'utilisateur.
|
||||
|
||||
* * *
|
||||
4
content/tutorials/_index.md
Normal file
4
content/tutorials/_index.md
Normal file
@@ -0,0 +1,4 @@
|
||||
---
|
||||
title: "Tutoriels"
|
||||
layout: "list"
|
||||
---
|
||||
88
hugo.toml
88
hugo.toml
@@ -4,6 +4,25 @@ title = ""
|
||||
theme = "chill-theme"
|
||||
defaultContentLanguage = "fr"
|
||||
|
||||
# Language configuration
|
||||
[languages]
|
||||
[languages.fr]
|
||||
languageCode = "fr-fr"
|
||||
languageName = "Français"
|
||||
weight = 1
|
||||
contentDir = "content"
|
||||
|
||||
[languages.en]
|
||||
languageCode = "en-us"
|
||||
languageName = "English"
|
||||
weight = 2
|
||||
contentDir = "content/en"
|
||||
[languages.nl]
|
||||
languageCode = "nl-nl"
|
||||
languageName = "Nederlands"
|
||||
weight = 3
|
||||
contentDir = "content/nl"
|
||||
|
||||
# Required Features
|
||||
enableEmoji = true # Enable emoji support
|
||||
enableGitInfo = true # Enable Git info for lastmod
|
||||
@@ -108,11 +127,76 @@ pagination = { pagerSize = 6, path = "page" }
|
||||
has_submenu = true
|
||||
submenu = [
|
||||
{ name = "Documentation technique", url = "/resources/technical-documentation" },
|
||||
{ name = "Manuels", url = "/resources/manuals" }
|
||||
{ name = "Manuels", url = "/resources/manuals" },
|
||||
{ name = "Tutoriels", url = "/tutorials" }
|
||||
]
|
||||
[[menu.main]]
|
||||
name = "Nous contacter"
|
||||
url = "/contact"
|
||||
weight = 5
|
||||
|
||||
|
||||
[languages.en.menu]
|
||||
[[languages.en.menu.main]]
|
||||
name = "Features"
|
||||
url = "/features"
|
||||
weight = 1
|
||||
[[languages.en.menu.main]]
|
||||
name = "Installation"
|
||||
weight = 2
|
||||
[languages.en.menu.main.params]
|
||||
has_submenu = true
|
||||
submenu = [
|
||||
{ name = "By Champs Libres", url = "/install/hosted" },
|
||||
{ name = "Self-hosted", url = "/install/on-premise" }
|
||||
]
|
||||
[[languages.en.menu.main]]
|
||||
name = "Pricing"
|
||||
url = "/pricing"
|
||||
weight = 3
|
||||
[[languages.en.menu.main]]
|
||||
name = "Resources"
|
||||
weight = 4
|
||||
[languages.en.menu.main.params]
|
||||
has_submenu = true
|
||||
submenu = [
|
||||
{ name = "Technical Documentation", url = "/resources/technical-documentation" },
|
||||
{ name = "Manuals", url = "/resources/manuals" },
|
||||
{ name = "Tutorials", url = "/tutorials" }
|
||||
]
|
||||
[[languages.en.menu.main]]
|
||||
name = "Contact Us"
|
||||
url = "/contact"
|
||||
weight = 5
|
||||
|
||||
[languages.nl.menu]
|
||||
[[languages.nl.menu.main]]
|
||||
name = "Functies"
|
||||
url = "/features"
|
||||
weight = 1
|
||||
[[languages.nl.menu.main]]
|
||||
name = "Installatie"
|
||||
weight = 2
|
||||
[languages.nl.menu.main.params]
|
||||
has_submenu = true
|
||||
submenu = [
|
||||
{ name = "Door Champs Libres", url = "/install/hosted" },
|
||||
{ name = "Zelf gehost", url = "/install/on-premise" }
|
||||
]
|
||||
[[languages.nl.menu.main]]
|
||||
name = "Prijsstelling"
|
||||
url = "/pricing"
|
||||
weight = 3
|
||||
[[languages.nl.menu.main]]
|
||||
name = "Bronnen"
|
||||
weight = 4
|
||||
[languages.nl.menu.main.params]
|
||||
has_submenu = true
|
||||
submenu = [
|
||||
{ name = "Technische Documentatie", url = "/resources/technical-documentation" },
|
||||
{ name = "Handleidingen", url = "/resources/manuals" },
|
||||
{ name = "Tutorials", url = "/tutorials" }
|
||||
]
|
||||
[[languages.nl.menu.main]]
|
||||
name = "Contacteer Ons"
|
||||
url = "/contact"
|
||||
weight = 5
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 181 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 132 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 170 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 195 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 211 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 117 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 142 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 123 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 183 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 164 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 136 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 146 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 85 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 176 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 147 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 120 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 120 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 109 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 150 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 118 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 93 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 89 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 175 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
Reference in New Issue
Block a user