abpframework / abpframework/abp
CmsKit: Meta information for SEO
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 3.7k
- Avg merge
- 15h 32m
- Merged PRs (30d)
- 106
Description
Is there an existing issue for this?
- I have searched the existing issues
Is your feature request related to a problem? Please describe the problem.
I think it would be a good addition if blog posts and pages get the ability of adding some meta information to be more SEO friendly.
For example:
Description
Take short description and put that into <meta name="description" content="YOURSHORTDESCRIPTION" />
I think a configuration would be good to control whether to apply the logic or not. Maybe the user has something else in place.
Keywords
Take tags and put that into <meta name="keywords" content="YOURTAG1,YOURTAG2" />
I think a configuration would be good to control whether to apply the logic or not. Maybe the user has something else in place.
Title
Take the Title and set ViewBag.Title to that
I think this would need something additional. Maybe you want to have something like "CompanyName - " + EntityTitle
Describe the solution you'd like
The maybe-overkill solution
There would be multiple ways of archiving this. Here's just an idea here to get discussion going.
Add a new page as a submenu item of CMS for meta information. The new page prodives CRUD functionality for setting meta stuff like described above.
The entity could look something like this:
- string input -> EntityType (set if you want to apply logic for a specific entity type. leave empty to apply to all)
- dropdown input -> MetaAttribute enum info (Title, Description, Keywords, CustomMetaProperty) where the first three are as described above
- string input -> if CustomMetaProperty, you can set things like
og:titleif you want to support Open Graph stuff - dropdown input -> dropdown for supported properties to set + the option
SetManually
If SetManually is set -> You need to manually define the attribute when creating/ editing the specified type.
Related components would need to respect what's been set here.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or tests. Start by mapping the CmsKit blog posts, pages, and related components, then clarify whether the scope is configurable metadata or a CRUD page. Done should include agreed behavior for descriptions, keywords, titles, custom properties, and manual overrides.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100