When I have to edit some content on a site I often spend more time on searching where the data is rather than editing it. In this context an integration with a search engine is the right way to go.
* Having proper indexes on pages, global data types and meta data, binded to 'entity tokens' in C1, will make all the dynamic content on the site searchable.
Futhermore, we can have a "code search", which will not be available for editors, but only for administrators/developers.
When I need to fix an existing functionality it takes quite a lot of time to find f.e. where's the code that inserts table with some particular identifier, or where's the code that sends an email with this content. Of course it is easy to do by using "Find in files" in Visual Studio, IF website files are accessible by network but when they aren't and/or some of the information I need is on SQL database (f.e. a default value for a function call parameter) it is a lot of time spent that could be avoided.
* Having indexes on all xslt-functions, /app_Code cs files, javascript/css/aspx/aspx.cs files will turn support works into a coding paradise
Of course, the suggested weapon of choise is Lucene.NET
Comments: Added in v6.0 - see https://github.com/Orckestra/C1-CMS-Foundation/releases/tag/v6.0 - (altrhough code search would require you write a search provider, all the needed infrastructure is in C1 now)
* Having proper indexes on pages, global data types and meta data, binded to 'entity tokens' in C1, will make all the dynamic content on the site searchable.
Futhermore, we can have a "code search", which will not be available for editors, but only for administrators/developers.
When I need to fix an existing functionality it takes quite a lot of time to find f.e. where's the code that inserts table with some particular identifier, or where's the code that sends an email with this content. Of course it is easy to do by using "Find in files" in Visual Studio, IF website files are accessible by network but when they aren't and/or some of the information I need is on SQL database (f.e. a default value for a function call parameter) it is a lot of time spent that could be avoided.
* Having indexes on all xslt-functions, /app_Code cs files, javascript/css/aspx/aspx.cs files will turn support works into a coding paradise
Of course, the suggested weapon of choise is Lucene.NET
Comments: Added in v6.0 - see https://github.com/Orckestra/C1-CMS-Foundation/releases/tag/v6.0 - (altrhough code search would require you write a search provider, all the needed infrastructure is in C1 now)