[Entry/Edit] CSS: Inheritance

[not-a-ethan]

Type of Edit (select all that apply)

Add new content (definitions, codeblocks, etc.)

Description (optional)

Add if the CSS property is inherited.

Code of Conduct

• I agree to follow Codecademy Doc's Code of Conduct

For Maintainers

• Labels added
• Issue is assigned

[not-a-ethan]

I'm willing to make this change I'm just not sure where to put it in each entry.

[not-a-ethan]

Should we have a table with some values like on MDN web docs?

[Dusch4593]

@ethan-master-coding Not too sure about the MDN-like yet. Also, are we sure this is an edit? Do we even have a CSS: Inheritance entry to begin with?

[not-a-ethan]

@Dusch4593 I'm talking about properties. Like the color property is inherited. But the border is not inherited. Im talking about that inheritance for each property. And you can remove the typo lable its not relevant to this.

[Dusch4593]

@Dusch4593 I'm talking about properties. Like the color property is inherited. But the border is not inherited. Im talking about that inheritance for each property. And you can remove the typo lable its not relevant to this.

Right but which entries would get this edit? The title of your issue suggests, to me at least, that you'd like to make an edit in an entry called "CSS: Inheritance" which isn't what you meant, it doesn't seem.

[not-a-ethan]

@Dusch4593 The edit would be to every CSS property in the docs. And for the title, I couldn't think of a better one.

[Dusch4593]

@Dusch4593 The edit would be to every CSS property in the docs. And for the title, I couldn't think of a better one.

Oof that's a lot of files. What if we did this to start?

• Create a CSS concept entry called "Inheritance" (since it is a pretty notable aspect of CSS properties)
• Make that edit to 3-4 exiting CSS entries (color, border, etc.)

As for the title, no worries! 😊

[not-a-ethan]

@Dusch4593 So we just have 1 big page that has all the properties and their inheritance. Got it.

[Dusch4593]

@Dusch4593 So we just have 1 big page that has all the properties and their inheritance. Got it.

Maybe that could be written as a markdown table with links to any appropriate Docs entries.

Also, this "Inheritance" should have a breakdown between inherited properties and non-inherited properties.