mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-06 22:34:02 -05:00
Web Commitments proposal Q1 2026 (#345)
This commit is contained in:
Felicio
1
.node-version
Normal file
1
.node-version
Normal file
@@ -0,0 +1 @@
|
||||
18.14
|
||||
@@ -31,6 +31,7 @@ The Logos Contribute portal directly supports the quarterly KPIs by:
|
||||
- **GitHub Issues Integration**: Display curated issues from contribute.logos.co repository
|
||||
|
||||
## Task List
|
||||
|
||||
### Contributor Directory
|
||||
|
||||
* fully qualified name: `vac:web:ift:2025q4-logos-contributions-portal:contributor-directory`
|
||||
@@ -101,6 +102,7 @@ Plumb BI-provided GitHub datasets into the portal to power contributor metrics a
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
- API by BI team
|
||||
|
||||
### Leaderboard
|
||||
|
||||
|
||||
126
content/web/ift/2026q1-demos.md
Normal file
126
content/web/ift/2026q1-demos.md
Normal file
@@ -0,0 +1,126 @@
|
||||
---
|
||||
title: Demos
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: "Demonstration of completed work and presentations to showcase the Web team's deliverables, share progress with the entire organization, and gather feedback for continuous improvement."
|
||||
---
|
||||
|
||||
`vac:web:ift:2026q1-demos`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves demonstrating completed work and creating presentations to showcase the Web team's deliverables, share progress with the entire organization, and gather feedback for continuous improvement. These demonstrations serve as internal communication tools that present what the team has accomplished and enable cross-functional collaboration and learning.
|
||||
|
||||
The demos commitment supports IFT's strategic objectives by:
|
||||
- **Completed Work Showcase**: Demonstrating finished Web team deliverables and accomplishments to the broader organization
|
||||
- **Progress Presentations**: Sharing completed projects, features, and solutions through organized presentations
|
||||
- **Knowledge Sharing**: Communicating technical approaches, solutions, and learnings from completed work across service units and projects
|
||||
- **Feedback Collection**: Gathering input from stakeholders, other teams, and the organization on completed work to improve future deliverables and alignment
|
||||
- **Cross-Functional Collaboration**: Enabling other teams to understand Web capabilities and identify collaboration opportunities based on demonstrated work
|
||||
|
||||
## Task List
|
||||
|
||||
### Biweekly 1 - IFT Townhall Demo
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-1-ift-townhall`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/01/15
|
||||
* end-date: 2026/01/22
|
||||
|
||||
#### Description
|
||||
|
||||
Prepare and deliver a biweekly demonstration of completed Web team work at the IFT Townhall, showcasing deliverables and gathering feedback.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Presentation materials
|
||||
- Demo recording/documentation
|
||||
|
||||
### Biweekly 2 - IFT Townhall Demo
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-2-ift-townhall`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/01/29
|
||||
* end-date: 2026/02/05
|
||||
|
||||
#### Description
|
||||
|
||||
Prepare and deliver a biweekly demonstration of completed Web team work at the IFT Townhall, showcasing deliverables and gathering feedback.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Presentation materials
|
||||
- Demo recording/documentation
|
||||
|
||||
### Biweekly 3 - IFT Townhall Demo
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-3-ift-townhall`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/12
|
||||
* end-date: 2026/02/19
|
||||
|
||||
#### Description
|
||||
|
||||
Prepare and deliver a biweekly demonstration of completed Web team work at the IFT Townhall, showcasing deliverables and gathering feedback.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Presentation materials
|
||||
- Demo recording/documentation
|
||||
|
||||
### Biweekly 4 - IFT Townhall Demo
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-4-ift-townhall`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/26
|
||||
* end-date: 2026/03/05
|
||||
|
||||
#### Description
|
||||
|
||||
Prepare and deliver a biweekly demonstration of completed Web team work at the IFT Townhall, showcasing deliverables and gathering feedback.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Presentation materials
|
||||
- Demo recording/documentation
|
||||
|
||||
### Biweekly 5 - IFT Townhall Demo
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-5-ift-townhall`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Prepare and deliver a biweekly demonstration of completed Web team work at the IFT Townhall, showcasing deliverables and gathering feedback.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Presentation materials
|
||||
- Demo recording/documentation
|
||||
|
||||
### Biweekly 6 - IFT Townhall Demo
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-6-ift-townhall`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/26
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Prepare and deliver a biweekly demonstration of completed Web team work at the IFT Townhall, showcasing deliverables and gathering feedback.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Presentation materials
|
||||
- Demo recording/documentation
|
||||
77
content/web/ift/2026q1-maintenance.md
Normal file
77
content/web/ift/2026q1-maintenance.md
Normal file
@@ -0,0 +1,77 @@
|
||||
---
|
||||
title: "Web Maintenance & Support"
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: "Ongoing maintenance and support for previously delivered web projects across the IFT ecosystem, ensuring continued functionality, security, and performance optimization."
|
||||
---
|
||||
|
||||
`vac:web:ift:2026q1-maintenance`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves ongoing maintenance and support for previously delivered web projects across the IFT ecosystem. The Web unit ensures continued functionality, security updates, performance optimization, and compatibility management for all web applications, websites, and tools delivered in previous quarters.
|
||||
|
||||
The maintenance commitment supports IFT's strategic objectives by:
|
||||
- **Project Sustainability**: Ensuring delivered projects remain functional and secure over time
|
||||
- **User Experience Continuity**: Maintaining high-quality user experiences across all web properties
|
||||
- **Technical Debt Management**: Addressing issues and improvements that emerge post-launch
|
||||
- **Resource Planning**: Providing clear allocation for ongoing support work
|
||||
|
||||
## Task List
|
||||
|
||||
### Support & Questions
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-maintenance:support-questions`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Respond to questions and support requests raised by stakeholders, users, and team members regarding previously delivered web projects. Provide timely responses and guidance to ensure continued project usability.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Response documentation
|
||||
- Support tickets resolved
|
||||
- FAQ updates
|
||||
|
||||
### Issue Logging & Planning
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-maintenance:issue-logging`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Log issues, bugs, and improvement requests on GitHub for planning and prioritization. Ensure all maintenance-related issues are properly documented and tracked for future work.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- GitHub issues created
|
||||
- Issue documentation
|
||||
- Planning backlog updates
|
||||
|
||||
### Hotfixes
|
||||
|
||||
* fully qualified name: `vac:web:ift:2026q1-maintenance:hotfixes`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Address critical bugs and security issues requiring immediate hotfixes across previously delivered web projects. Ensure rapid response to urgent issues affecting production systems.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Hotfix implementations
|
||||
- Hotfix deployment documentation
|
||||
- Post-hotfix verification reports
|
||||
@@ -18,6 +18,30 @@ The unit's work directly supports IFT's strategic objective of scaling project c
|
||||
|
||||
[[web/preview|Roadmap Preview]]
|
||||
|
||||
## 2026q1
|
||||
|
||||
### `ift:`
|
||||
|
||||
* [[web/ift/2026q1-demos|demos]]
|
||||
* [[web/ift/2026q1-maintenance|maintenance]]
|
||||
|
||||
### `status:`
|
||||
|
||||
* [[web/status/2026q1-community-curation|community-curation]]
|
||||
* [[web/status/2026q1-sn-hub|sn-hub]]
|
||||
* [[web/status/2026q1-sn-website|sn-website]]
|
||||
* [[web/status/2026q1-status-wallet-extension|status-wallet-extension]]
|
||||
* [[web/status/2026q1-status-website|status-website]]
|
||||
* [[web/status/2026q1-status-app|status-app]]
|
||||
|
||||
### `logos:`
|
||||
|
||||
* [[web/logos/2026q1-contribute-portal|contribute-portal]]
|
||||
* [[web/logos/2026q1-logos-website|logos-website]]
|
||||
* [[web/logos/2026q1-logos-forum|logos-forum]]
|
||||
|
||||
### 2025q4
|
||||
|
||||
## 2025q4 `vac:web:`
|
||||
|
||||
---
|
||||
|
||||
171
content/web/logos/2026q1-contribute-portal.md
Normal file
171
content/web/logos/2026q1-contribute-portal.md
Normal file
@@ -0,0 +1,171 @@
|
||||
---
|
||||
title: Contribute Portal
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "logos"
|
||||
draft: false
|
||||
description: "Development of Contribute Portal, a contribution hub that recognizes open source contributors and helps new developers make their first contributions to strengthen the Logos ecosystem."
|
||||
---
|
||||
|
||||
`vac:web:logos:2026q1-contribute-portal`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves developing Contribute Portal, a comprehensive contribution hub that recognizes open source contributors and helps new developers make their first meaningful contributions to the Logos ecosystem. The portal serves as a critical component of the volunteer-driven, open source community building strategy, showcasing contributor activity, providing curated resources, and offering clear pathways for community engagement.
|
||||
|
||||
The Contribute Portal directly supports the quarterly KPIs by:
|
||||
- **External Developer Contributions**: Tracking and encouraging 10% month-over-month increase in external developers contributing to the Logos technology stack
|
||||
- **Community Activation**: Supporting the 10% activation benchmark for new community members through clear contribution pathways
|
||||
- **Hacktivation Barriers**: Providing 10% increase in tagged lower tasks by CCs in GitHub repositories
|
||||
- **Community Retention**: Helping retain contributors through recognition and engagement systems
|
||||
|
||||
**Key Features Include:**
|
||||
- **Contributor Directory**: Displays GitHub usernames, profile links, contribution counts, and contribution history
|
||||
- **Individual Profiles**: Detailed pages with contribution details and complete contribution lists
|
||||
- **Search Functionality**: Search by GitHub username or repository name
|
||||
- **Contribution Guidelines**: Clear instructions and best practices maintained on GitHub
|
||||
- **Contributor Ladder**: Structured growth path where contributors earn recognition, responsibilities, and privileges (from leaderboard presence and swag to reviewer rights and governance roles) as they progress through ranks
|
||||
- **Contributors Leaderboard**: Seasonal and all-time rankings highlight active contributors across coding, design, documentation, translation, etc.
|
||||
- **Proposal Submission**: Form allowing developers, writers, designers, and others to submit proposals
|
||||
- **GitHub Issues Integration**: Display curated issues from contribute.logos.co repository
|
||||
|
||||
## Task List
|
||||
|
||||
### Contribution Guidelines
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:contribution-guidelines`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/26
|
||||
* end-date: 2026/03/12
|
||||
|
||||
#### Description
|
||||
|
||||
Review and update contribution guidelines copy to ensure clarity and completeness.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated contribution guidelines documentation
|
||||
- Copy review report
|
||||
|
||||
### Use BI team's Github Data
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:bi-data`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/26
|
||||
|
||||
#### Description
|
||||
|
||||
Integrate BI team's GitHub data API to power contributor metrics and analytics. Migrate issues and select repositories for data integration.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- API integration implementation
|
||||
- Issue migration completed
|
||||
- Repository selection documented
|
||||
|
||||
### Leaderboard
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:leaderboard`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Implement seasonal and all-time leaderboards with sorting that highlights high-impact contributors across coding, design, documentation, and translation.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Leaderboard UI implementation
|
||||
- Sorting and filtering functionality
|
||||
|
||||
### Tier & Scoring
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:tier-scoring`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Define the tier logic and scoring rules that map contributor activity into the recognition ladder system as specified in the proposal.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Tier and scoring system implementation
|
||||
- Documentation of scoring rules
|
||||
- Ladder system integration
|
||||
|
||||
### Proposals
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:proposals`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Launch the proposal submission flow so volunteers can pitch work or request support directly in the portal.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Analytics
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:analytics`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Set up Umami analytics integration for tracking portal usage and contributor engagement metrics.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Umami analytics integration
|
||||
- Analytics dashboard configuration
|
||||
- Tracking implementation
|
||||
|
||||
### Search
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:search`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Implement search functionality on dedicated pages to allow users to search by GitHub username or repository name.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Search functionality implementation
|
||||
- Search UI components
|
||||
|
||||
### Sign-up form
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:sign-up-form`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Implement sign-up form for new contributors to register and join the portal.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Sign-up form implementation
|
||||
- Form validation and submission
|
||||
|
||||
> https://miro.com/app/board/uXjVGe0JT7A=/?moveToWidget=3458764651894962888&cot=14
|
||||
104
content/web/logos/2026q1-logos-forum.md
Normal file
104
content/web/logos/2026q1-logos-forum.md
Normal file
@@ -0,0 +1,104 @@
|
||||
---
|
||||
title: Logos Forum
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "logos"
|
||||
draft: false
|
||||
description: "Optimization of the Logos Forum experience to reduce onboarding friction, enable seamless story submission, and improve community contribution workflows."
|
||||
---
|
||||
|
||||
`vac:web:logos:2026q1-logos-forum`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves optimizing the Logos Forum experience to address critical bottlenecks that prevent community members from contributing their stories and engaging with the community. The current forum experience creates significant friction that causes potential contributors to drop off, requiring personal relationships and handholding to successfully onboard new users.
|
||||
|
||||
The Logos Forum optimization will support Logos' strategic objectives by:
|
||||
- **Reduced Friction**: Eliminating barriers that prevent community members from contributing stories and pitches
|
||||
- **Self-Service Onboarding**: Enabling users to contribute without requiring personal handholding
|
||||
- **Community Growth**: Making it easier for new members to share their ideas and build with Logos
|
||||
- **Story Onboarding**: Streamlining the process for community members to submit and share their stories
|
||||
|
||||
**Key Problem Areas:**
|
||||
- **Email Domain Restrictions**: Forum doesn't accept custom domain names in email addresses
|
||||
- **Spam Filter Cooldown**: 24-hour cooldown period prevents instant posting, even for legitimate contributors
|
||||
- **First Post Complexity**: New users face barriers to posting their intro - category selection, multiple buttons, and unclear posting flow
|
||||
- **Content Visibility Restrictions**: Content may be hidden based on user rank, preventing engagement from visitors and new users
|
||||
|
||||
## Task List
|
||||
|
||||
### Custom Domain Email Support
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-forum:custom-domain-email-support`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Allow registration with custom domain email addresses to remove barriers for users with professional email domains.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Email validation update
|
||||
- Custom domain support implementation
|
||||
- Registration flow updates
|
||||
|
||||
### Cooldown Bypass System
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-forum:cooldown-bypass-system`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/26
|
||||
|
||||
#### Description
|
||||
|
||||
Implement referral code on signup to bypass 24-hour cooldown period. If referral code system not possible, implement heart system that allows users to request bypassing the cooldown. Maintain spam protection while enabling legitimate community members to post immediately.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Referral code system or heart system implementation
|
||||
- Cooldown bypass logic
|
||||
- Spam protection maintenance
|
||||
|
||||
### First Post Intro Flow
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-forum:first-post-intro-flow`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Enable new users to post their intro immediately, no matter what. Automatic flow that brings new users directly to a text field where they can write their intro. Single post button, no category choice required. Very straightforward, simplified posting experience. Remove 24-hour comment-only restriction for intro posts.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Simplified intro posting flow
|
||||
- Automatic redirect to intro text field
|
||||
- Single-button posting interface
|
||||
- Removal of comment-only restriction
|
||||
|
||||
### Content Visibility
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-forum:content-visibility`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Allow anyone, including first-time visitors who are not signed up, to see all posts and comments. Remove content restrictions based on user rank or registration status. Enable public viewing to encourage engagement with community member posts.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Public content visibility implementation
|
||||
- Removal of rank-based restrictions
|
||||
- Guest viewing capability
|
||||
|
||||
> https://github.com/acid-info/logos/issues/19
|
||||
113
content/web/logos/2026q1-logos-website.md
Normal file
113
content/web/logos/2026q1-logos-website.md
Normal file
@@ -0,0 +1,113 @@
|
||||
---
|
||||
title: Logos Website
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "logos"
|
||||
draft: false
|
||||
description: "Continued development and enhancement of the Logos website, building upon the comprehensive platform to improve user journeys, add new features, and optimize community engagement."
|
||||
---
|
||||
|
||||
`vac:web:logos:2026q1-logos-website`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves continued development and enhancement of the Logos website, building upon the comprehensive platform launched in previous quarters. The work focuses on improving user journeys, adding new features, optimizing community engagement, and refining the dual-experience architecture for developers and non-developers.
|
||||
|
||||
The Logos website enhancement will support Logos' strategic objectives by:
|
||||
- **User Experience Refinement**: Improving user journeys based on analytics and user feedback
|
||||
- **Feature Expansion**: Adding new features and functionality to support community growth
|
||||
- **Community Engagement**: Optimizing pathways for contribution, learning, and participation
|
||||
- **Content Updates**: Keeping website content current with latest Logos developments and community activities
|
||||
|
||||
## Task List
|
||||
|
||||
### Contribute Portal
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-website:contribute-portal`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Integrate contribute portal leaderboard into the Logos website. Coordinate with legal and EcoDev teams for review and approval.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Leaderboard component integration into Logos website
|
||||
- Legal team review documentation and sign-off
|
||||
- EcoDev team review documentation and sign-off
|
||||
- Leaderboard UI implementation on website
|
||||
|
||||
### Admin
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-website:admin`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/26
|
||||
|
||||
#### Description
|
||||
|
||||
Set up admin functionality for production release and integrate with infrastructure team's CI/CD pipeline.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Admin panel implementation
|
||||
- Production release configuration
|
||||
- CI/CD pipeline integration
|
||||
|
||||
### CRM
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-website:crm`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Implement CRM functionality as specified in the design board and Discord discussions for managing community relationships and engagement.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- CRM system implementation
|
||||
- Integration with website
|
||||
- Documentation
|
||||
|
||||
### CMS/Sanity
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-website:cms-sanity`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Propose alternative to Sanity CMS for content management, enabling non-technical team members to update website content.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Sanity CMS alternative proposal
|
||||
- Documentation and training materials
|
||||
|
||||
### Selfhosting
|
||||
|
||||
* fully qualified name: `vac:web:logos:2026q1-logos-website:selfhosting`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/19
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Set up self-hosting infrastructure and deployment processes for the Logos website.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Self-hosting configuration
|
||||
- Deployment documentation
|
||||
- Infrastructure setup
|
||||
@@ -70,3 +70,20 @@ Optimize Status web SEO fundamentals—performance, structured data, and metadat
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### CMS
|
||||
|
||||
* fully qualified name: `vac:web:status:2025q4-status-website:cms`
|
||||
* owner: felicio
|
||||
* status: not started
|
||||
* start-date: 2025/10/01
|
||||
* end-date: 2025/12/31
|
||||
|
||||
#### Description
|
||||
|
||||
Evaluate and implement CMS solution for Status website. Review CMS comparison overview and create GitHub PRs for implementation.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- CMS evaluation report
|
||||
- CMS implementation GitHub PRs
|
||||
- CMS integration documentation
|
||||
59
content/web/status/2026q1-community-curation.md
Normal file
59
content/web/status/2026q1-community-curation.md
Normal file
@@ -0,0 +1,59 @@
|
||||
---
|
||||
title: Community Curation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "status"
|
||||
draft: false
|
||||
description: "Migration of the Community Curation DApp to the status-web monorepo, enabling SNT holders to vote on which communities should be included in the Status Communities directory."
|
||||
---
|
||||
|
||||
`vac:web:status:2026q1-community-curation`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves migrating the Community Curation DApp to the [status-web monorepo](https://github.com/status-im/status-web), a centralized repository for building user interfaces, websites, web applications, dApps, browser extensions, and APIs in the Status ecosystem.
|
||||
|
||||
The Community Curation DApp allows SNT holders to determine which communities should be included in the Status Communities directory through a decentralized voting mechanism. The DApp provides governance functionality for community inclusion, removal, and featured status.
|
||||
|
||||
**Key Features:**
|
||||
- **Community Addition Voting**: SNT holders can vote for or against adding communities to the directory
|
||||
- **Community Removal Voting**: SNT holders can vote for or against removing communities from the directory
|
||||
- **Weekly Featured Selection**: Ongoing voting for which communities from the directory should appear in the Weekly Featured section
|
||||
- **Voting Periods**: Two-week voting periods followed by one-week verification periods
|
||||
- **Cooldown Periods**: 30-day cooldown between votes for the same community addition/removal, and 3-week cooldown for Weekly Featured communities
|
||||
|
||||
**Voting Rules:**
|
||||
- Each vote lasts for two weeks, followed by a one-week verification period
|
||||
- If a vote to add ends in favor, the community is added; otherwise, a new vote can be started after 30 days
|
||||
- If a vote to remove ends in favor, the community is removed; otherwise, a new vote can be submitted after 30 days
|
||||
- Weekly Featured section displays five communities with the most votes, rotating weekly
|
||||
- Communities that leave Weekly Featured cannot return for three weeks
|
||||
|
||||
The migration to the status-web monorepo will support Status' strategic objectives by:
|
||||
- **Code Consolidation**: Centralizing web development efforts in a unified monorepo structure
|
||||
- **Maintainability**: Improving code organization and maintenance through shared tooling and packages
|
||||
- **Developer Experience**: Leveraging the monorepo's shared components, build tools, and development workflows
|
||||
- **Ecosystem Integration**: Aligning with other Status web applications and tools in the same repository
|
||||
|
||||
## Task List
|
||||
|
||||
### Migration to status-web Monorepo
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-community-curation:migration-to-status-web-monorepo`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/26
|
||||
|
||||
#### Description
|
||||
|
||||
Migrate Community Curation DApp to the status-web monorepo. Integrate with existing monorepo structure, build tools, and shared packages. Ensure compatibility with status-web development workflows and deployment processes.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Migrated DApp code
|
||||
- Monorepo integration
|
||||
- Build and deployment configuration
|
||||
- Documentation
|
||||
|
||||
204
content/web/status/2026q1-sn-hub.md
Normal file
204
content/web/status/2026q1-sn-hub.md
Normal file
@@ -0,0 +1,204 @@
|
||||
---
|
||||
title: SN Hub
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "status"
|
||||
draft: false
|
||||
description: "Continued development and enhancement of Status Network Hub, the main portal application for Status Network users to access all network features including staking, yield earning, bridging, and public funding pool tracking."
|
||||
---
|
||||
|
||||
`vac:web:status:2026q1-sn-hub`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves continued development and enhancement of the Status Network Hub (SN Hub), building upon the Testnet MVP to add advanced features, improve user experience, and prepare for mainnet launch. The hub serves as the unified interface for all Status Network features and activities.
|
||||
|
||||
The SN Hub development will support Status Network's strategic objectives by:
|
||||
- **Feature Expansion**: Adding advanced features beyond the Testnet MVP including analytics, tokenomics features, and governance tools
|
||||
- **Mainnet Preparation**: Ensuring all core features are ready for mainnet launch
|
||||
- **User Experience Enhancement**: Improving onboarding flows, dashboard functionality, and overall usability
|
||||
- **Network Growth**: Enabling increased participation in staking, liquidity provision, and governance
|
||||
|
||||
## Task List
|
||||
|
||||
### SDK
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:sdk`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/01/22
|
||||
|
||||
#### Description
|
||||
|
||||
Implement SDK functionality for claiming Karma, distributing Karma, and authentication.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- SDK implementation
|
||||
- Karma claiming functionality
|
||||
- Karma distribution functionality
|
||||
- Authentication system
|
||||
|
||||
### Proxy API
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:proxy-api`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/01/22
|
||||
|
||||
#### Description
|
||||
|
||||
Set up proxy API infrastructure including Status RPC proxy, Status Market proxy, with dedicated credentials and quota management.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Status RPC proxy implementation
|
||||
- Status Market proxy implementation
|
||||
- Credential and quota management system
|
||||
|
||||
### Depositing
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:depositing`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/01/15
|
||||
|
||||
#### Description
|
||||
|
||||
Implement depositing functionality with GUSD vault integration.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Depositing interface
|
||||
- GUSD vault integration
|
||||
- Transaction handling
|
||||
|
||||
### Karma Evolution
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:karma-evolution`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/01/08
|
||||
* end-date: 2026/01/29
|
||||
|
||||
#### Description
|
||||
|
||||
Implement Karma evolution system including Karma progress tracking and transaction allowance management.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Karma progress system
|
||||
- Transaction allowance functionality
|
||||
- Evolution tracking
|
||||
|
||||
### NFT Evolution
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:nft-evolution`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/01/08
|
||||
* end-date: 2026/01/31
|
||||
|
||||
#### Description
|
||||
|
||||
Implement NFT evolution system based on contracts and Karma integration.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- NFT evolution system
|
||||
- Contract integration
|
||||
- Karma-based NFT logic
|
||||
|
||||
### Backend
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:backend`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/01/15
|
||||
* end-date: 2026/02/28
|
||||
|
||||
#### Description
|
||||
|
||||
Implement backend functionality for leaderboard and app discovery features.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Leaderboard backend
|
||||
- App discovery backend
|
||||
- API endpoints
|
||||
|
||||
### QA
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:qa`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/01/15
|
||||
* end-date: 2026/01/29
|
||||
|
||||
#### Description
|
||||
|
||||
Define test cases for QA testing of SN Hub features and functionality.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Test case documentation
|
||||
- Test plan
|
||||
- QA reports
|
||||
|
||||
### Selfhosting
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:selfhosting`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/01/15
|
||||
* end-date: 2026/01/29
|
||||
|
||||
#### Description
|
||||
|
||||
Set up self-hosting infrastructure and deployment processes for SN Hub.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Self-hosting configuration
|
||||
- Deployment documentation
|
||||
- Infrastructure setup
|
||||
|
||||
### Translations
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:i18n`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/01/22
|
||||
* end-date: 2026/02/05
|
||||
|
||||
#### Description
|
||||
|
||||
Implement internationalization (i18n) support for SN Hub to enable multi-language functionality.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- i18n implementation
|
||||
- Translation files
|
||||
- Language selector
|
||||
|
||||
### SEO
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-hub:seo`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/01/22
|
||||
* end-date: 2026/02/05
|
||||
|
||||
#### Description
|
||||
|
||||
Implement SEO optimization for SN Hub to improve search engine visibility and discoverability.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- SEO implementation
|
||||
- Meta tags and structured data
|
||||
- SEO audit and optimization report
|
||||
95
content/web/status/2026q1-sn-website.md
Normal file
95
content/web/status/2026q1-sn-website.md
Normal file
@@ -0,0 +1,95 @@
|
||||
---
|
||||
title: SN Website
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "status"
|
||||
draft: false
|
||||
description: "Development and optimization of the Status Network website to showcase network features, provide documentation, and support community engagement."
|
||||
---
|
||||
|
||||
`vac:web:status:2026q1-sn-website`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves developing and optimizing the Status Network website to showcase network features, provide comprehensive documentation, and support community engagement. The website serves as the primary information hub for the Status Network ecosystem.
|
||||
|
||||
The SN website development will support Status Network's strategic objectives by:
|
||||
- **Network Showcase**: Presenting Status Network features, capabilities, and use cases
|
||||
- **Documentation Hub**: Providing comprehensive technical documentation and guides
|
||||
- **Community Engagement**: Supporting community activities, events, and participation
|
||||
- **User Onboarding**: Helping new users understand and get started with Status Network
|
||||
|
||||
## Task List
|
||||
|
||||
### SEO
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-website:seo`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/01/29
|
||||
* end-date: 2026/02/12
|
||||
|
||||
#### Description
|
||||
|
||||
Implement SEO optimization for the Status Network website to improve search engine visibility and discoverability.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- SEO implementation
|
||||
- Meta tags and structured data
|
||||
- SEO audit and optimization report
|
||||
|
||||
### Translations
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-website:translations`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/01/29
|
||||
* end-date: 2026/02/12
|
||||
|
||||
#### Description
|
||||
|
||||
Implement translations support with public contribution flow for community translations.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Translation system implementation
|
||||
- Public contribution flow integration
|
||||
- Translation files
|
||||
|
||||
### Analytics
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-website:analytics`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/05
|
||||
* end-date: 2026/02/19
|
||||
|
||||
#### Description
|
||||
|
||||
Implement analytics with campaign tag management for tracking and measuring website performance.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Analytics implementation
|
||||
- Campaign tag management system
|
||||
- Tracking configuration
|
||||
|
||||
### Selfhosting
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-sn-website:selfhosting`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/05
|
||||
* end-date: 2026/02/19
|
||||
|
||||
#### Description
|
||||
|
||||
Set up self-hosting infrastructure with infrastructure team's CDN guarantees and automated CI integration.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Self-hosting configuration
|
||||
- CDN setup
|
||||
- CI/CD pipeline integration
|
||||
41
content/web/status/2026q1-status-app.md
Normal file
41
content/web/status/2026q1-status-app.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Status App
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "status"
|
||||
draft: false
|
||||
description: "Supporting continued development of Status App by ensuring web applications, interfaces, and extensions remain functional during native app upgrades, refactoring, and protocol improvements."
|
||||
---
|
||||
|
||||
`vac:web:status:2026q1-status-app`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves supporting the continued development of the Status App by ensuring that web applications, interfaces, and extensions remain functional and compatible during native app upgrades, refactoring, and protocol improvements. As the Status App undergoes ongoing development and enhancements, the Web unit ensures that all web-based components continue to work seamlessly.
|
||||
|
||||
The Status App web support will support Status' strategic objectives by:
|
||||
- **Compatibility Maintenance**: Ensuring web applications and interfaces remain functional during native app upgrades
|
||||
- **User Experience Continuity**: Preventing disruption to web-based user experiences during development
|
||||
- **Protocol Integration**: Supporting new protocol features and improvements in web interfaces
|
||||
- **Feature Parity**: Maintaining feature consistency between native and web implementations
|
||||
|
||||
## Task List
|
||||
|
||||
### External Social Link Preview
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-app:external-social-link-preview`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/26
|
||||
* end-date: 2026/03/12
|
||||
|
||||
#### Description
|
||||
|
||||
Implement external social link preview functionality for shared posts in the Status App web interface.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Link preview implementation
|
||||
- Social media integration
|
||||
- Preview UI components
|
||||
239
content/web/status/2026q1-status-wallet-extension.md
Normal file
239
content/web/status/2026q1-status-wallet-extension.md
Normal file
@@ -0,0 +1,239 @@
|
||||
---
|
||||
title: Status Wallet Extension
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "status"
|
||||
draft: false
|
||||
description: "Continued development and enhancement of the browser wallet extension focused on trading and investor utility, featuring multi-chain swaps, portfolio management, and real-time token tracking."
|
||||
---
|
||||
|
||||
`vac:web:status:2026q1-status-wallet-extension`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves continued development and enhancement of the Status Wallet Extension, building upon the MVP to add advanced features, improve trading capabilities, and expand the portfolio management functionality. The extension serves as a comprehensive trading wallet and token price tracker for casual and meme coin traders and investors.
|
||||
|
||||
The Status Wallet Extension development will support Status' strategic objectives by:
|
||||
- **Feature Expansion**: Adding advanced trading features, social aspects, and enhanced portfolio management
|
||||
- **Revenue Optimization**: Improving swap fees, bridge transactions, and subscription models
|
||||
- **User Experience Enhancement**: Refining UI/UX based on user feedback and market research
|
||||
- **Market Expansion**: Reaching broader audiences through improved features and marketing integration
|
||||
|
||||
## Task List
|
||||
|
||||
### Proxy API Rate Limiting
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:proxy-api-rate-limiting`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/02/05
|
||||
* end-date: 2026/02/19
|
||||
|
||||
#### Description
|
||||
|
||||
Implement proxy API rate limiting to manage API usage and prevent abuse.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Rate limiting implementation
|
||||
- API quota management
|
||||
- Rate limit configuration
|
||||
|
||||
### QA Defining Test Cases Together
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:qa-defining-test-cases-together`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/05
|
||||
* end-date: 2026/02/19
|
||||
|
||||
#### Description
|
||||
|
||||
Collaborate with QA team to define comprehensive test cases for wallet extension features and functionality.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Test case documentation
|
||||
- Test plan
|
||||
- QA collaboration notes
|
||||
|
||||
### Value Chart
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:value-chart`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/12
|
||||
* end-date: 2026/03/05
|
||||
|
||||
#### Description
|
||||
|
||||
Implement value chart functionality to display portfolio value over time.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Value chart component
|
||||
- Chart data integration
|
||||
- UI implementation
|
||||
|
||||
### Hide Small Balances
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:hide-small-balances`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/02/12
|
||||
* end-date: 2026/02/26
|
||||
|
||||
#### Description
|
||||
|
||||
Implement feature to hide small token balances from the wallet view for cleaner UI.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Hide small balances functionality
|
||||
- User preference settings
|
||||
- UI toggle implementation
|
||||
|
||||
### LI.FI Swap Integration
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:lifi-swap-integration`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/12
|
||||
* end-date: 2026/03/05
|
||||
|
||||
#### Description
|
||||
|
||||
Integrate LI.FI swap functionality to enable multi-chain token swaps within the wallet extension.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- LI.FI integration
|
||||
- Swap interface
|
||||
- Multi-chain support
|
||||
|
||||
### Send NFT
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:send-nft`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/19
|
||||
* end-date: 2026/03/05
|
||||
|
||||
#### Description
|
||||
|
||||
Implement functionality to send NFTs from the wallet extension.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Send NFT feature
|
||||
- NFT transfer interface
|
||||
- Transaction handling
|
||||
|
||||
### Global Password
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:global-password`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/02/19
|
||||
* end-date: 2026/03/05
|
||||
|
||||
#### Description
|
||||
|
||||
Implement global password functionality for unified authentication across wallet features.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Global password system
|
||||
- Authentication integration
|
||||
- Password management UI
|
||||
|
||||
### Multi Account
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:multi-account`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/26
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Implement multi-account support to allow users to manage multiple accounts within the wallet extension.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Multi-account functionality
|
||||
- Account switching interface
|
||||
- Account management UI
|
||||
|
||||
### Multi Wallet
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:multi-wallet`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/26
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Implement multi-wallet support to allow users to connect and manage multiple wallets simultaneously.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Multi-wallet functionality
|
||||
- Wallet connection management
|
||||
- Wallet switching interface
|
||||
|
||||
### Dapp Connection
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:dapp-connection`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/19
|
||||
|
||||
#### Description
|
||||
|
||||
Implement dApp connection functionality to enable wallet extension to connect with decentralized applications.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- dApp connection system
|
||||
- Connection approval interface
|
||||
- dApp integration support
|
||||
|
||||
### Hardware Wallets
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:hardware-wallets`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/03/05
|
||||
* end-date: 2026/03/26
|
||||
|
||||
#### Description
|
||||
|
||||
Implement hardware wallet support with QR code-based connection and Keycard Shell integration.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Hardware wallet integration
|
||||
- QR code connection system
|
||||
- Keycard Shell support
|
||||
|
||||
### Browser and System Notifications
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:browser-system-notifications`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/03/12
|
||||
* end-date: 2026/03/26
|
||||
|
||||
#### Description
|
||||
|
||||
Implement browser and system notifications to alert users of wallet activities and transactions.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Notification system implementation
|
||||
- Browser notification integration
|
||||
- System notification support
|
||||
96
content/web/status/2026q1-status-website.md
Normal file
96
content/web/status/2026q1-status-website.md
Normal file
@@ -0,0 +1,96 @@
|
||||
---
|
||||
title: Status Website
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "web"
|
||||
- "status"
|
||||
draft: false
|
||||
description: "Continued optimization and maintenance of the Status website with internationalization support and SEO improvements to enhance global accessibility and discoverability."
|
||||
---
|
||||
|
||||
`vac:web:status:2026q1-status-website`
|
||||
|
||||
## Description
|
||||
|
||||
This commitment involves continued optimization and maintenance of the Status website, building upon previous work to enhance internationalization, improve SEO, and maintain high-quality user experience. The website serves as the primary public-facing interface for the Status ecosystem.
|
||||
|
||||
The Status website optimization will support Status' strategic objectives by:
|
||||
- **Global Accessibility**: Expanding internationalization support to reach broader global audiences
|
||||
- **Discoverability**: Improving SEO to increase organic traffic and user acquisition
|
||||
- **User Experience**: Maintaining and enhancing website performance and usability
|
||||
- **Content Updates**: Keeping website content current with latest Status developments and features
|
||||
|
||||
## Task List
|
||||
|
||||
### SEO
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-website:seo`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/02/12
|
||||
* end-date: 2026/02/26
|
||||
|
||||
#### Description
|
||||
|
||||
Implement SEO optimization for the Status website to improve search engine visibility and discoverability.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- SEO implementation
|
||||
- Meta tags and structured data
|
||||
- SEO audit and optimization report
|
||||
|
||||
### Translations
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-website:translations`
|
||||
* owner: jkbktl
|
||||
* status: not started
|
||||
* start-date: 2026/02/12
|
||||
* end-date: 2026/02/26
|
||||
|
||||
#### Description
|
||||
|
||||
Implement translations support with design improvements, public contribution flow, and automatic addition of copy to base English translation file.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Translation system implementation
|
||||
- Public contribution flow
|
||||
- Automatic translation file updates
|
||||
- Translation UI design
|
||||
|
||||
### Copy Changes, Section Reduction
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-website:copy-changes-section-reduction`
|
||||
* owner: JulesFiliot
|
||||
* status: not started
|
||||
* start-date: 2026/02/19
|
||||
* end-date: 2026/03/05
|
||||
|
||||
#### Description
|
||||
|
||||
Update website copy and reduce sections to improve clarity and user experience.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated copy content
|
||||
- Section reduction implementation
|
||||
- Content review documentation
|
||||
|
||||
### Selfhosting
|
||||
|
||||
* fully qualified name: `vac:web:status:2026q1-status-website:selfhosting`
|
||||
* owner: jinhojang6
|
||||
* status: not started
|
||||
* start-date: 2026/02/26
|
||||
* end-date: 2026/03/12
|
||||
|
||||
#### Description
|
||||
|
||||
Set up self-hosting infrastructure and deployment processes for the Status website.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Self-hosting configuration
|
||||
- Deployment documentation
|
||||
- Infrastructure setup
|
||||
Reference in New Issue
Block a user