May 17, 2026, 11:40 PM
This commit is contained in:
Paweł Domański
@@ -0,0 +1,2 @@
|
||||
.env
|
||||
__pycache__/
|
||||
@@ -0,0 +1,54 @@
|
||||
# Agentone Crew
|
||||
|
||||
Welcome to the Agentone Crew project, powered by [crewAI](https://crewai.com). This template is designed to help you set up a multi-agent AI system with ease, leveraging the powerful and flexible framework provided by crewAI. Our goal is to enable your agents to collaborate effectively on complex tasks, maximizing their collective intelligence and capabilities.
|
||||
|
||||
## Installation
|
||||
|
||||
Ensure you have Python >=3.10 <=3.13 installed on your system. This project uses [UV](https://docs.astral.sh/uv/) for dependency management and package handling, offering a seamless setup and execution experience.
|
||||
|
||||
First, if you haven't already, install uv:
|
||||
|
||||
```bash
|
||||
pip install uv
|
||||
```
|
||||
|
||||
Next, navigate to your project directory and install the dependencies:
|
||||
|
||||
(Optional) Lock the dependencies and install them by using the CLI command:
|
||||
```bash
|
||||
crewai install
|
||||
```
|
||||
### Customizing
|
||||
|
||||
**Add your `OPENAI_API_KEY` into the `.env` file**
|
||||
|
||||
- Modify `src/agentone/config/agents.yaml` to define your agents
|
||||
- Modify `src/agentone/config/tasks.yaml` to define your tasks
|
||||
- Modify `src/agentone/crew.py` to add your own logic, tools and specific args
|
||||
- Modify `src/agentone/main.py` to add custom inputs for your agents and tasks
|
||||
|
||||
## Running the Project
|
||||
|
||||
To kickstart your crew of AI agents and begin task execution, run this from the root folder of your project:
|
||||
|
||||
```bash
|
||||
$ crewai run
|
||||
```
|
||||
|
||||
This command initializes the agentone Crew, assembling the agents and assigning them tasks as defined in your configuration.
|
||||
|
||||
This example, unmodified, will run the create a `report.md` file with the output of a research on LLMs in the root folder.
|
||||
|
||||
## Understanding Your Crew
|
||||
|
||||
The agentone Crew is composed of multiple AI agents, each with unique roles, goals, and tools. These agents collaborate on a series of tasks, defined in `config/tasks.yaml`, leveraging their collective skills to achieve complex objectives. The `config/agents.yaml` file outlines the capabilities and configurations of each agent in your crew.
|
||||
|
||||
## Support
|
||||
|
||||
For support, questions, or feedback regarding the Agentone Crew or crewAI.
|
||||
- Visit our [documentation](https://docs.crewai.com)
|
||||
- Reach out to us through our [GitHub repository](https://github.com/joaomdmoura/crewai)
|
||||
- [Join our Discord](https://discord.com/invite/X4JWnZnxPb)
|
||||
- [Chat with our docs](https://chatg.pt/DWjSBZn)
|
||||
|
||||
Let's create wonders together with the power and simplicity of crewAI.
|
||||
@@ -0,0 +1,20 @@
|
||||
[project]
|
||||
name = "agentone"
|
||||
version = "0.1.0"
|
||||
description = "agentone using crewAI"
|
||||
authors = [{ name = "Your Name", email = "you@example.com" }]
|
||||
requires-python = ">=3.10,<=3.13"
|
||||
dependencies = [
|
||||
"crewai[tools]>=0.80.0,<1.0.0"
|
||||
]
|
||||
|
||||
[project.scripts]
|
||||
agentone = "agentone.main:run"
|
||||
run_crew = "agentone.main:run"
|
||||
train = "agentone.main:train"
|
||||
replay = "agentone.main:replay"
|
||||
test = "agentone.main:test"
|
||||
|
||||
[build-system]
|
||||
requires = ["hatchling"]
|
||||
build-backend = "hatchling.build"
|
||||
@@ -0,0 +1,189 @@
|
||||
# Report on WP Engine and WordPress Developments
|
||||
|
||||
## Introduction
|
||||
|
||||
This report provides a comprehensive overview of recent developments in the WordPress ecosystem and WP Engine's contributions as of 2023. The aim is to present detailed insights into the latest features, acquisitions, partnerships, and community growth that are shaping the future of WordPress and WP Engine's role within it.
|
||||
|
||||
## 1. WP Engine Launches Atlas for Headless WordPress Development
|
||||
|
||||
WP Engine has introduced **Atlas**, a groundbreaking platform designed for headless WordPress development. Atlas seamlessly integrates the robust content management capabilities of WordPress with modern frontend frameworks such as React and Vue.js. This combination allows developers to build highly dynamic, performant, and scalable websites.
|
||||
|
||||
### Key Features of Atlas:
|
||||
|
||||
- **Integrated Development Environment**: Atlas provides tools and plugins that simplify the development workflow, including headless WordPress starters and local development environments.
|
||||
- **Scalability**: With headless architecture, content delivery is decoupled from the frontend, allowing for better performance and scalability.
|
||||
- **Enhanced Security**: By separating the frontend from the backend, Atlas reduces the attack surface, enhancing the overall security of websites.
|
||||
|
||||
### Impact on Developers:
|
||||
|
||||
Developers can now leverage their preferred frontend technologies while still benefiting from WordPress's powerful CMS capabilities. This opens up new possibilities for creating rich user experiences and pushing the boundaries of web development.
|
||||
|
||||
## 2. WordPress 6.3 "Lionel" Released
|
||||
|
||||
In August 2023, WordPress released **version 6.3**, nicknamed "**Lionel**" in honor of jazz legend **Lionel Hampton**. This release introduces significant enhancements aimed at improving the user experience, site editing capabilities, and overall performance.
|
||||
|
||||
### Highlights of WordPress 6.3:
|
||||
|
||||
- **Enhanced Site Editor**: The Site Editor now offers more flexibility, allowing users to edit templates and template parts with ease.
|
||||
- **New Design Tools**: Introduction of new blocks, improved typography controls, and expanded color options provide users with greater creative freedom.
|
||||
- **Performance Improvements**: Optimizations in loading times, script handling, and image processing contribute to a faster and more efficient website performance.
|
||||
- **Accessibility Enhancements**: Commitment to inclusivity with updates that make WordPress more accessible to users with disabilities.
|
||||
- **Integration of Block Themes**: Better support and features for block themes, encouraging users to adopt the full-site editing experience.
|
||||
|
||||
### Benefits for Users:
|
||||
|
||||
The "Lionel" release empowers users to build and customize their websites without extensive coding knowledge, making WordPress an even more user-friendly platform.
|
||||
|
||||
## 3. WP Engine Acquires Frost Theme
|
||||
|
||||
WP Engine has acquired the **Frost** theme, a modern and minimalist WordPress theme optimized for the block editor. This strategic acquisition enhances WP Engine's offerings within the **Genesis Framework**, providing developers and designers with more tools for creating visually appealing websites.
|
||||
|
||||
### Features of the Frost Theme:
|
||||
|
||||
- **Block Editor Optimization**: Designed specifically to work seamlessly with WordPress's block editor (Gutenberg), enabling intuitive design experiences.
|
||||
- **Minimalist Design**: Offers a clean and modern aesthetic that can be customized to fit various brand identities.
|
||||
- **Responsive and Mobile-Friendly**: Ensures websites look great on all devices, enhancing user engagement and experience.
|
||||
- **Integration with Genesis Framework**: Provides developers with powerful features and tools inherent in the Genesis ecosystem.
|
||||
|
||||
### Implications for WP Engine:
|
||||
|
||||
- **Enhanced Offerings**: Strengthens WP Engine's position in providing premium themes and tools to its customers.
|
||||
- **Community Growth**: Encourages more developers to adopt the Genesis Framework, fostering innovation within the WordPress community.
|
||||
|
||||
## 4. Advancements in Full Site Editing (FSE)
|
||||
|
||||
WordPress continues to advance its **Full Site Editing (FSE)** capabilities, revolutionizing how users build and customize their websites. FSE allows users to edit all parts of their site—including headers, footers, sidebars, and more—using the block editor.
|
||||
|
||||
### Key Developments:
|
||||
|
||||
- **Global Styles**: Users can now define and manage styles that affect the entire site from a single interface.
|
||||
- **Template Editing**: Create and modify templates for different post types and pages without leaving the editor.
|
||||
- **Block Patterns and Variations**: Introduction of reusable design elements that streamline the site-building process.
|
||||
- **Enhanced User Interface**: Improvements in the editor's interface make navigation and editing more intuitive.
|
||||
|
||||
### Advantages for Users:
|
||||
|
||||
- **Greater Control**: Users have unprecedented control over their site's appearance without needing to delve into code.
|
||||
- **Efficiency**: Faster site building and customization process, reducing the time to launch.
|
||||
- **Customization**: Ability to create unique designs tailored to specific needs and preferences.
|
||||
|
||||
## 5. WP Engine Enhances Security Features
|
||||
|
||||
WP Engine has rolled out advanced security features to protect WordPress environments against evolving cyber threats.
|
||||
|
||||
### Security Enhancements Include:
|
||||
|
||||
- **Real-Time Threat Detection**: Continuous monitoring for malicious activities and vulnerabilities specific to WordPress.
|
||||
- **Automated Patching**: Swift deployment of security patches to address known vulnerabilities without user intervention.
|
||||
- **Malware Scanning and Removal**: Regular scans to detect malware with tools to automatically remove identified threats.
|
||||
- **DDoS Protection**: Mitigation strategies to protect websites from Distributed Denial of Service attacks.
|
||||
- **Security Audit Logs**: Detailed logs that track changes and activities for auditing and compliance purposes.
|
||||
|
||||
### Benefits:
|
||||
|
||||
- **Peace of Mind**: Users can focus on their business without worrying about security risks.
|
||||
- **Compliance**: Helps businesses meet regulatory requirements related to data security and privacy.
|
||||
- **Reputation Management**: Protects brands from the negative impact of security breaches.
|
||||
|
||||
## 6. Introduction of Pattern Directory in WordPress
|
||||
|
||||
WordPress has launched the **Pattern Directory**, an online repository of pre-designed block patterns that users can insert into their pages and posts.
|
||||
|
||||
### Features of the Pattern Directory:
|
||||
|
||||
- **Variety of Designs**: Offers a wide range of patterns, including galleries, call-to-action sections, headers, and more.
|
||||
- **Ease of Use**: Users can browse, preview, and insert patterns directly from the block editor.
|
||||
- **Community Contributions**: Designers and developers can submit their patterns, enriching the repository.
|
||||
- **Customization**: Patterns can be modified after insertion to tailor them to specific needs.
|
||||
|
||||
### Impact on Content Creation:
|
||||
|
||||
- **Accelerated Design Process**: Reduces the time needed to create complex layouts.
|
||||
- **Consistency**: Helps maintain design consistency across different pages and posts.
|
||||
- **Accessibility**: Provides professionally designed elements to users without design expertise.
|
||||
|
||||
## 7. WP Engine's Partnership with Cloudflare
|
||||
|
||||
WP Engine has entered into a strategic partnership with **Cloudflare**, integrating enterprise-grade Content Delivery Network (CDN) and security services directly into their hosting plans.
|
||||
|
||||
### Highlights of the Partnership:
|
||||
|
||||
- **Enhanced Site Speed**: Leveraging Cloudflare's global CDN to deliver content faster to users worldwide.
|
||||
- **Improved Reliability**: Reduced latency and downtime, ensuring websites are consistently accessible.
|
||||
- **Robust Security**: Protection against DDoS attacks, malicious traffic, and other online threats.
|
||||
- **Advanced Features**: Access to HTTP/3, intelligent routing, and other cutting-edge technologies.
|
||||
|
||||
### Benefits for WP Engine Customers:
|
||||
|
||||
- **Performance Optimization**: Faster load times contribute to better user experiences and SEO rankings.
|
||||
- **Security Assurance**: Comprehensive protection enhances site integrity and trustworthiness.
|
||||
- **Cost Efficiency**: Integrated services reduce the need for additional third-party solutions.
|
||||
|
||||
## 8. Focus on Accessibility Improvements
|
||||
|
||||
Accessibility has been a significant focus for both WP Engine and WordPress, aiming to make the web more inclusive for individuals with disabilities.
|
||||
|
||||
### WordPress 6.3 Accessibility Enhancements:
|
||||
|
||||
- **Keyboard Navigation Improvements**: Enhanced navigation within the editor for users relying on keyboards.
|
||||
- **Screen Reader Support**: Better support for screen readers with improved ARIA labels and announcements.
|
||||
- **Contrast Adjustments**: Default themes updated to ensure sufficient color contrast ratios.
|
||||
- **Form Labeling**: Correct labeling of forms and inputs to assist users with assistive technologies.
|
||||
|
||||
### WP Engine's Commitment:
|
||||
|
||||
- **Accessibility Audits**: Regular assessments of themes and plugins for compliance with WCAG 2.1 guidelines.
|
||||
- **Educational Resources**: Providing guidance and best practices for developers to create accessible content.
|
||||
- **Inclusive Design**: Encouraging the adoption of design principles that cater to a diverse user base.
|
||||
|
||||
### Importance:
|
||||
|
||||
- **Legal Compliance**: Helps site owners comply with regulations like the Americans with Disabilities Act (ADA).
|
||||
- **Expanded Audience**: Makes content accessible to a wider audience, enhancing user engagement and satisfaction.
|
||||
- **Ethical Responsibility**: Supports the global initiative for an inclusive internet.
|
||||
|
||||
## 9. WP Engine's Managed WooCommerce Hosting
|
||||
|
||||
WP Engine has expanded its services with optimized hosting solutions specifically tailored for **WooCommerce**, the leading eCommerce plugin for WordPress.
|
||||
|
||||
### Features of Managed WooCommerce Hosting:
|
||||
|
||||
- **Performance Optimization**: Infrastructure tuned for faster page loads and checkout processes.
|
||||
- **Scalability**: Handles high traffic volumes, ensuring store availability during peak times.
|
||||
- **Specialized Tools**: Includes features like Elasticsearch, instant store search, and advanced caching.
|
||||
- **Security Measures**: Enhanced security protocols to protect sensitive customer data and transactions.
|
||||
- **24/7 Support**: Access to WooCommerce experts for technical assistance.
|
||||
|
||||
### Advantages for Online Stores:
|
||||
|
||||
- **Improved Conversion Rates**: Faster and more reliable stores lead to better customer experiences and increased sales.
|
||||
- **Lower Maintenance**: Managed services reduce the technical burden on store owners.
|
||||
- **Competitive Edge**: Access to advanced features helps businesses stand out in the crowded eCommerce landscape.
|
||||
|
||||
## 10. Growth of the WordPress Community and Ecosystem
|
||||
|
||||
As of 2023, WordPress powers over **43% of all websites** on the internet, reflecting significant growth in its adoption and influence.
|
||||
|
||||
### Community Developments:
|
||||
|
||||
- **WordCamps and Meetups**: Resumption of global events fostering knowledge sharing and networking among users, developers, and enthusiasts.
|
||||
- **Contributions to Core**: Increased community contributions to WordPress core, plugins, themes, and translations.
|
||||
- **Educational Resources**: Expansion of tutorials, online courses, and documentation to support users of all skill levels.
|
||||
|
||||
### Ecosystem Expansion:
|
||||
|
||||
- **Plugin and Theme Growth**: Thousands of new plugins and themes added to the repository, enhancing functionality and customization options.
|
||||
- **Integration with Emerging Technologies**: Adoption of AI, machine learning, and other technologies within the WordPress ecosystem.
|
||||
- **Commercial Opportunities**: Growth in WordPress-based businesses, including agencies, hosting providers, and service vendors.
|
||||
|
||||
### Significance:
|
||||
|
||||
- **Innovation**: A thriving community drives innovation, ensuring WordPress remains a leading platform.
|
||||
- **Economic Impact**: Supports a vast economy of developers, designers, and businesses globally.
|
||||
- **Collaborative Culture**: Emphasizes the importance of open-source collaboration and shared success.
|
||||
|
||||
## Conclusion
|
||||
|
||||
The developments highlighted in this report underscore the dynamic and evolving nature of WordPress and WP Engine's pivotal role in this ecosystem. From technological advancements like headless development with Atlas to the emphasis on accessibility and security, these strides reflect a commitment to innovation, inclusivity, and user empowerment. The continued growth of the WordPress community and its expansive ecosystem promises a vibrant future for content creators, developers, and businesses worldwide.
|
||||
|
||||
---
|
||||
@@ -0,0 +1,19 @@
|
||||
researcher:
|
||||
role: >
|
||||
{topic} Senior Data Researcher
|
||||
goal: >
|
||||
Uncover cutting-edge developments in {topic}
|
||||
backstory: >
|
||||
You're a seasoned researcher with a knack for uncovering the latest
|
||||
developments in {topic}. Known for your ability to find the most relevant
|
||||
information and present it in a clear and concise manner.
|
||||
|
||||
reporting_analyst:
|
||||
role: >
|
||||
{topic} Reporting Analyst
|
||||
goal: >
|
||||
Create detailed reports based on {topic} data analysis and research findings
|
||||
backstory: >
|
||||
You're a meticulous analyst with a keen eye for detail. You're known for
|
||||
your ability to turn complex data into clear and concise reports, making
|
||||
it easy for others to understand and act on the information you provide.
|
||||
@@ -0,0 +1,17 @@
|
||||
research_task:
|
||||
description: >
|
||||
Conduct a thorough research about {topic}
|
||||
Make sure you find any interesting and relevant information given
|
||||
the current year is 2024.
|
||||
expected_output: >
|
||||
A list with 10 bullet points of the most relevant information about {topic}
|
||||
agent: researcher
|
||||
|
||||
reporting_task:
|
||||
description: >
|
||||
Review the context you got and expand each topic into a full section for a report.
|
||||
Make sure the report is detailed and contains any and all relevant information.
|
||||
expected_output: >
|
||||
A fully fledge reports with the mains topics, each with a full section of information.
|
||||
Formatted as markdown without '```'
|
||||
agent: reporting_analyst
|
||||
@@ -0,0 +1,54 @@
|
||||
from crewai import Agent, Crew, Process, Task
|
||||
from crewai.project import CrewBase, agent, crew, task
|
||||
|
||||
# Uncomment the following line to use an example of a custom tool
|
||||
# from agentone.tools.custom_tool import MyCustomTool
|
||||
|
||||
# Check our tools documentations for more information on how to use them
|
||||
# from crewai_tools import SerperDevTool
|
||||
|
||||
@CrewBase
|
||||
class Agentone():
|
||||
"""Agentone crew"""
|
||||
|
||||
agents_config = 'config/agents.yaml'
|
||||
tasks_config = 'config/tasks.yaml'
|
||||
|
||||
@agent
|
||||
def researcher(self) -> Agent:
|
||||
return Agent(
|
||||
config=self.agents_config['researcher'],
|
||||
# tools=[MyCustomTool()], # Example of custom tool, loaded on the beginning of file
|
||||
verbose=True
|
||||
)
|
||||
|
||||
@agent
|
||||
def reporting_analyst(self) -> Agent:
|
||||
return Agent(
|
||||
config=self.agents_config['reporting_analyst'],
|
||||
verbose=True
|
||||
)
|
||||
|
||||
@task
|
||||
def research_task(self) -> Task:
|
||||
return Task(
|
||||
config=self.tasks_config['research_task'],
|
||||
)
|
||||
|
||||
@task
|
||||
def reporting_task(self) -> Task:
|
||||
return Task(
|
||||
config=self.tasks_config['reporting_task'],
|
||||
output_file='report.md'
|
||||
)
|
||||
|
||||
@crew
|
||||
def crew(self) -> Crew:
|
||||
"""Creates the Agentone crew"""
|
||||
return Crew(
|
||||
agents=self.agents, # Automatically created by the @agent decorator
|
||||
tasks=self.tasks, # Automatically created by the @task decorator
|
||||
process=Process.sequential,
|
||||
verbose=True,
|
||||
# process=Process.hierarchical, # In case you wanna use that instead https://docs.crewai.com/how-to/Hierarchical/
|
||||
)
|
||||
@@ -0,0 +1,58 @@
|
||||
#!/usr/bin/env python
|
||||
import sys
|
||||
import warnings
|
||||
|
||||
from agentone.crew import Agentone
|
||||
|
||||
warnings.filterwarnings("ignore", category=SyntaxWarning, module="pysbd")
|
||||
|
||||
# This main file is intended to be a way for you to run your
|
||||
# crew locally, so refrain from adding unnecessary logic into this file.
|
||||
# Replace with inputs you want to test with, it will automatically
|
||||
# interpolate any tasks and agents information
|
||||
|
||||
def run():
|
||||
"""
|
||||
Run the crew.
|
||||
"""
|
||||
inputs = {
|
||||
'topic': 'Napisz mi na temat WP Engine i Wordpress'
|
||||
}
|
||||
Agentone().crew().kickoff(inputs=inputs)
|
||||
|
||||
|
||||
def train():
|
||||
"""
|
||||
Train the crew for a given number of iterations.
|
||||
"""
|
||||
inputs = {
|
||||
"topic": "AI LLMs"
|
||||
}
|
||||
try:
|
||||
Agentone().crew().train(n_iterations=int(sys.argv[1]), filename=sys.argv[2], inputs=inputs)
|
||||
|
||||
except Exception as e:
|
||||
raise Exception(f"An error occurred while training the crew: {e}")
|
||||
|
||||
def replay():
|
||||
"""
|
||||
Replay the crew execution from a specific task.
|
||||
"""
|
||||
try:
|
||||
Agentone().crew().replay(task_id=sys.argv[1])
|
||||
|
||||
except Exception as e:
|
||||
raise Exception(f"An error occurred while replaying the crew: {e}")
|
||||
|
||||
def test():
|
||||
"""
|
||||
Test the crew execution and returns the results.
|
||||
"""
|
||||
inputs = {
|
||||
"topic": "AI LLMs"
|
||||
}
|
||||
try:
|
||||
Agentone().crew().test(n_iterations=int(sys.argv[1]), openai_model_name=sys.argv[2], inputs=inputs)
|
||||
|
||||
except Exception as e:
|
||||
raise Exception(f"An error occurred while replaying the crew: {e}")
|
||||
@@ -0,0 +1,19 @@
|
||||
from crewai.tools import BaseTool
|
||||
from typing import Type
|
||||
from pydantic import BaseModel, Field
|
||||
|
||||
|
||||
class MyCustomToolInput(BaseModel):
|
||||
"""Input schema for MyCustomTool."""
|
||||
argument: str = Field(..., description="Description of the argument.")
|
||||
|
||||
class MyCustomTool(BaseTool):
|
||||
name: str = "Name of my tool"
|
||||
description: str = (
|
||||
"Clear description for what this tool is useful for, you agent will need this information to use it."
|
||||
)
|
||||
args_schema: Type[BaseModel] = MyCustomToolInput
|
||||
|
||||
def _run(self, argument: str) -> str:
|
||||
# Implementation goes here
|
||||
return "this is an example of a tool output, ignore it and move along."
|
||||
Generated
+4239
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user