JoomlArt Forums 32,862 posts

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#158270

To be able to edit these files directly on the backend would be nice.

[ghostik Friend ghostikJoin date: April 2010Posts: 71Downloads:2Uploads:1 Thanks: 2 Thanked: 11 times in 4 posts]

#369972

my opinion: why?
when I make website for anyone, i make complete website with styled css, layouts, …
client would not be able to easy make change of deisgn, becouse he could design completely break

[dpk Friend dpkJoin date: June 2006Posts: 129Downloads:0Uploads:0 Thanks: 19 Thanked: 2 times in 1 posts]

#370050

<em>@ghostik 212620 wrote:</em><blockquote>my opinion: why?
when I make website for anyone, i make complete website with styled css, layouts, …
client would not be able to easy make change of deisgn, becouse he could design completely break</blockquote>

They already have the ability to break the design if they have administrator accounts. What you are describing is an access level problem to be solved with the ACL and proper permissions for users according to their roles. Not all clients are the same. Some are fully capable of handling design and wish to do so. Others you might need to deny access to templates on the backend.

For those who need to work on design, it’s a convenience to be able to edit HTML and CSS in the backend. And as long as T3 has style and layout code in different places (the plugin and template folders), making the relevant files accessible per template in the backend would have a centralizing effect — it would make design customization much easier to learn and do.

[Author]

Posts