Git Product home page Git Product logo

docs's Introduction

docs's People

Contributors

bobdenotter avatar boorj avatar carsonf avatar cdowdy avatar dadaxr avatar eduardomart avatar evertalbers avatar gdmac avatar gwendolenlynch avatar i-valchev avatar ichag avatar jadwigo avatar maelstromeous avatar marcelfw avatar mcdennem avatar michaelborn avatar nestordedios avatar peterboorsma avatar phillippohlandt avatar pinpickle avatar pvankouteren avatar raistlfiren avatar rarila avatar rixbeck avatar rossriley avatar sahassar avatar simongroenewolt avatar svanterichter avatar xiaohutai avatar zomars avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs's Issues

Add documentation for relations/sortorder

It would be nice to have some more examples in the documentation for related items, like sort order, show only future related items and combining things like that.

Revert HTML fieldtype options untill 2.0.x

Recently in the 2-beta, options to configure the html fieldtype (with a ckconfig setting) were introduced.
However, this needs a more generic approach, as i already have a use-case where you want to set options for a date-type of field as well.

I propose we make a more generic option to pass javascript settings to a field, and for the time being remove the mention of ckconfig from the docs, just in case that option is going to be used a lot, and we get complaints on a change of syntax afterwards.

e.g. 11ca3cc

Remove default taxonomies notice

The documentation here should be updated: http://docs.bolt.cm/taxonomies

Specifically this part:
"Note: If you’d like to just display the ‘default’ taxonomies in your templates, you can use this to include it: {% include '_sub_taxonomylinks.twig' with {record: record} %}"

There doesn't seem to be a "_sub_taxonomylinks.twig" included in the release.

Missing sample code for content type.

In source/content.md there seems to be some sample code missing after the following line.

To add a listing of these news items to the website, edit the twig template view/index.twig. Most likeley, it'll contain an include for a header and some other things. Add the following to the HTML-code, preferable somewhere below the header section:

Replace "css" in SimpleForms readme

The SimpleForms readme says:

mail_template: assets/simpleforms_mail.twig - The Twig template to format the emails with. If you want to modify the CSS, you should copy the file to your theme/ folder, and modify it there. Any changes in the file in the distribution might be overwritten after an update to the extension.

"modify the CSS" should be "modify the HTML"

Get records with specific taxonomy value

Hi, can someone please tell me how do I get records of all entries with specific taxonomy value. For example all records with category: work.

Thank you in advance!

Update "always present fields" in content.md

As pointed out by @GDmac

9:27 PM <GDmac> Bopp, is this still true? "every contenttype has a Field for 'id', 'slug', 'date_created' and 'user'"
9:27 PM <Bopp> nope
9:27 PM <GDmac> bopp, i know slug can be overridden
9:28 PM <Bopp> yes, it can be overridden, but it's still there
9:28 PM <GDmac> and the others?
9:29 PM <Bopp> there's no 'user' anymore though.. Instead it has an ownerid column, containing a reference to a user.
9:29 PM <Bopp> also, no "date" anymore, but rather datecreated, datechanged, datepublish and datedepublish
9:29 PM <GDmac> i'll leave content.md to later then
9:30 PM <Bopp> and it also always has a status.
9:30 PM <Bopp> GDmac: i'll paste this part of the chat into a new issue, so we won't forget. :-)

Clearer names in documentation about paging

In http://docs.bolt.cm/content-paging you talk about adding names in a parameter for the pager {{ pager('entries') }}. It is, however, not clear you use the name of the array, or the name of the contenttype, because both are named the same.
( {% setcontent entries = "entries/latest/3" allowpaging %} )

{% setcontent myentries = "entries/latest/3" allowpaging %} would be clearer, so there is no mix up for people that only copy and paste.

documentation is not up to date / complete / sufficient

The documentation is old, insufficient or incomplete

Some things I'm missing or look wrong to me

Getting started:

  • config_local.yml and related tips

Working with bolt:

  • content types configuration ( contenttypes.yml )
    • all fields in a readable format
    • file uploads / file lists

Templating:

  • query parameters for use in templates - setcontent x where { a : b } and other constructions like that

Development:

  • building a twig filter
  • creating your own nut commands
  • all mentions of \util::foo

Extensions:

  • building an extension is not consistent with most included extensions
  • what is the recommended way to set up a database connection in an extension
  • saving and loading content from an extension
  • what documentation for an extension is recommended
  • how to send a mail from within an extension
  • how to add a script/css/twig asset from an extension

is it possible to add debug stuff to the debugbar

there is an explanation for {{ print() }}
there is an explanation for \util::var_dump()

but the explanation for adding messages to the debug bar is missing

(and now I have to look for it in the code, because I forgot how to do it)

User manual repository

Hi, not really an issue here, it is just a question.

Is there a repository for user documentation that can be found at http://manual.bolt.cm

I'm French and I started the translation of the user manual.

Are there a way to give back 💞 the translated pages to the project when done ?
I found bolt/bolt-docs but it is just about technical/developer documentation.

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.