florent/pages
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated prettier (#3420)

Browse Source 
Signed-off-by: George Araújo <george.gcac@gmail.com>
This commit is contained in:
George 2026-01-04 17:51:02 -03:00 committed by GitHub
parent 903760519c
commit 586a0ffd76
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
8 changed files with 14 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.github/agents/customize.agent.md vendored
View File

@ -344,7 +344,6 @@ Always guide users to test changes locally before pushing to GitHub:
3. **Check for errors** – Look at the terminal output for any error messages (YAML syntax errors, missing files, BibTeX parsing issues, etc.). 3. **Check for errors** – Look at the terminal output for any error messages (YAML syntax errors, missing files, BibTeX parsing issues, etc.).
4. **Verify visually** – Manually navigate through your site: 4. **Verify visually** – Manually navigate through your site:
- Check that pages load without errors - Check that pages load without errors
- Verify text displays correctly - Verify text displays correctly
- Ensure images are visible - Ensure images are visible
@ -352,7 +351,6 @@ Always guide users to test changes locally before pushing to GitHub:
- Check that your changes appear as expected - Check that your changes appear as expected
5. **Test on different pages** – If you modified: 5. **Test on different pages** – If you modified:
- `_config.yml` – Check the entire site (affects global settings) - `_config.yml` – Check the entire site (affects global settings)
- Blog posts – Check the blog page and individual post - Blog posts – Check the blog page and individual post
- Publications – Check the publications page - Publications – Check the publications page
@ -436,7 +434,6 @@ Help users avoid these frequent errors:
## Boundaries ## Boundaries
- ✅ **Always do:** - ✅ **Always do:**
- Modify configuration files (`_config.yml`, `_data/*.yml`) - Modify configuration files (`_config.yml`, `_data/*.yml`)
- Create/edit content files (posts, pages, projects, news) - Create/edit content files (posts, pages, projects, news)
- Update BibTeX bibliography - Update BibTeX bibliography
@ -446,7 +443,6 @@ Help users avoid these frequent errors:
- Reference official documentation when helpful - Reference official documentation when helpful
- ⚠️ **Ask first:** - ⚠️ **Ask first:**
- Major structural changes to the template - Major structural changes to the template
- Removing core functionality or pages - Removing core functionality or pages
- Modifying GitHub Actions workflows - Modifying GitHub Actions workflows
@ -498,21 +494,17 @@ Help users avoid these frequent errors:
When users reference issues or discussions: When users reference issues or discussions:
1. **Accept information without requiring links** – Don't demand that users track down and share issue/discussion URLs 1. **Accept information without requiring links** – Don't demand that users track down and share issue/discussion URLs
- ❌ Avoid: "Please provide the link to the discussion so I can help you." - ❌ Avoid: "Please provide the link to the discussion so I can help you."
- ✅ Do this: "Let me help based on what you've described. If you remember any details from the discussion, that would be helpful." - ✅ Do this: "Let me help based on what you've described. If you remember any details from the discussion, that would be helpful."
2. **Verify information against current code** – Assume advice from older discussions might be outdated 2. **Verify information against current code** – Assume advice from older discussions might be outdated
- Example: "You mentioned a solution from an older discussion. Let me check if that still applies with the current version..." - Example: "You mentioned a solution from an older discussion. Let me check if that still applies with the current version..."
- Be prepared to offer updated guidance if the codebase has changed - Be prepared to offer updated guidance if the codebase has changed
3. **Acknowledge patterns while providing current guidance** – Show you understand the context but prioritize current best practices 3. **Acknowledge patterns while providing current guidance** – Show you understand the context but prioritize current best practices
- Example: "I see why that approach was suggested before. With our current code, here's the recommended way to do this..." - Example: "I see why that approach was suggested before. With our current code, here's the recommended way to do this..."
4. **Mention when discussions are particularly relevant** – If a recent discussion is very relevant, you can mention it 4. **Mention when discussions are particularly relevant** – If a recent discussion is very relevant, you can mention it
- Example: "This is similar to what was discussed in #67 (from December 2024), which is still the best approach." - Example: "This is similar to what was discussed in #67 (from December 2024), which is still the best approach."
5. **Suggest sharing solutions** – If a user's question or your solution would help the community, encourage them to update or create discussions 5. **Suggest sharing solutions** – If a user's question or your solution would help the community, encourage them to update or create discussions

2
.github/agents/docs.agent.md vendored
View File

@ -133,7 +133,6 @@ to process your files located in `_layouts/` and `_includes/`.
## Boundaries ## Boundaries
- ✅ **Always do:** - ✅ **Always do:**
- Update documentation files (`*.md` in root directory) - Update documentation files (`*.md` in root directory)
- Keep documentation in sync with actual code and configuration - Keep documentation in sync with actual code and configuration
- Use existing documentation style and structure (or improve it with patterns from this agent) - Use existing documentation style and structure (or improve it with patterns from this agent)
@ -143,7 +142,6 @@ to process your files located in `_layouts/` and `_includes/`.
- Preserve existing table of contents markers (`<!--ts-->` and `<!--te-->` - Preserve existing table of contents markers (`<!--ts-->` and `<!--te-->`
- ⚠️ **Ask first:** - ⚠️ **Ask first:**
- Major restructuring of documentation organization - Major restructuring of documentation organization
- Adding entirely new documentation files - Adding entirely new documentation files
- Changing the documentation format or style guide - Changing the documentation format or style guide

7
CUSTOMIZE.md
View File

@ -213,7 +213,6 @@ Understanding al-folio's technology stack will help you better customize and ext
### Backend ### Backend
- **Jekyll 4.x**: [Jekyll](https://jekyllrb.com/) is a static site generator written in Ruby that transforms your Markdown files and templates into a static website. Jekyll is used to: - **Jekyll 4.x**: [Jekyll](https://jekyllrb.com/) is a static site generator written in Ruby that transforms your Markdown files and templates into a static website. Jekyll is used to:
- Convert Markdown files to HTML - Convert Markdown files to HTML
- Process Liquid templates - Process Liquid templates
- Manage collections (posts, projects, news, books, etc.) - Manage collections (posts, projects, news, books, etc.)
@ -221,7 +220,6 @@ Understanding al-folio's technology stack will help you better customize and ext
- Minify CSS and JavaScript - Minify CSS and JavaScript
- **Ruby Gems** (Jekyll plugins): The project uses several Ruby plugins to extend Jekyll's functionality: - **Ruby Gems** (Jekyll plugins): The project uses several Ruby plugins to extend Jekyll's functionality:
- `jekyll-scholar`: Manages bibliography files (BibTeX) and generates publication pages with citations - `jekyll-scholar`: Manages bibliography files (BibTeX) and generates publication pages with citations
- `jekyll-archives-v2`: Creates archive pages for posts and collections organized by category, tag, or date - `jekyll-archives-v2`: Creates archive pages for posts and collections organized by category, tag, or date
- `jekyll-paginate-v2`: Handles pagination for blog posts and archives - `jekyll-paginate-v2`: Handles pagination for blog posts and archives
@ -239,7 +237,6 @@ Understanding al-folio's technology stack will help you better customize and ext
### Build and Deployment ### Build and Deployment
- **GitHub Actions**: Automated workflows for building, testing, and deploying your site. Workflows are defined in `.github/workflows/`: - **GitHub Actions**: Automated workflows for building, testing, and deploying your site. Workflows are defined in `.github/workflows/`:
- **Deploy**: Automatically builds and deploys your site to GitHub Pages when you push changes to the main branch - **Deploy**: Automatically builds and deploys your site to GitHub Pages when you push changes to the main branch
- **Link checking**: Validates that all links in your site are not broken - **Link checking**: Validates that all links in your site are not broken
- **Code formatting**: Ensures code follows the Prettier code style - **Code formatting**: Ensures code follows the Prettier code style
@ -467,7 +464,6 @@ To update a library:
1. Change the `version` number 1. Change the `version` number
2. Obtain the new integrity hash for the updated library version and update the `integrity` field with the new hash. You can: 2. Obtain the new integrity hash for the updated library version and update the `integrity` field with the new hash. You can:
- Check if the CDN provider (e.g., jsDelivr, cdnjs, unpkg) provides the SRI hash for the file. Many CDN sites display the SRI hash alongside the file URL. - Check if the CDN provider (e.g., jsDelivr, cdnjs, unpkg) provides the SRI hash for the file. Many CDN sites display the SRI hash alongside the file URL.
- Generate the SRI hash yourself using a tool such as [SRI Hash Generator](https://www.srihash.org/) or by running the following command in your terminal: - Generate the SRI hash yourself using a tool such as [SRI Hash Generator](https://www.srihash.org/) or by running the following command in your terminal:
@ -477,7 +473,6 @@ To update a library:
Replace `[FILE_URL]` with the URL of the library file. Then, prefix the result with `sha384-` and use it in the `integrity` field. Replace `[FILE_URL]` with the URL of the library file. Then, prefix the result with `sha384-` and use it in the `integrity` field.
For detailed instructions on updating specific libraries, see the FAQ: For detailed instructions on updating specific libraries, see the FAQ:
- [How can I update Academicons version](FAQ.md#how-can-i-update-academicons-version-on-the-template) - [How can I update Academicons version](FAQ.md#how-can-i-update-academicons-version-on-the-template)
- [How can I update Font Awesome version](FAQ.md#how-can-i-update-font-awesome-version-on-the-template) - [How can I update Font Awesome version](FAQ.md#how-can-i-update-font-awesome-version-on-the-template)
- [How can I update Tabler Icons version](FAQ.md#how-can-i-update-tabler-icons-version-on-the-template) - [How can I update Tabler Icons version](FAQ.md#how-can-i-update-tabler-icons-version-on-the-template)
@ -660,7 +655,6 @@ GitHub restricts the default `GITHUB_TOKEN` from triggering other workflows when
### How to set up the PAT ### How to set up the PAT
1. **Create a Personal Access Token** 1. **Create a Personal Access Token**
- Go to [GitHub Settings > Developer settings > Personal access tokens](https://github.com/settings/tokens). - Go to [GitHub Settings > Developer settings > Personal access tokens](https://github.com/settings/tokens).
- Click "Generate new token" (classic or fine-grained). - Click "Generate new token" (classic or fine-grained).
- Grant at least the following permissions: - Grant at least the following permissions:
@ -668,7 +662,6 @@ GitHub restricts the default `GITHUB_TOKEN` from triggering other workflows when
- Save the token somewhere safe. - Save the token somewhere safe.
2. **Add the PAT as a repository secret** 2. **Add the PAT as a repository secret**
- Go to your repository on GitHub. - Go to your repository on GitHub.
- Navigate to `Settings` > `Secrets and variables` > `Actions` > `New repository secret`. - Navigate to `Settings` > `Secrets and variables` > `Actions` > `New repository secret`.
- Name the secret `PAT` (must match the name used in the workflow). - Name the secret `PAT` (must match the name used in the workflow).

2
INSTALL.md
View File

@ -167,14 +167,12 @@ If you need to manually re-deploy your website to GitHub pages, go to Actions, c
1. [Use this template -> Create a new repository](https://github.com/new?template_name=al-folio&template_owner=alshedivat). 1. [Use this template -> Create a new repository](https://github.com/new?template_name=al-folio&template_owner=alshedivat).
2. Netlify: **Add new site** -> **Import an existing project** -> **GitHub** and give Netlify access to the repository you just created. 2. Netlify: **Add new site** -> **Import an existing project** -> **GitHub** and give Netlify access to the repository you just created.
3. Netlify: In the deploy settings 3. Netlify: In the deploy settings
- Set **Branch to deploy** to `main` - Set **Branch to deploy** to `main`
- **Base directory** is empty - **Base directory** is empty
- Set **Build command** to `sed -i "s/^\(baseurl: \).*$/baseurl:/" _config.yml && bundle exec jekyll build` - Set **Build command** to `sed -i "s/^\(baseurl: \).*$/baseurl:/" _config.yml && bundle exec jekyll build`
- Set **Publish directory** to `_site` - Set **Publish directory** to `_site`
4. Netlify: Add the following two **environment variables** 4. Netlify: Add the following two **environment variables**
- | Key | Value | - | Key | Value |
| -------------- | -------------------------------------------------------------------------------------- | | -------------- | -------------------------------------------------------------------------------------- |
| `JEKYLL_ENV` | `production` | | `JEKYLL_ENV` | `production` |

2
_posts/2015-07-15-code.md
View File

@ -43,7 +43,6 @@ For displaying code in a list item, you have to be aware of the indentation, as
````markdown ````markdown
1. We can put fenced code blocks inside nested bullets, too. 1. We can put fenced code blocks inside nested bullets, too.
1. Like this: 1. Like this:
```c ```c
@ -56,7 +55,6 @@ For displaying code in a list item, you have to be aware of the indentation, as
Which displays: Which displays:
1. We can put fenced code blocks inside nested bullets, too. 1. We can put fenced code blocks inside nested bullets, too.
1. Like this: 1. Like this:
```c ```c

2
assets/js/distillpub/transforms.v2.js
View File

@ -436,7 +436,7 @@
} }
function createCommonjsModule(fn, module) { function createCommonjsModule(fn, module) {
return (module = { exports: {} }), fn(module, module.exports), module.exports; return ((module = { exports: {} }), fn(module, module.exports), module.exports);
} }
var bibtexParse = createCommonjsModule(function (module, exports) { var bibtexParse = createCommonjsModule(function (module, exports) {

22
package-lock.json generated
View File

@ -6,18 +6,18 @@
"": { "": {
"devDependencies": { "devDependencies": {
"@shopify/prettier-plugin-liquid": "1.4.0", "@shopify/prettier-plugin-liquid": "1.4.0",
"prettier": "3.1.1" "prettier": "^3.1.1"
} }
}, },
"node_modules/@shopify/liquid-html-parser": { "node_modules/@shopify/liquid-html-parser": {
"version": "2.2.0", "version": "2.9.0",
"resolved": "https://registry.npmjs.org/@shopify/liquid-html-parser/-/liquid-html-parser-2.2.0.tgz", "resolved": "https://registry.npmjs.org/@shopify/liquid-html-parser/-/liquid-html-parser-2.9.0.tgz",
"integrity": "sha512-hD0XV+Re9BC3yMOshHCwU94LagW7LQTWPdtpU0IE/pMbco+ke7Hir1Ad7eloHAgzR+6iw4LzDEFuHFpKZWmGKw==", "integrity": "sha512-bkI4tLbU47YUxpgbMa9fgeJjFEMvRNEFL644Yk0ZKo5H1IRzU4pPyCQ6PkGvb0JJnt7OZ+RDGvb6ZLCnAR2Z/A==",
"dev": true, "dev": true,
"license": "MIT", "license": "MIT",
"dependencies": { "dependencies": {
"line-column": "^1.0.2", "line-column": "^1.0.2",
"ohm-js": "^16.3.0" "ohm-js": "^17.0.0"
} }
}, },
"node_modules/@shopify/prettier-plugin-liquid": { "node_modules/@shopify/prettier-plugin-liquid": {
@ -73,9 +73,9 @@
} }
}, },
"node_modules/ohm-js": { "node_modules/ohm-js": {
"version": "16.6.0", "version": "17.3.0",
"resolved": "https://registry.npmjs.org/ohm-js/-/ohm-js-16.6.0.tgz", "resolved": "https://registry.npmjs.org/ohm-js/-/ohm-js-17.3.0.tgz",
"integrity": "sha512-X9P4koSGa7swgVQ0gt71UCYtkAQGOjciJPJAz74kDxWt8nXbH5HrDOQG6qBDH7SR40ktNv4x61BwpTDE9q4lRA==", "integrity": "sha512-LySMdjweN1hKBMMV8lM44+1wiewkndDNNJxtgVAscs7y683MXCdQZLsIaw64/p8NuqYbKOWZoHIOA5DU/xchoA==",
"dev": true, "dev": true,
"license": "MIT", "license": "MIT",
"engines": { "engines": {
@ -83,9 +83,9 @@
} }
}, },
"node_modules/prettier": { "node_modules/prettier": {
"version": "3.1.1", "version": "3.7.4",
"resolved": "https://registry.npmjs.org/prettier/-/prettier-3.1.1.tgz", "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.7.4.tgz",
"integrity": "sha512-22UbSzg8luF4UuZtzgiUOfcGM8s4tjBv6dJRT7j275NXsy2jb4aJa4NNveul5x4eqlF1wuhuR2RElK71RvmVaw==", "integrity": "sha512-v6UNi1+3hSlVvv8fSaoUbggEM5VErKmmpGA7Pl3HF8V6uKY7rvClBOJlH6yNwQtfTueNkGVpOv/mtWL9L4bgRA==",
"dev": true, "dev": true,
"license": "MIT", "license": "MIT",
"bin": { "bin": {

4
package.json
View File

@ -1,6 +1,6 @@
{ {
"devDependencies": { "devDependencies": {
"@shopify/prettier-plugin-liquid": "1.4.0", "@shopify/prettier-plugin-liquid": "1.10.0",
"prettier": "3.1.1" "prettier": "^3.7.4"
} }
} }