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

"Root" core container component (data provider) #36

Closed
2 tasks done
arcticicestudio opened this issue Nov 20, 2018 · 0 comments
Closed
2 tasks done

"Root" core container component (data provider) #36

arcticicestudio opened this issue Nov 20, 2018 · 0 comments

Comments

@arcticicestudio
Copy link
Contributor

arcticicestudio commented Nov 20, 2018

Related epics: #26

The Root core container is the first and one of the important main data provider React components of this project. It represents the base element and entry point that wraps the all custom application components and serves as a data provider later on. Some of the tasks in the future will be to

Tasks

  • Initially implement core container component Root that renders the passed children within a React.Fragment.
  • Initially implement the Landing root/index page component and render an self-closing Root component.
@arcticicestudio arcticicestudio added this to the 0.1.0 milestone Nov 20, 2018
@arcticicestudio arcticicestudio self-assigned this Nov 20, 2018
arcticicestudio added a commit that referenced this issue Nov 20, 2018
It renders the passed `children` within a `React.Fragment`.

The `Root` core container is the first and one of the important main
data provider React components of this project. It represents the base
element and entry point that wraps the all custom application components
and serves as a data provider later on. Some of the tasks in the future
will be to

- provide context props and functions for the global theme through
  styled-components (1) `ThemeProvider` (3) component
- inject global styles through styled-components
  `createglobalstyle` (3) function including typography (GH-2) related
  data like application-wide used fonts
- possibly data stores for state management libraries like MobX (4)

References:
  (1) https://styled-components.com
  (2) https://www.styled-components.com/docs/api#createglobalstyle
  (3) https://www.styled-components.com/docs/api#themeprovider
  (4) https://mobx.js.org

GH-36
arcticicestudio added a commit that referenced this issue Nov 20, 2018
This commit is the initial implementation and renders an self-closing
"Root" component.

GH-36
arcticicestudio added a commit that referenced this issue Nov 20, 2018
…ontainer-component

"Root" core container component (data provider)
@arcticicestudio arcticicestudio removed their assignment Nov 20, 2018
arcticicestudio added a commit that referenced this issue Dec 2, 2018
To provide the global theme (1), the `ThemeProvider` (2) component has
been implemented into the `Root` core container component (3). The
global theme, placed in `src/styles/themes` is passed to the provider to
make the theme globally available.

References:
  (1) https://www.styled-components.com/docs/advanced#theming
  (2) https://www.styled-components.com/docs/api#themeprovider
  (3) #36

Associated epics: GH-51
GH-53
@arcticicestudio arcticicestudio mentioned this issue Dec 3, 2018
3 tasks
arcticicestudio added a commit that referenced this issue Dec 4, 2018
Both the context consumer and provider components have been implemented
in the `Root` core container component . The consumer is exported which
can then be imported in any component to consume the provided values.

References:
  (1) #36

Associated epic: GH-51
GH-57
arcticicestudio added a commit that referenced this issue Dec 6, 2018
This is the default layout of Nord Docs that consists of the `Root` core
container (1) as root element and the core components representing the
header (2), the main page container (3) and the footer.

References:
  (1) #36
  (2) #64
  (3) #65

Associated epic: GH-63
Depends on GH-65
Relates to: GH-36, GH-64
GH-66
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant