3.2.2 • Published 6 years ago

@nib-components/content-markdown v3.2.2

Weekly downloads
38
License
-
Repository
-
Last release
6 years ago

Setting up your component

Delete this section after you've setup the component

Before the component is accepted into the DLS:

  1. Github: Create the repository under your own username/organisation

When the component is accepted into the DLS:

  1. Github: Transfer ownership of the repository to frontend
  2. BuildKite: Create a New Pipeline
  3. BuildKite: Enter the following settings:
  • Name: content-markdown
  • Git Repository: git@git.nib.com.au:frontend/content-markdown.git
  1. BuildKite: Remove the default Step and add a Read steps from repository step
  • And add cd deploy && bundle install && bundle update sceptre sceptre-dotnet sceptre-app && bundle exec sceptre-app pipeline upload to the Commands to run textbox
  • And add os=linux to the Agent Targeting Rules textbox
  1. BuildKite: Create Pipeline and follow the instructions to add the webhook to GithubEnterprise
  2. BuildKite: Go to Settings
  • Check Build pull requests from third-party forked repositories and click Save Github Enterprise Settings
  • Copy the Markdown badge from Settings and past it below.
  1. Github: Edit the readme to remove these steps and kick off a New build
  2. Github: Protect the master branch
  • Go to Settings > Branches
  • Choose the master branch
  • Check Protect this branch
  • Check Require status checks to pass before merging
  • Check Include administrators and Require branches to be up to date before merging
  • Check all Status checks found in the last week for this repository

@nib-components/content-markdown

Build status dependencies Status

A content-markdown component.

Installation

npm install --save @nib-components/content-markdown

Usage

import ContentMarkdown from '@nib-components/content-markdown';

const Markdown = ContentMarkdown.extend`
  font-size: .8125em;
  line-height: 1.5385;
  h3 {
    padding: 0 0 .25em;
  }
  a {
    color: #00b1c0;
  }
`;

<Markdown content={content}/>

Properties

content

The markdown content to be displayed.

Required. A string.

className

The className can be passed to add more customisation.

Optional. A string.

Change log

1.0.0

Initial release.

Contributing

You can edit the files in ./src, whilst running npm run watch. This will compile for the ./dist folder.

3.2.2

6 years ago

3.2.1

6 years ago

3.2.0

7 years ago

3.1.14

7 years ago

3.1.13

7 years ago

3.1.12

7 years ago

3.1.11

7 years ago

3.1.10

7 years ago

3.1.9

7 years ago

3.1.8

7 years ago

3.1.7

7 years ago

3.1.6

7 years ago

3.1.5

7 years ago

3.1.4

7 years ago

3.1.3

7 years ago

3.1.2

7 years ago

3.1.1

7 years ago

3.1.0

7 years ago

3.0.22

7 years ago

3.0.21

7 years ago

3.0.20

7 years ago

3.0.19

7 years ago

3.0.18

7 years ago

3.0.17

7 years ago

3.0.16

7 years ago

3.0.15

7 years ago

3.0.14

7 years ago

3.0.13

7 years ago

3.0.12

7 years ago

3.0.11

7 years ago

3.0.10

7 years ago

3.0.9

7 years ago

3.0.8

7 years ago

3.0.7

7 years ago

3.0.6

7 years ago

3.0.5

7 years ago

3.0.4

7 years ago

3.0.2

7 years ago

3.0.1

7 years ago

3.0.0

7 years ago

2.1.0

7 years ago

2.0.1

7 years ago

2.0.0

7 years ago

1.0.0

7 years ago

0.0.2

7 years ago

0.0.1

7 years ago