Giter VIP home page Giter VIP logo

Comments (6)

jessevdk avatar jessevdk commented on July 23, 2024

I'm not sure I understand. A new section of what? cldoc does not support markdown titles as special segments, they are just going to be part of the documenting element. If you want to make special documentation pages, use categories. Am I misunderstanding something?

from cldoc.

rhdunn avatar rhdunn commented on July 23, 2024

What I am trying to do here is add a license to the documentation files (Copyright line and which license (Apache, Creative Commons, etc.) the documentation is licensed under). I tried this above, e.g.:

Copyright (C) ...

This file is licensed under the Creative Commons Attribution (CC-BY) 2.0 license.

#<cldoc:id>

Brief description.

However, cldoc did not like that (it complained it could not find a #<cldoc:id>). Therefore, I added a License section at the end:

#<cldoc:id>

Brief description.

# License

This file is licensed under the Creative Commons Attribution (CC-BY) 2.0 license.

Copyright (C) ...

from cldoc.

jessevdk avatar jessevdk commented on July 23, 2024

Ideally, there would be support for some commented sections in markdown. The only thing that I found that people tend to do, is to use xml/html style comments (i.e. ), which will still end up in the output, but are obviously then not rendered. Would this be an acceptable solution for you?

from cldoc.

rhdunn avatar rhdunn commented on July 23, 2024

I would prefer it if there were a more markdown friendly approach (hence the use of sections).

Another approach I could do is use a YAML front section like is done for jekyll-based markdown files, where I do, e.g.:

---
_copyright_: "Copyright ..."
_license_: "CC-BY-SA 3.0"
---

If you do not want to make cldoc support this, I can run the markdown through a filter that will remove the YAML front section before it gets passed to cldoc.

from cldoc.

jessevdk avatar jessevdk commented on July 23, 2024

I don't want to hijack markdown semantics for special purposes. This also seems like quite a specific use case, so I'm not really willing to introduce yaml into the markdown file just for this. If you want to go the filter way, you can use --merge-filter.

from cldoc.

rhdunn avatar rhdunn commented on July 23, 2024

Fair enough.

from cldoc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.