Discussion: Ideas, introductions and notes for Taskserver ccsync in GSoC'27

**Description**
This discussion thread is for brainstorming features, integrations, and UX enhancements that we could implement for `ccsync` as part of GSoC 2027. Everyone is encouraged to propose, refine, and discuss ideas in preparation. The discussion might be related to any of these ideas or new ones, and their implementations, etc. **Please do not share your personal information, proposals, art, anything that might be useful, etc. here.**

Contributors can also use this thread to briefly introduce themselves and/or represent their interests or skills relevant to GSoC 2027 with CCSync.

**Expected Output**
- A list of proposed ideas, feature requests, integration plans, UX suggestions, and contributor interests for GSoC 2027 (not all ideas may be implemented).
- Clarification, refinement, and prioritization of possible directions for `ccsync`
- Placeholder only: no implementation or assignment of work unless ideas are moved to tracked issues, after further review

**Feature & UX Ideas for now (all these are part of the same project)**
1. Data Visualization & UX (Medium/High Priority)
- Kanban & Calendar Views using projects: Moving beyond lists to project-based boards and time-based scheduling.
- Task Graph Flow Diagram: A semantic graph (using Cytoscape.js or D3.js) showing dependencies, project clusters, and tag relationships.
- Advanced Theming: High-contrast modes, adjustable typography, and persistent light/dark themes.
- Text to speech: Add a native TTS module, that dictates the texts of each task Dialog, on demand. Would make it easier to navigate across tasks

2. Ecosystem & Integrations (Medium/High Priority)
- Centralized Sync Hub: Expanding 2-way sync for Google Tasks (priority), Google Calendar, Jira, and Joplin.
- Code Host Integration: Integration with GitHub/GitLab issues via Bugwarrior.
- Notification Engine: External reminders via Email (likely by extending the backend CLI).
- Updated [Documentation ](https://its-me-abhishek.github.io/ccsync-docs/) for all the new changes

3. Core & Performance (Medium)
- PWA Support: Offline usage via Web Workers for a desktop/mobile app-like experience.
- Account Portability: Tools for bulk transfer, deletion, or UUID migration between accounts.
- Mock Demo Instance: A "Try Before You Login" feature using a mock frontend implementation that doesn't require real auth. It can include a sample user with secrets, etc. Some tasks, similar to the real HomePage

4. **Task Graph Flow Diagram Idea:** Semantic “task graph” with visual connections
- Nodes = tasks, Edges = dependencies/project/tag sharing
- Different line styles for each relation, interactive exploration (Cytoscape.js/D3.js)
- Node color/border for project/priority, hover/click for task info, mini-map overview, filters for graph layers
- Optional: visual effects (aging, completion, AI “theme” nodes)
- Implementation path: preprocess tasks in browser, render with react-cytoscapejs, style by edge type, add filtering/interactions.

Feel free to DM me on Zulip for any discussion related to proposals, etc.

**Important Links**
- https://ccextractor.org/

NOTE: This list is not exhaustive; additional ideas may be proposed, and some items listed here may be deprioritized or removed over time. The scope (hours required) can thus be decided for the project once these are finalized. Please use this thread strictly for discussion and brainstorming. Since this is not a tracked issue, it is not assignable, and contributors are requested not to start implementation work based on these ideas at this stage.