Open Ground Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Rotoscope Roadmap ======

Plenty of things can be part of the roadmap of Rotoscope. Let's try to put various releases into plans. 

  - DONE! - Release with hard coded links, testing functionality (alpha) 
  - IN PROGRESS - Add pills to turn on and off categories
  - Add maximize / minimize to larger sections
  - Page improvements, initial unsearched state (add animations?) beautify
  - Separate Links from HTML, put into JSON, figure out process
  - Fix Footer and add real subpages
  - Logo improvements towards improved branding
  - how to get the .com?
  - Testing Period, and create placeholder social media, post to sites, upload to open source or no?
  - Look at an additional design
  - Add link creation front end
  - Add account features

===== Fuzzy Search =====

implementing a simple fuzzy matching algorithm with light processing requirements could allow things to show/hide/transpose certain entries or entire categories based on what use is searching for. Can it do it on the fly? Because it has to be able to do that as they type. 
==== Data Ontology ====

In the digital world, an ontology is a way to organize and structure data so that it can be easily understood and shared between different systems. It's like a dictionary that defines the meaning of terms and relationships between them.

Think of it like a map that helps computers understand the connections between different pieces of information. This way, when you search for something online, the results can be more accurate and relevant.

For example, imagine you're searching for information about a movie. An ontology would help the search engine understand that "movie" is related to "actors," "directors," and "genres." This way, the search results can include information about the movie's cast, crew, and plot.

==== Footer Links and Info Pages ====

Asking A.I. for help putting in some additional content pages to fill in the footer. 

need some suggestions. in the footer I've got links. I'm not, at this time, prepared to add separate page content. But I need some ideas for what links make sense there. I think an F.A.Q and a roadmap will be a good couple pages to have. Eventually if made open source for people, then some tips on how to add your own links, youtube channel information. 

=== A.I. Answer to the footer question: ===

Looking at your footer structure, here are relevant link suggestions that align with Rotoscope's privacy-focused search functionality:

=== For the "About" section: ===

  * Privacy Policy
  * How It Works
  * Search Engine Partners
  * Support the Project

=== For the "Services" section: ===

  * Browser Extensions
  * API Access
  * Custom Search Tools
  * Search Filters
  * Advanced Features

=== For the "Other" section: === 

  * Privacy Guide
  * Search Tips
  * Keyboard Shortcuts
  * Contributing
  * Release Notes

These links would provide valuable context and information about Rotoscope's capabilities even before building out the full pages. The structure supports future expansion while maintaining relevance to your core search aggregation service.


==== Front end features, submission, authentication etc. ====

I've been able to get a high level summary outline of needs as to how to do front end features for adding websites via form, and eventually adding login security. A.I. was helpful in direction of what to expect and what technologies will be necessary or touched. 

Prompt: "I'm still implenting things a little at a time, but i want to look out ahead. so eventualy these links will come from a JSON file. And that json file I would like to make it so I could fill out a form and add a new link to the JSON file appending it in the right spot. And later, maybe a person could login to the instance and make those changes. Could provide me a brief summary of what would be needed to implement that functionality?"

Yes! To implement that functionality you'll need:

  - Backend server (Node.js, Python, PHP etc) to:
    * Handle form submissions
    * Read/write JSON file
    * Manage user authentication
  - HTML form with fields for:
    * Category selection
    * Site name
    * Icon path
    * Search URL pattern
    * Display URL
  - Authentication system:
    * User login/registration
    * Session management
    * Access control
  -  API endpoints to:
    * GET current JSON data
    * POST new entries
    * PUT/PATCH updates
    * Validate submissions
  - Frontend JavaScript to:
    * Submit form data
    * Handle responses
    * Update display
    * Manage user sessions

The implementation can start simple with basic form submission and JSON updates, then expand to include user authentication and more advanced features as needed.