Closed joelanman closed 1 year ago
This gets an up-vote from me 👍
At the National Lottery Heritage Fund we are using the prototype-kit 'unbranded'.
Such as HMRC Frontend
Am I correct in believing that would more nicely separate the bundled GOVUK Frontend from our organisation specific frontend (assets, styles, scripts)?
Is there a manual step to import them? (And therefor be in the outputted css file used by the prototype kit?)
This is my working document https://docs.google.com/document/d/1NrN6GmKDvQLoEEJj_hjSpb8GJNLH8KZqm-1PE1D9d4U
And this is the channel I advise people in which leads into that documentation https://ukgovernmentdigital.slack.com/archives/C044HKGJX1T
@ruthhammond @joelanman I've separated out the previous plugin assurance doc and the Create a plugin draft, as it was getting a little confusing.
@nataliecarey we've put together a structure for the create a plugin guide, which includes a tutorial aspect (create your first plugin) and more technical parts for the package.json and config file.
Are you able to build on the draft with the technical elements and the example plugin you walked me through before? It would be great to take the user through that process. Thanks!
plugin guidance is now online:
What
Add documentation for Plugins
Plugin notes:
https://docs.google.com/document/d/11yuUfSLT47yunW5HHTraBV1KBxbE5cYxO-NNb935Iq0/edit#
Create a plugin guide draft: https://docs.google.com/document/d/1xLETvJApivoUiBw4enajmEKYp-07ItAQW0O7cBuesws/edit#
PR: https://github.com/alphagov/govuk-prototype-kit-docs/pull/231
Why
So people can write and use them
Who
Done when