You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Markdown defines the 1st level headers as headers with "===" under them and 2nd level - with "-------" (or with one "#" character in the beginning for 1st level and 2 "##" for 2nd level).
When creating the content index, JSDuck currently recognizes only the 2nd level headers.
Introduction
============
Ext Gantt allows you
Basic features
==============
Weekends, highliting, skeep during DD
how to make it plain (no holidays at all)
Defining availability for individual days
=========================================
weekday, day override, week day override
parent - child
Availability for tasks
----------------------
Availability for resources
--------------------------
For example, for the text above the following content will be generated:
Would be great if it will also include 1st level headers in the content.
Thanks, Nickolay
The text was updated successfully, but these errors were encountered:
Thats intentional, because the first level header is intended as the title of the whole guide. It's supposed to be used only once - at the beginning of the guide.
Hm.. Then perhaps a 3rd level headers could be included in the contents? Right now only 2nd level headers are included in the content, meanwhile its pretty common to have sections and sub-sections in the guides.
Markdown defines the 1st level headers as headers with "===" under them and 2nd level - with "-------" (or with one "#" character in the beginning for 1st level and 2 "##" for 2nd level).
When creating the content index, JSDuck currently recognizes only the 2nd level headers.
For example, for the text above the following content will be generated:

Would be great if it will also include 1st level headers in the content.
Thanks, Nickolay
The text was updated successfully, but these errors were encountered: