[searchisko-dev] Quickstart provider and info
Pete Muir
pmuir at redhat.com
Wed Oct 9 11:39:03 EDT 2013
On 8 Oct 2013, at 22:58, Jason Porter <jporter at redhat.com> wrote:
> Here's what I've come up with. Let me know what you think Pete. Everything with sys_ is either recommended or required.
>
> # JSON payload to Searchisko (and mapping)
> #
> # {
> # # Pulled from the file (our names : searchisko mapping)
> # header: sys_title
> # author: sys_contributors (should be an array)
> # level (difficulty?)
Sounds good.
> # technologies: tags (should be an array)
> # summary: sys_description
> # target_product: (project?)
Yeah, we've discussed before that we will just represent products as a project, with a custom flag.
> # url (build it from output_path): sys_url_view
> #
> # # Other required searchisko mappings (searchisko : what we send)
> # sys_content_content-type: not sure (markdown or html?)
HTML, *I think*, as this is what the result will point at. But I'm not sure.
> # sys_content (raw markdown or html?)
> # sys_type: "quickstart"
> # sys_content_type: "quickstart"
> # sys_content_provider: whatever-we-name-the-provider
> #
> # # I think we can pull these from git, like we do currently for the site
> # sys_created
> # sys_activity_dates
> # sys_list_activity_date
> # sys_updated
+1
> #
> # # I don't think we have any way of getting these, should we start adding them? I'm not sure how "required" these are
> # sys_project
> # sys_project_name
I think this should be the product.
> #
> # # comments may be great, but we'd need to get them from disqus
> # }
More information about the searchisko-dev
mailing list