search

WeAreSnook / human-services

Extensions proposed by the English Local Government Association (LGA) and the local government OpenCommunity project to the OpenReferral standard for human services data. Schema generator code is given to express the schema in various formats. Data conversion routines to make it conform to the standard. API that serves the data in a format compliant with the standard.
0 stars 1 forks source link

Build front end page templates #86

Open anandamaryon opened 3 years ago

anandamaryon commented 3 years ago

Templates for pages attached and viewable here: https://www.figma.com/file/mlvnzbhd51X7DUtxMLAaT1/ORUK-page-templates?node-id=0%3A1

Content page template_ content page

Homepage template_ home page

Section landing page template_ landing page

PorismDominicSkinner commented 3 years ago
kingdomlevel commented 3 years ago

^ Thanks for sharing the above - will be very useful as we move in to front-end components next week but also for creating the content structures (I'm doing this today!).

I just wanted to flag the couple of page structure types from the current prototype that I don't think we have covered in the page templates (at this point at least!):

List-type Page

image

Community Page

I think we're all aware of the work being done here but writing here to keep myself right. There are 2 versions on the current prototype, one with left sidebar, one without - this will need clarified at some point. image

Who's Using Open Referral UK

image

anandamaryon commented 3 years ago

^ Thanks for sharing the above - will be very useful as we move in to front-end components next week but also for creating the content structures (I'm doing this today!).

I just wanted to flag the couple of page structure types from the current prototype that I don't think we have covered in the page templates (at this point at least!):

Good spot, I wasn't sure how deep to go but I can add those templates too 👍 I might wait until we're a little more settled on the designs for those though, as they are still in flux.

anandamaryon commented 3 years ago

@kingdomlevel @UsmanAfzal

Updated page templates (I think this is all of them now but do tell if I've missed any!)

Also let me know if anything needs discussion or more detail needs ironing out.

Content page: Article (e.g About ORUK) template_ content page_ article

Content page: Case study detail template_ content page_ Case study

Content page: Join now template_ content page_ Join now

Content page: Who's using template_ content page_ Who's using

Home page template_ home page

Section landing page template_ landing page

Updated @UsmanAfzal (21 Apr)

anandamaryon commented 3 years ago

@yemijaiyeola Assigned this to you because I'm not sure how your splitting up the work but feel free to assign again

ailsaleen commented 3 years ago

@yemijaiyeola should we break this task down into smaller components?

That way we can prioritise them independently. Tomorrow in planning it would be great to break tickets down into what's needed for pre-launch, soft-launch etc (definitions in the weekly deck we showed on Friday here: https://docs.google.com/presentation/d/1Te6MTRXO4ScURtLXpOwaSzXvpJti9H9uDVLFIRVLMUw/edit#slide=id.gd25d70a68a_0_17)

yemijaiyeola commented 3 years ago

Yes, breaking this down is a great Idea. Will try and do that ahead of planning tomorrow.

Yemi

On Mon, 19 Apr 2021 at 15:47, ailsaleen @.***> wrote:

@yemijaiyeola https://github.com/yemijaiyeola should we break this task down into smaller components?

  • A ticket for each remaining page that needs a front end template (which ones do we have left?)
  • A ticket for visual styling

That way we can prioritise them independently. Tomorrow in planning it would be great to break tickets down into what's needed for pre-launch, soft-launch etc (definitions in the weekly deck we showed on Friday here: https://docs.google.com/presentation/d/1Te6MTRXO4ScURtLXpOwaSzXvpJti9H9uDVLFIRVLMUw/edit#slide=id.gd25d70a68a_0_17 )

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/WeAreSnook/human-services/issues/86#issuecomment-822526249, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASL4FUAMAZ2WGFLRZLL33QTTJQ7BHANCNFSM42SSRCRQ .

-- This email is sent on behalf of We Are Snook Limited ("Snook") and is strictly confidential and intended solely for the addressee(s).  If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully;  (ii) contact Snook immediately on +44(0)203 880 7600 quoting the name of the sender and the addressee then delete it from your system. Snook has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted.  You should scan attachments (if any) for viruses.   We Are Snook Limited, registered in Scotland under number SC373366 with a registered address of 84 Miller Street, Glasgow G1 1DT.  A Northgate Public Services company.

ailsaleen commented 3 years ago

Happy to chat about it, I made two just as placeholder (feel free to modify, keep or whatever): https://github.com/WeAreSnook/human-services/projects/4#card-59362074 https://github.com/WeAreSnook/human-services/projects/4#card-59361599

On Mon, Apr 19, 2021 at 3:59 PM yemijaiyeola @.***> wrote:

Yes, breaking this down is a great Idea. Will try and do that ahead of planning tomorrow.

Yemi

On Mon, 19 Apr 2021 at 15:47, ailsaleen @.***> wrote:

@yemijaiyeola https://github.com/yemijaiyeola should we break this task down into smaller components?

  • A ticket for each remaining page that needs a front end template (which ones do we have left?)
  • A ticket for visual styling

That way we can prioritise them independently. Tomorrow in planning it would be great to break tickets down into what's needed for pre-launch, soft-launch etc (definitions in the weekly deck we showed on Friday here:

https://docs.google.com/presentation/d/1Te6MTRXO4ScURtLXpOwaSzXvpJti9H9uDVLFIRVLMUw/edit#slide=id.gd25d70a68a_0_17 )

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/WeAreSnook/human-services/issues/86#issuecomment-822526249 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ASL4FUAMAZ2WGFLRZLL33QTTJQ7BHANCNFSM42SSRCRQ

.

-- This email is sent on behalf of We Are Snook Limited ("Snook") and is strictly confidential and intended solely for the addressee(s). If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully; (ii) contact Snook immediately on +44(0)203 880 7600 quoting the name of the sender and the addressee then delete it from your system. Snook has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted. You should scan attachments (if any) for viruses.

We Are Snook Limited, registered in Scotland under number SC373366 with a registered address of 84 Miller Street, Glasgow G1 1DT. A Northgate Public Services company.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/WeAreSnook/human-services/issues/86#issuecomment-822535637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHHUJJMAYHUYBRZBHV5ORPDTJRALHANCNFSM42SSRCRQ .