Addons

[ghost]

Hi guys,

Hope you are doing well !

I was looking at your repo, saying to myself finally a good CMS oriented project, written in Go ! :-)

I want to suggest the following list of addons:

• [ ] 1. Elasticsearch client for Go: https://github.com/olivere/elastic
• [ ] 2. A modern text indexing library for go: https://github.com/blevesearch/bleve
• [ ] 3. Go utility for ElasticSearch and Bleve: https://github.com/dorsha/lennon
• [ ] 4. HTTP/REST/JSON front-end to bleve: https://github.com/blevesearch/bleve-explorer
• [ ] 5. AngularJS admin GUI to any RESTful API : https://github.com/marmelab/ng-admin
• [ ] 6. Faster performance web framework https://github.com/gin-gonic/gin
  1. Would help to scale the volume of tags or posts, you could publish
  2. Would implement some advanced full-text search functions and the addons like bleve explorer
  3. Would merge the benefits of the 2 above
  4. & 5. A Rest API would simplify how to build custom Admin GUI.

Did u shaped a roadmap for your project ? Maybe I missed the link :-)

Fragmenta sounds really promising :-)

Cheers, Luc

[joeblew99]

i have used Bleve and the explorer. Its really perfect for a CMS in My opinion. Its able to be decoupled

[kennygrant]

I haven't done a road map as yet (I'm mostly using the issues for that), but those are interesting ideas. Thanks. For extending so far I've been adding code in src/lib and simply linking it, but some sort of addon system is another option. I'd want to avoid adding dependencies to core but would be happy to see people exploring addons and reporting back here.

Re bleve, I tend to use psql FTS, but yes you could use things like bleve or elastic search for searches - better to tackle external integrations like that when you require them though I think, rather than attempting to pre-emptively optimise for speed or scale. Re a js frontend, this isn't something I'm personally interested in, but again I'd be interested to see the results if someone wanted to try. I would definitely like to serve json for all endpoints at some point so that this is easy to do. Re gin, you could certainly build something similar with it (or micro).

[joeblew99]

make sense. YAGNI....

[kennygrant]

Going to close this one in favour of specific changes, if you want a specific one, please open an issue on that alone.

Ones that interest me from the list above:

• Serving json for a js front end
• Possibly some text/indexing search extension
• Using some other pure-go storage/search solution

Ones that definitely don't interest me:

• Using ElasticSearch by default (too heavyweight for a default)
• Using gin as default (though it's quite possible in your own apps, just modify templates)