Blog AI Design

Admin  |  Dashboard  |  Content  |  Custom  |  Users  |  Settings  |  About

Design notes for Claude

General

  • I'll be getting BlogAI ready for our ai-research-blog rewrite. 
    • Rationale: We will be keeping all features and capabilities.  I want to ensure that what we have in BlogEngine.net is working the way it is intended to work so that we don't have to refactor twice; you'll be able to pull class and AngularJs logic into new framework and update as required. This will streamline overall design.
  • Maintain the same schema with exception of "Contacts"
    • Schema means that we generate N-Quad schema's to match the legacy BlogEngine.net SQL Schema; we will only use N-Quad for ai-research-blog.
    • Contacts removal rationale: - was manually added later for a specific purpose that no longer exists
  • BLL - DAL layers matter here. 
    • This first iteration everything is going to be specific to how BlogEngine.NET did processing.  If we do a one-to-one migration process (fields and how data is handled) then the process can move smoothly - reusing whatever is feasible.   Later, when it is fully functional, we can start picking priority areas and replacing BLLs / DALs with a more modern, mainstream process if/as applicable.
    • Versioning could be king here.  We could polish up the process by allowing our data to be backwards and forwards compatible. 
  • In an agile manner, we'll want to start with the following main features to where it is functional (can be used for post/pages)
    • CRUDL Posts
    • CRUDL Pages
  • We'll operate under the premise that our underlying definitions will use Tenant/Orgs
    • We are in Tenant 1 = www.Global-Webnet.com (no other tenants at this time - but code supports tenant)
    • Organization will be Blogs
    • Roles will apply to both Tenant and Orgs (currently they are for blogs) with Tenant roles apply to all orgs (as expected)

 ADMIN SECTIONS