[ 
https://issues.apache.org/jira/browse/SYNCOPE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942769#comment-15942769
 ] 

Andrea Patricelli commented on SYNCOPE-1019:
--------------------------------------------

[~amsonu99] glad to hear about your interest. Please subscribe to Apache 
Syncope DEV mailing list if you want to participate and have technical 
questions, to participate to the GSOC you should register 
[here|https://summerofcode.withgoogle.com/] and follow google.
Though is a good way to know you all please read below ;)
[DISCLAIM] This Jira issue is NOT meant to subscribe proposals or to subscribe 
to the GSOC! You should use official Google channel.
[~menuka94] Well, I suggest to read carefully 
[this|http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/]

> Template mechanism for Enduser UI
> ---------------------------------
>
>                 Key: SYNCOPE-1019
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1019
>             Project: Syncope
>          Issue Type: New Feature
>          Components: enduser
>            Reporter: Francesco Chicchiriccò
>              Labels: gsoc2017
>             Fix For: 2.1.0
>
>
> Provide a mechanism for defining templates (in terms of HTML, CSS and image 
> files) to simply the appearance customization of the Enduser UI.
> The the goal of the issue is to provide a way to:
> - avoid HTML code duplication, and define reusable components.
> - define an HTML template mechanism which aim is to improve customizability 
> of the enduser (enduser is meant to be customized and extended, it is not a 
> finite product, but a proposal from which to start a new implementation).
> - exploit as much as possible code re-usability features provided by 
> AngularJS (if possible).
> - if needed review actula  CSS implementation, in order to better fit the new 
> template mechanism
> - do NOT compromise (or change) enduser functionalities at all! Buttons, 
> selects, wizard and other components should preserve their role and function; 
> the core logic should remain the same, though enduser is open to discuss 
> improvements also in that way ;)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to