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
In addition to the features already supported by this awesome extension, I would be interested in having a page added for all datasets by default.
Sketch of the feature requirements:
Datasets currently have a description field. This field would support markdown and treated as the dataset's page source. This field's textbox would display using the editor (medium or ckeditor).
A new tab called 'info' (or something) would be added to the dataset template, and display the description content rendered according to the extension settings (supporting richer content than the standard ckan description field)
The info tab would allow content authors to provide more thorough documentation for the dataset.
I realize that half or more of this feature request is actually related to a custom theme. I'd be interested to hear any feedback about how this feature could be implemented using this extension out of the box. And, if other people would find that a useful addition to the core ckan.
The text was updated successfully, but these errors were encountered:
I'm not sure which benefits this would have over the standard description field of a package. If I understand you correctly then it's about two different (but related) things:
Providing a better editor for the description field. This would be very nice, but CKAN core would probably be a better place for that change.
A more flexible display of information for packages ("supporting richer content than the standard ckan description field") -- I don't understand that point, what features beyond the existing Markdown support are you missing?
In addition to the features already supported by this awesome extension, I would be interested in having a page added for all datasets by default.
Sketch of the feature requirements:
I realize that half or more of this feature request is actually related to a custom theme. I'd be interested to hear any feedback about how this feature could be implemented using this extension out of the box. And, if other people would find that a useful addition to the core ckan.
The text was updated successfully, but these errors were encountered: