Skip to content

chore(css): Add CSS properties page #39932

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

chore(css): Add CSS properties page #39932

wants to merge 5 commits into from

Conversation

bsmth
Copy link
Member

@bsmth bsmth commented Jun 13, 2025

Description

This is a basic landing page for CSS props.

Motivation

We don't have a page for props yet, and the team are looking to include a CSS properties page in site navigation in the very near future. This is an attempt at a starting point for this.

@bsmth bsmth requested review from a team as code owners June 13, 2025 12:32
@bsmth bsmth requested review from chrisdavidmills and pepelsbey and removed request for a team June 13, 2025 12:32
@github-actions github-actions bot added Content:CSS Cascading Style Sheets docs size/l [PR only] 501-1000 LoC changed labels Jun 13, 2025
Copy link
Contributor

github-actions bot commented Jun 13, 2025

Preview URLs

Flaws (1)

URL: /en-US/docs/Web/CSS/Properties
Title: CSS properties
Flaw count: 1

  • macros:
    • Macro produces link /en-US/docs/Web/CSS/--_star_ which is a redirect

(comment last updated: 2025-06-13 12:58:22)

Copy link
Collaborator

@Rumyra Rumyra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one nit

@bsmth bsmth requested a review from Rumyra June 13, 2025 12:56
@Josh-Cena
Copy link
Member

Do we really want to hand-maintain this? This seems destined to go out of date. Can it be a macro instead?

@bsmth
Copy link
Member Author

bsmth commented Jun 13, 2025

Do we really want to hand-maintain this? This seems destined to go out of date. Can it be a macro instead?

No, I don't think we want to hand-maintain it, I think this will indeed be a macro (list pages by page type?) but I'm scaffolding it one time based on what we have per page type to get this going.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:CSS Cascading Style Sheets docs size/l [PR only] 501-1000 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants