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

Feature Request: Front-end editing #97

Open
newlocalmedia opened this Issue Jul 23, 2014 · 13 comments

Comments

Projects
None yet
@newlocalmedia

newlocalmedia commented Jul 23, 2014

Ideally you should be able to do almost everything on the front end that you can do on the back.

Being able to edit the main content of a page on the front end is the most important front end feature to start with.

Having a quick way to switch between the front and back ends would also be an improvement.

@maximilianmikus

This comment has been minimized.

maximilianmikus commented Jul 28, 2014

+1

@saschadube saschadube added this to the Future milestone Jul 29, 2014

@MacWordPress

This comment has been minimized.

MacWordPress commented Jul 30, 2014

+1

@realrandal

This comment has been minimized.

realrandal commented Jul 31, 2014

Maybe also frontend inline editing style?

Functionality like NoNumber Better Preview. Would be nice. "View Site" link is not the best way, especially it's hidden in user menu. So it might be as button on toolbar to Preview edited content directly on site. Additionally other views current app or even menu items related to it.

@pepperstreet

This comment has been minimized.

pepperstreet commented Sep 13, 2015

+1
I agree on "inline editing" for frontend.
Probably the backend can be tailored for clients by roles and permissions.

@peterthomashorn

This comment has been minimized.

peterthomashorn commented Jan 21, 2016

While I was thinking about front-end editing in the last days, I read an interesting article about it yesterday. It points out how front-end editing actually undermines the established concept of separating front- and back-end or in other terms content from design. Also, front-end editing would not add substantial extra value (actually new functionality) like other goals on the roadmap. While I do not have experience implementing specifically such a feature, I think the effort to maintain the necessary code is (in my eyes) not worth the gain. Plus it would feel like bloat in the attractively slim Pagekit. Just my two cents.

@YoKoGFX

This comment has been minimized.

YoKoGFX commented Apr 29, 2016

+1

@oneumyvakin

This comment has been minimized.

oneumyvakin commented Apr 30, 2016

-1

Agree with @alomvar useless spent of efforts.

@StudioNameHere

This comment has been minimized.

StudioNameHere commented Apr 30, 2016

Agreeing with @alomvar -1

@edirpedro

This comment has been minimized.

edirpedro commented May 12, 2016

Front-End editing is for Designers who doesn't want to code or contract a coder, Period!

It's a tool hard to maintain and not useful to the client who needs to focus on the content of their website and not on page design that was already built to them. Always when I offered too many options to customize the page for my clients, they built something very problematic to their users. They don't understand about design and can't understand all the little things that makes a webpage great to end users. At the end, is my fault their website is running bad.

Only very few situations this could be useful, like Medium.com does on the article editor, but notice that the tool is focused on writing the article and not designing a full page, there are pre-built types of content with a specific design to choose, you can't change the structure, just choose one to use.

@amdad

This comment has been minimized.

amdad commented May 12, 2016

@edirpedro You just don't know what this issue is about. Not that kind of frontend editing.

@rudivdme

This comment has been minimized.

rudivdme commented May 24, 2016

+1
Use this: http://getcontenttools.com/

@leannephillipz

This comment has been minimized.

leannephillipz commented Jul 14, 2016

What might be nice is new user types E.g. "Site Owner" and "Site Designer"

The "Site Designer" user could have access to a few more features, like templates and CSS.

Whereas the "site owner" has admin access, but can not access design features (keeping it for the user).

@tobbexiv

This comment has been minimized.

Contributor

tobbexiv commented Jul 14, 2016

What might be nice is new user types E.g. "Site Owner" and "Site Designer"
The "Site Designer" user could have access to a few more features, like templates and CSS.
Whereas the "site owner" has admin access, but can not access design features (keeping it for the user).

This is already possible: Create own roles and assign them specific rights. Also this is a little bit offtopic.

Regarding the topic: A simple editor to edit the code like in the backend might be ok in my opinion. The backend preview does not take theme specific styling into account so for me it looks different in the background preview and the real site. so an editor where I can easily switch between real preview and edit without the need of having multiple tabs open would be nice. Additionally it is then possible to make small changes without being required to login to the backend and find the page there ...

But I yould not include a theme designer here. Only the backend editor for sites (and maybe widgets).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment