Skip to content
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

Make Settings area customizable #7

Closed
azeller opened this issue Jan 25, 2021 · 3 comments
Closed

Make Settings area customizable #7

azeller opened this issue Jan 25, 2021 · 3 comments

Comments

@azeller
Copy link

azeller commented Jan 25, 2021

When activating this plugin, it will display above the content in a very dominant way. MODX is about customizing the user-experience as close to the clients needs as possible. I'd like to move the SEO settings per resource either below the content or have the SEO-Section collapsed. Otherwise the most important part (the content) will always display belog the SEO section.
Would be glad if we could just choose to move it some place else, much like Tagger does it.

@sdrenth
Copy link
Contributor

sdrenth commented Jan 28, 2021

@azeller Feel free to submit a Pull Request with the desired changes, we encourage everyone to collaborate and improve all extras together.

@deJaya
Copy link

deJaya commented Aug 16, 2021

I'd really like to see some flexibility with this too.

I think it's a great extra, but I can't deploy it as it is because it would cause too much confusion for users. Even for a seasoned MODX manager it's just too prominent and takes up too much of the Resource real estate.

I'd like to see it in its own dedicated tab but even if the SEO block was minimised by default - that would be a start.

I'm afraid I don't have the Github skills to provide a pull-request.

@ilyautkin
Copy link
Contributor

SEO-Section now display below content section on resource. I'm closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants