diff --git a/content/contributing-code/documentation-guidelines/contents.lr b/content/contributing-code/documentation-guidelines/contents.lr
new file mode 100644
index 00000000..f5efc80a
--- /dev/null
+++ b/content/contributing-code/documentation-guidelines/contents.lr
@@ -0,0 +1,43 @@
+_model: page
+---
+_template: page-with-toc.html
+---
+title: Documentation Guidelines
+---
+description: This Documentation Guidelines (style guide) ensures all the files in all repositories and any other documentation are properly documented.
+---
+body:
+
+# Documentation guidelines
+
+The purpose of this guideline is to provide a step-by-step framework for writing and maintaining high-quality documentation for Creative Commons (CC) projects. This guide covers essential sections such as project style guide Preference, Style modification, terminologies, markdown usage. Following these guidelines ensures consistency, clarity, and ease of use for all contributors and users.
+
+## Style guide reference
+
+For general writing style and guidelines, refer to the following upstream style guides:
+
+- [Google Developer Style Guide (Preferred)](https://developers.google.com/style/)
+- [Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/style-guide/welcome/)
+
+## Style preferences modifications
+
+While adhering to the upstream style guides, observe the following modifications:
+- All acronyms must be defined on first use
+- Use active voice wherever possible to improve clarity and engagement.
+- Keep sentences concise and to the point, avoiding jargon unless necessary.
+
+
+## Terminology
+
+Establishing a clear "Terminology" section for Creative Commons (CC)-specific usage is crucial. Below are some proprietary terms and their usage:
+
+- **Creative Commons (CC)**: A non-profit organization enabling sharing and reuse of creative works.
+- **Licenses**: Legal tools that allow creators to specify how their works can be used.
+- **Attribution**: Giving credit to the creator of a work, required by most CC licenses.
+
+
+## Markdown usage
+This section provides guidelines for using Markdown in documentation:
+- For comprehensive documentation on GitHub-flavored Markdown, refer to the [GitHub Markdown Guide](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax).
+- For additional information on the specific Markdown implementation used in Lektor, visit the [Lektor Markdown Documentation](https://www.getlektor.com/docs/content/#markdown).
+- Note: Use code block markup for instructions on installation, deployment, and development, especially to write code commands.
diff --git a/content/programs/contents.lr b/content/programs/contents.lr
index 6e5d1b8a..b706ba5c 100644
--- a/content/programs/contents.lr
+++ b/content/programs/contents.lr
@@ -22,22 +22,20 @@ CC isn't currently participating in Google Season of Docs (GSoD).
### Google Summer of Code
-CC is applying for participation in Google Summer of Code (GSoC) 2024.
+CC will apply for participation in Google Summer of Code (GSoC) 2025.
- [Program website](https://summerofcode.withgoogle.com/)
### Outreachy
-CC isn't participating in the May 2024 internships.
-
-CC will participate in the December 2024 internships.
+CC is participating in the December 2024 cohort.
- [Program website](https://www.outreachy.org/)
- [CC's Outreachy page][outreachycc]
diff --git a/databags/repos.json b/databags/repos.json
index 8cab5dcc..40ed37c6 100644
--- a/databags/repos.json
+++ b/databags/repos.json
@@ -473,7 +473,7 @@
"english_name": "CC Legal Database",
"featured": false,
"id": 133715391,
- "language": "HTML",
+ "language": "CSS",
"license": {
"name": "MIT License",
"url": "https://github.com/creativecommons/legaldb/blob/main/LICENSE"
diff --git a/themes/vocabulary_theme/templates/layout.html b/themes/vocabulary_theme/templates/layout.html
index 727b705d..3568c192 100644
--- a/themes/vocabulary_theme/templates/layout.html
+++ b/themes/vocabulary_theme/templates/layout.html
@@ -1,4 +1,5 @@
+
@@ -46,7 +47,7 @@