how would we handle global sidebar or category wise sidebar?

[amitu]

Currently we handle sidebar by adding sidebar explicitly in each page. We can minimise the code to add it explicitly, but we still have to add it explicitly. How do we globally handle sidebar? And sidebar is just one example, what if we want to globally add items in header, footer, or any other common component?

In most packages we are going to ask people to not import doc-site, but to create a module, and import that module as doc-site: my-doc-site.ftd

-- import: doc-site
export: *

And in our FPM.ftd we can put:

-- package: amitu.com
-- dependency: fifthtry.github.io/doc-site
-- fpm.auto-import: amitu.com/my-doc-site as ds

As you see we do not import doc-site as ds, but my-doc-site as ds.

Now in our my-doc-site.ftd we can create a page component:

-- import: doc-site
export: *

-- component page:
optional caption title:
children children:
optional body body:

-- doc-site.page: $page.title
children: $page.children
body: $page.body

-- doc-site.page.sidebar: 

-- ftd.text: Awesome Sidebar

-- end: doc-site.page.sidebar: 
-- end: doc-site.page

-- end: page

We have create page with same arguments as doc-site.page. Since now my-doc-site has an actual page defined, any attempt to use my-doc-site.page will use this component. The export: * has lower priority than symbols defined in the module explicitly.

[amitu]

The same technique we will now use for updating fonts and colour schemes.

my-ds.ftd:

-- import: my-color-scheme
-- import: my-typography-scheme

-- component page:
optional caption title:
children children:
optional body body:

-- doc-site.page: $page.title
children: $page.children
body: $page.body
colors: $my-color-scheme.colors
types: $my-typography-scheme.types

-- end: doc-site.page

-- end: page

Every package will have to create a my-ds.ftd file, and it will have to be added to auto-import. Instead of ds.page we have to start using my-ds.page.

[amitu]

@Heulitig we will have to do the following:

1. rename inherited.types and inherited.colors in default_bag() to ftd.default-types and ftd.default-colors respectively.
2. add colors and types arguments to container_arguments(), they will be optional.
3. add colors: $ftd.default-colors and types: $ftd.default-typestomain_column()`
4. add colors and types arguments to ds.page, with default value pointing to ftd.default-*.

[amitu]

We need a sample color scheme package, sample type scheme package, a test package using these two, and a writeup about how to create custom color and type schemes.