Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature suggest: pages on datasets #50

Open
ted-strauss-K1 opened this issue Mar 24, 2017 · 1 comment
Open

Feature suggest: pages on datasets #50

ted-strauss-K1 opened this issue Mar 24, 2017 · 1 comment

Comments

@ted-strauss-K1
Copy link

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.

@torfsen
Copy link
Contributor

torfsen commented May 11, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants