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

Build email template #1

Open
3 of 12 tasks
addania opened this issue Jun 14, 2020 · 1 comment · May be fixed by #2
Open
3 of 12 tasks

Build email template #1

addania opened this issue Jun 14, 2020 · 1 comment · May be fixed by #2
Assignees
Labels

Comments

@addania
Copy link
Collaborator

addania commented Jun 14, 2020

PR: #2


Description:
Build the first email template according to:
https://dribbble.com/shots/3032303-Desktop-Email-Client-Concept

Other link for inspiration:
https://dribbble.com/search/email%20client
http://react.pixelstrap.com/endless/email-app/emailDefault

Tasklist:

  • Build the layout
  • Style the template
  • Use quark (box, link)

Questions:

Questions - Part 2 :)

  • should I re-create all the functionality of this page? clickable buttons, submenus with redirects, etc?
  • why elements like, path, navigation icons, etc are ul, li tags (in original page)?
  • should icons be buttons or a tags?
  • if I import fontawesome to project, do I also need to npm install it (I did not yet)? or do I need to add it to dependencies in package.json? or is this done automatically?
  • should we think about theming entire thing in one place, rather then having individual (for example color) styles on each element?
  • should we think of how data will be provided? like list of emails, user info (name, pic) etc? Or these will be hard-coded for now?
@addania addania self-assigned this Jun 14, 2020
@addania addania linked a pull request Jun 14, 2020 that will close this issue
@namjul
Copy link
Owner

namjul commented Jun 17, 2020

How to start a project like this? Some tips? Start with static page, or with component logic, strucure?

The important step is to identify the UI hierarchy, so you ask yourself "what kind of component is this little section here" and they generally will fall into certain groups. You can layout components and primitives/general components and then you can the more specific ones. These can be further categorized into "data entry" and "data display" components. And even further navigation, feedback components.

But just start somewhere and don't overanalyse. Just go with the flow and you will discover the proper boundaries.

Can we use flex box to position items instead of bootstrap grid?

Yes you can create a Flex component with

const Flex = quark('div', { baseStyle: { display: 'flex'})`

// it like
<Flex css={{ justifyContent: 'center' }}>
      <quark.a>a link</quark.a>
      <quark.div>my div</quark.div>
      <quark.p>my p</quark.p>
</Flex>

Can we use https://fontawesome.com/ or https://materializecss.com/icons.html ?

Sure and https://react-icons.netlify.com/ is also an option

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

Successfully merging a pull request may close this issue.

2 participants