Repalce pseudo-classes with pseudo-elements

[stevenjoezhang]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines.
• Tests for the changes was maked (for bug fixes / features).
  • Muse | Mist have been tested.
  • Pisces | Gemini have been tested.
• Docs in NexT website have been added / updated (for features).

PR Type

What kind of change does this PR introduce?

• Bugfix.
• Feature.
• Code style update (formatting, local variables).
• Refactoring (no functional changes, no api changes).
• Build related changes.
• CI related changes.
• Documentation content changes.
• Other... Please describe:

What is the current behavior?

Issue resolved: N/A

What is the new behavior?

• Screenshots with this changes: N/A
• Link to demo site with this changes: N/A

How to use?

In NexT _config.yml:

...

Does this PR introduce a breaking change?

• Yes.
• No.

[stevenjoezhang]

Oh, how careless I am ... This class name is spliced out

[stevenjoezhang]

I see. Now we got several page/post types:
post: picture | quote
page: categories | tags | schedule

[1v9]

@stevenjoezhang Yes, and // TODO: Refactor. is right 😅

[todo]

Refactor.

hexo-theme-next/source/css/_common/components/post/post-type.styl

Lines 1 to 6 in 6f483bb

	// TODO: Refactor.
	.page-home, .page-post-detail {
	.post-type-quote {
	This conversation was marked as resolved by 1v9
	.post-header,

---

This comment was generated by todo based on a TODO comment in 6f483bb in #953. cc @theme-next.

[stevenjoezhang]

I'm still confused by post-type-quote 😂
Let's deal with it later

[1v9]

@stevenjoezhang Low Low priority ✔