luccasa / design-system Goto Github PK

do it after #39 and #38 so its deployed under /prisme

• create a class GuidelinePage extends Page where we can easily define a page and its associated markdown
• create class FeaturePage extends Page with additional property guidelines: GuidelinePage so we can link a feature (component n stuff) to a guideline page
• add a router-outlet for guidelines, when calling featurePage.toRoute() it injects the guideline in the page

Bonus : ng g guidelines components/listing/xxx
generate the .md in /src/guidelines/component/listing/xxx/xxx.guidelines.md
generate the right GuidelinePage at the right place

for this moqup

may need to rewrite a lot of stuff, or extract the info member

If you navigate between examples with TS code and without TS code, pri-examples doesn't update its display of codeTabs-menu.

to add an example to a feautre you can use the ng g example schematic, but then, you need to manually update the examples list in the feature file. it would be super more betterer if the schema updated the file on its own

the front end test references this repo, i think the demo page of lucca-front also does

home page still says design-system

http://prisme.lucca.io/ressources/colors

c'est #9acd32 et pas #828db9

right now its configured to deploy to luccasa.github.io/design-system, it must change to deploy to uccasa.github.io/prisme

like we do with the theme, parse the scss form @lf/icons to get the latest icons list

then update this page

thats gonna be the part witrh the most unintended consequences i think

use angular universal for prisme so the server is capable of some server side rendering allowing for preview url sharing

see wot i did on meteo-fiable

right now pages are defined in xxx.router and sometimes its a mega big file

what would be better is if the page was defined next to the component it uses.

also we could define a generic PageComponent that every page could extend

the ng g feature does all file creation but

• import of the newly created feature module in the parent module - here
• add feature page to parent group page - here

La documentation de thème devrait inclure le nom de la map (eg. navSide), le chemin (eg. components.navSide). Il faudrait aussi faire mieux ressortir les maps au sein du thème

some features have an associated markdown file to explain some guidelines regarding the thing. if we had a schema to generate all files and stuff, it would be nice

either

• ng g guidelines components/loaders/gauge creates the mardown file guidelines/components/loaders/gauge.md

or

• ng g feature components/loaders/gauge --guidelines creates a gauge feature and md file and links the 2

prefix ds doesnt make sense anymore, find a better prefix and use it

• pr
• p
• prism

currently, the script that generates the docs for package ng makes the file name be the file under node_modules

    "fileName": "node_modules/@lucca-front/ng/lib/option/item/option-item.model.d.ts",

it'll be better if it linked to the file hosted on githubs

http://prisme.lucca.io/components/layout/templates

Some might say we are missing a Dasherize() somewhere

might lead to some circular dependency shenanigans