Pet Plate was founded in 2016 by Renaldo Webb when he decided it was time to feed his first dog Winston real food, so he started cooking for him and soon discovered that there was a tremendous need for Pet Plate

Pet Plate

petplate

Of Progress and the Smallways Family 

Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's Jump right in 🚀 .... I've gathered and put together an Extensive PR Template! Feel free to tailor it further to align with your style. Template Link: https://gist.github.com/smyaseen/ab4ee4a159ba8071aaab6335c4d7423e ..... Contents: ⚡ Wait What?
⚡ But Why?
⚡ But How? 1️⃣ What - PR templates offer a visual snapshot for reviewers to quickly grasp the essence and state of a pull request. Imagine your team diving into a PR and instantly comprehending its purpose, changes, and necessary actions. That's the magic of a well-structured template. 2️⃣ Why - Reason 1: Mind Off the Trivial, Focus on Impactful Say goodbye to mental juggling! Templates serve as a self-checklist, eliminating the need to wrack your brain over remembering small yet crucial details. Instead, channel that mental energy towards crafting exceptional code and solving complex challenges. Reason 2: Living Documentation Treat your PR template as a living, breathing document that captures the essence of each change. It's not just about the present; it's a reference point for the future. Easily traceable and understandable, it becomes a valuable resource for anyone peeking into the history of your codebase. But wait, there's more! 🌟 Reason 3: Consistency & Standardization With PR templates, maintain consistency across your project repositories. Whether you're working on bug fixes, feature enhancements, or other changes, ensure a uniform approach that aligns with your team's best practices. Reason 4: Enhanced Communication These templates aren't just for code; they foster better communication within your team. Express your intentions, highlight potential issues, and open the floor for meaningful discussions—all in one structured format. Reason 5: Effortless Onboarding Simplify onboarding for new team members by providing a clear blueprint for creating effective pull requests. It's like having a welcome mat that guides them through the team's established processes. 3️⃣ How - Create a custom template with Markdown, and name it "PULL_REQUEST_TEMPLATE.md"


Paste the following example: ## Description



## What type of PR is this? (check all applicable)

- [ ] 🍕 Feature - A new feature.
- [ ] 🐛 Bug Fix - self-explanatory
- [ ] 📝 Documentation Update - Documentation and related changes.
- [ ] 🎨 Style - Changes that do not affect the meaning of the code; for example, white space, formatting, or missing semicolons.
- [ ] 🧑‍💻 Code Refactor - A code that neither fixes a bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name).
- [ ] 🔥 Performance Improvements - A code change that improves performance.
- [ ] ✅ Test - Added | Modified | Removed tests
- [ ] 🤖 Build - Changes related to code building (e.g. adding npm dependencies or external libraries).
- [ ] 🔁 CI - Changes that affect the build CI/CD pipeline
- [ ] 📦 Chore - Changes that do not affect the external user (e.g. updating the .gitignore file or .prettierrc file).
- [ ] ⏩ Revert - self-explanatory

## Related Tickets & Documents

## Mobile & Desktop Screenshots/Recordings



## Quality Checklist

- [ ] 👷‍♀️ Created small PR.
- [ ] 👴🏻 No deprecated or outdated code is introduced
- [ ] 💭 Code is self-documenting. Comments are unnecessary and should only be used to explain why a decision was made
- [ ] 🗒️ Methods are documented with JS Doc including description, params, and return type
- [ ] 📋 The commit message follows our guidelines
- [ ] 👌 The pull request description explains any decisions or trade-offs made regarding code quality and design
- [ ] 🔖 The branch follows our naming guidelines

## Self Checklist

- [ ] 👓 I have followed the style guidelines of this project
- [ ] 🤳 I have performed a self-review of my code
- [ ] 🏷️ I have correctly labelled PR & added Ticket Number
- [ ] 🙆‍♂️ I have cleared the Acceptance Criteria
- [ ] ⚠️ My changes generate no new warnings

## Added tests?

- [ ] 👍 yes, new and existing unit tests pass locally with my changes
  - [ ] ♻️ had to make changes to existing tests
- [ ] 🥹 no, because I need help
  - [ ] ⏮️ some existing tests are failing
- [ ] ⌛ no time to add tests
- [ ] 🙅 no, because they aren't needed

## Added to documentation?

- [ ] 📜 README.md
- [ ] 📝 Confluence
- [ ] 🙅 no documentation needed

## [optional] Are there any post-deployment tasks we need to perform?

## [optional] What gif best describes this PR or how it makes you feel? Head to your GitHub repository, select the default branch, and make a .git folder at the root.


Put the template in the folder and commit changes.


Now, every time someone makes a PR, the template will appear. Wrapping Up: We just Elevated Your Development Workflow with a GitHub PR Template. 🚀 ..... Now, you can supercharge your development workflow 🚀 That's it, folks! I hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub LinkedIn Helloooooooo! Helloooooooo! Hope you're doing great! This is SMY! 👋 Let's Jump right in 🚀 .... I've gathered and put together an Extensive PR Template! Feel free to tailor it further to align with your style. Template Link: https://gist.github.com/smyaseen/ab4ee4a159ba8071aaab6335c4d7423e https://gist.github.com/smyaseen/ab4ee4a159ba8071aaab6335c4d7423e ..... Contents: ⚡ Wait What? ⚡ But Why? ⚡ But How? ⚡ Wait What? Wait What? ⚡ But Why? But Why? ⚡ But How? But How? 1️⃣ What - PR templates offer a visual snapshot for reviewers to quickly grasp the essence and state of a pull request. Imagine your team diving into a PR and instantly comprehending its purpose, changes, and necessary actions. That's the magic of a well-structured template. 2️⃣ Why - Reason 1: Mind Off the Trivial, Focus on Impactful Say goodbye to mental juggling! Templates serve as a self-checklist, eliminating the need to wrack your brain over remembering small yet crucial details. Instead, channel that mental energy towards crafting exceptional code and solving complex challenges. Reason 2: Living Documentation Treat your PR template as a living, breathing document that captures the essence of each change. It's not just about the present; it's a reference point for the future. Easily traceable and understandable, it becomes a valuable resource for anyone peeking into the history of your codebase. But wait, there's more! 🌟 Reason 3: Consistency & Standardization With PR templates, maintain consistency across your project repositories. Whether you're working on bug fixes, feature enhancements, or other changes, ensure a uniform approach that aligns with your team's best practices. Reason 4: Enhanced Communication These templates aren't just for code; they foster better communication within your team. Express your intentions, highlight potential issues, and open the floor for meaningful discussions—all in one structured format. Reason 5: Effortless Onboarding Simplify onboarding for new team members by providing a clear blueprint for creating effective pull requests. It's like having a welcome mat that guides them through the team's established processes. 3️⃣ How - Create a custom template with Markdown, and name it "PULL_REQUEST_TEMPLATE.md" Paste the following example: Create a custom template with Markdown, and name it "PULL_REQUEST_TEMPLATE.md" Create a custom template with Markdown, and name it "PULL_REQUEST_ TEMPLATE.md " TEMPLATE.md Paste the following example: Paste the following example: ## Description



## What type of PR is this? (check all applicable)

- [ ] 🍕 Feature - A new feature.
- [ ] 🐛 Bug Fix - self-explanatory
- [ ] 📝 Documentation Update - Documentation and related changes.
- [ ] 🎨 Style - Changes that do not affect the meaning of the code; for example, white space, formatting, or missing semicolons.
- [ ] 🧑‍💻 Code Refactor - A code that neither fixes a bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name).
- [ ] 🔥 Performance Improvements - A code change that improves performance.
- [ ] ✅ Test - Added | Modified | Removed tests
- [ ] 🤖 Build - Changes related to code building (e.g. adding npm dependencies or external libraries).
- [ ] 🔁 CI - Changes that affect the build CI/CD pipeline
- [ ] 📦 Chore - Changes that do not affect the external user (e.g. updating the .gitignore file or .prettierrc file).
- [ ] ⏩ Revert - self-explanatory

## Related Tickets & Documents

## Mobile & Desktop Screenshots/Recordings



## Quality Checklist

- [ ] 👷‍♀️ Created small PR.
- [ ] 👴🏻 No deprecated or outdated code is introduced
- [ ] 💭 Code is self-documenting. Comments are unnecessary and should only be used to explain why a decision was made
- [ ] 🗒️ Methods are documented with JS Doc including description, params, and return type
- [ ] 📋 The commit message follows our guidelines
- [ ] 👌 The pull request description explains any decisions or trade-offs made regarding code quality and design
- [ ] 🔖 The branch follows our naming guidelines

## Self Checklist

- [ ] 👓 I have followed the style guidelines of this project
- [ ] 🤳 I have performed a self-review of my code
- [ ] 🏷️ I have correctly labelled PR & added Ticket Number
- [ ] 🙆‍♂️ I have cleared the Acceptance Criteria
- [ ] ⚠️ My changes generate no new warnings

## Added tests?

- [ ] 👍 yes, new and existing unit tests pass locally with my changes
  - [ ] ♻️ had to make changes to existing tests
- [ ] 🥹 no, because I need help
  - [ ] ⏮️ some existing tests are failing
- [ ] ⌛ no time to add tests
- [ ] 🙅 no, because they aren't needed

## Added to documentation?

- [ ] 📜 README.md
- [ ] 📝 Confluence
- [ ] 🙅 no documentation needed

## [optional] Are there any post-deployment tasks we need to perform?

## [optional] What gif best describes this PR or how it makes you feel? ## Description



## What type of PR is this? (check all applicable)

- [ ] 🍕 Feature - A new feature.
- [ ] 🐛 Bug Fix - self-explanatory
- [ ] 📝 Documentation Update - Documentation and related changes.
- [ ] 🎨 Style - Changes that do not affect the meaning of the code; for example, white space, formatting, or missing semicolons.
- [ ] 🧑‍💻 Code Refactor - A code that neither fixes a bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name).
- [ ] 🔥 Performance Improvements - A code change that improves performance.
- [ ] ✅ Test - Added | Modified | Removed tests
- [ ] 🤖 Build - Changes related to code building (e.g. adding npm dependencies or external libraries).
- [ ] 🔁 CI - Changes that affect the build CI/CD pipeline
- [ ] 📦 Chore - Changes that do not affect the external user (e.g. updating the .gitignore file or .prettierrc file).
- [ ] ⏩ Revert - self-explanatory

## Related Tickets & Documents

## Mobile & Desktop Screenshots/Recordings



## Quality Checklist

- [ ] 👷‍♀️ Created small PR.
- [ ] 👴🏻 No deprecated or outdated code is introduced
- [ ] 💭 Code is self-documenting. Comments are unnecessary and should only be used to explain why a decision was made
- [ ] 🗒️ Methods are documented with JS Doc including description, params, and return type
- [ ] 📋 The commit message follows our guidelines
- [ ] 👌 The pull request description explains any decisions or trade-offs made regarding code quality and design
- [ ] 🔖 The branch follows our naming guidelines

## Self Checklist

- [ ] 👓 I have followed the style guidelines of this project
- [ ] 🤳 I have performed a self-review of my code
- [ ] 🏷️ I have correctly labelled PR & added Ticket Number
- [ ] 🙆‍♂️ I have cleared the Acceptance Criteria
- [ ] ⚠️ My changes generate no new warnings

## Added tests?

- [ ] 👍 yes, new and existing unit tests pass locally with my changes
  - [ ] ♻️ had to make changes to existing tests
- [ ] 🥹 no, because I need help
  - [ ] ⏮️ some existing tests are failing
- [ ] ⌛ no time to add tests
- [ ] 🙅 no, because they aren't needed

## Added to documentation?

- [ ] 📜 README.md
- [ ] 📝 Confluence
- [ ] 🙅 no documentation needed

## [optional] Are there any post-deployment tasks we need to perform?

## [optional] What gif best describes this PR or how it makes you feel? Head to your GitHub repository, select the default branch, and make a .git folder at the root. Put the template in the folder and commit changes. Now, every time someone makes a PR, the template will appear. Head to your GitHub repository, select the default branch, and make a .git folder at the root. Head to your GitHub repository, select the default branch, and make a .git folder at the root. Put the template in the folder and commit changes. Put the template in the folder and commit changes. Now, every time someone makes a PR, the template will appear. Now, every time someone makes a PR, the template will appear. Wrapping Up: We just Elevated Your Development Workflow with a GitHub PR Template. 🚀 ..... Now, you can supercharge your development workflow 🚀 That's it, folks! I hope it was a good read for you. Thank you! ✨ 👉 Follow me GitHub GitHub LinkedIn LinkedIn

How to Elevate Your Development Workflow With GitHub PR Templates! 🌟

Disclaimer: The views and opinions expressed in this article are solely my own and do not necessarily reflect the views оf any institution оr organization. Introduction The complexity of software systems often requires software engineers or managers to write proposals to align teams, organizations, or stakeholders (partner teams, dependent services, etc.) on changes. These proposals help communicate motivation, recommendations, or milestones concisely, while getting feedback and aligning all stakeholders. Such documents also serve as past reference points for new employees taking ownership of software systems and understanding the thought process of how decisions were made in the past. This article provides a generic template for writing one pagers; although not limited to software systems, it has been proven helpful while leading software engineering organizations. Template Overview This will be the executive summary of the document, good for capturing motivation and what you are proposing for readers to get interested in your document. Introduction Provide details on the background/motivation for the change. Metrics/data can be included to explain the problem and provide additional insights. Goals In-scope requirements for this project. Non-Goals Call out any non-goals or out-of-scope tasks for this project. These can be distractions to solving the problem you want to focus on. Options Summarize a list of options/alternatives you considered to solve the problem, preferably with pros & cons for each. Recommendation Based on alternatives discussed in the previous section, provide recommendations for strategic solutions with explanations or supporting arguments. Tactical approach as an option - Based on challenges/timeline associated with achieving the recommended approach, consider providing a tactical solution; potentially, this can be an incremental step toward a strategic solution or minimal change to address the problem in the short term. Testing Describe how you will validate that the feature is working as intended; what will you test for? How will you test it? Will there be a period for gamma or pre-production validation? What will that entail? Make sure to include test cases that verify that the feature only applies to the events where it should apply Milestones List high-level tasks/milestones for recommended solutions with estimates in dev days. To provide this list apart from functional changes, think about: Testing strategy prior to release (unit, integration tests, etc.)
Need for/strategy to backfill
Any changes to metrics/reporting scripts/tools
New metrics/validation steps after release (canaries, pipeline approval workflows)
Security review
Mini operational readiness review References References you think might help readers to dive deep into the problem space or presented alternatives. FAQs Proactively answer any anticipated questions or questions, which might have been brought up in consecutive discussions related to this proposal. Appendix Add any supplementary information to the proposal, which readers can refer to as needed. Meeting # Notes Maintain the below summary for meetings you have the proposal review. Attendees List of people who attended the meeting. MoM (Minutes of Meeting) Summarize the Minutes of the meeting for future reference. Disclaimer : The views and opinions expressed in this article are solely my own and do not necessarily reflect the views оf any institution оr organization. Disclaimer Introduction The complexity of software systems often requires software engineers or managers to write proposals to align teams, organizations, or stakeholders (partner teams, dependent services, etc.) on changes. These proposals help communicate motivation, recommendations, or milestones concisely, while getting feedback and aligning all stakeholders. Such documents also serve as past reference points for new employees taking ownership of software systems and understanding the thought process of how decisions were made in the past. This article provides a generic template for writing one pagers; although not limited to software systems, it has been proven helpful while leading software engineering organizations. Template Overview This will be the executive summary of the document, good for capturing motivation and what you are proposing for readers to get interested in your document. Introduction Provide details on the background/motivation for the change. Metrics/data can be included to explain the problem and provide additional insights. Goals In-scope requirements for this project. Non-Goals Call out any non-goals or out-of-scope tasks for this project. These can be distractions to solving the problem you want to focus on. Options Summarize a list of options/alternatives you considered to solve the problem, preferably with pros & cons for each. Recommendation Based on alternatives discussed in the previous section, provide recommendations for strategic solutions with explanations or supporting arguments. Tactical approach as an option - Based on challenges/timeline associated with achieving the recommended approach, consider providing a tactical solution; potentially, this can be an incremental step toward a strategic solution or minimal change to address the problem in the short term. Tactical approach as an option - Testing Describe how you will validate that the feature is working as intended; what will you test for? How will you test it? Will there be a period for gamma or pre-production validation? What will that entail? Make sure to include test cases that verify that the feature only applies to the events where it should apply Milestones List high-level tasks/milestones for recommended solutions with estimates in dev days. To provide this list apart from functional changes, think about: Testing strategy prior to release (unit, integration tests, etc.) Need for/strategy to backfill Any changes to metrics/reporting scripts/tools New metrics/validation steps after release (canaries, pipeline approval workflows) Security review Mini operational readiness review Testing strategy prior to release (unit, integration tests, etc.) Need for/strategy to backfill Any changes to metrics/reporting scripts/tools New metrics/validation steps after release (canaries, pipeline approval workflows) Security review Mini operational readiness review References References you think might help readers to dive deep into the problem space or presented alternatives. FAQs Proactively answer any anticipated questions or questions, which might have been brought up in consecutive discussions related to this proposal. Appendix Add any supplementary information to the proposal, which readers can refer to as needed. Meeting # Notes Maintain the below summary for meetings you have the proposal review. Attendees Attendees List of people who attended the meeting. MoM (Minutes of Meeting) MoM (Minutes of Meeting) Summarize the Minutes of the meeting for future reference.

The One-Pager Advantage: A Template for Software Engineering Projects

এক-পৃষ্ঠার সুবিধা: সফ্টওয়্যার ইঞ্জিনিয়ারিং প্রকল্পগুলির জন্য একটি টেমপ্লেট

Der One-Pager-Vorteil: Eine Vorlage für Softwareentwicklungsprojekte

La ventaja de una página: una plantilla para proyectos de ingeniería de software

L'avantage d'une page : un modèle pour les projets de génie logiciel

वन-पेजर लाभ: सॉफ्टवेयर इंजीनियरिंग परियोजनाओं के लिए एक टेम्पलेट

ワンページの利点: ソフトウェア エンジニアリング プロジェクト用のテンプレート

한 페이지 분량의 장점: 소프트웨어 엔지니어링 프로젝트를 위한 템플릿

A vantagem de uma página: um modelo para projetos de engenharia de software

Преимущество одной страницы: шаблон для проектов разработки программного обеспечения

Tek Sayfa Avantajı: Yazılım Mühendisliği Projeleri İçin Bir Şablon

Lợi thế của một trang: Mẫu cho các dự án kỹ thuật phần mềm

单页优势：软件工程项目的模板

In this rather short and concise article, I'll try to explain various prompts, structures, and templates that can be used and tweaked to get the most out of LLMs. Let's Dive Into It. Problem-Solution: : Describe the issue or challenge. Problem : Propose a solution or multiple solutions. Solution : Explain the benefits of implementing the solution(s). Benefits : This template outlines a problem or challenge, and then proposes one or more solutions to address it. Explanation : Example Prompt "Identify a pressing environmental issue in your community and propose a comprehensive solution to mitigate its impact." SWOT Analysis: : List internal factors that contribute positively. Strengths : Identify internal factors that are detrimental. Weaknesses : Explore external factors that could be advantageous. Opportunities : Consider external factors that pose risks. Threats : SWOT stands for Strengths, Weaknesses, Opportunities, and Threats. This template helps analyze internal and external factors affecting a situation. Explanation : Example Prompt "Conduct a SWOT analysis of a local small business, considering its internal strengths and weaknesses, as well as external opportunities and threats in the market." Cause and Effect : : Identify the root cause of an issue or event. Cause : Describe the consequences or outcomes. Effect : Discuss the broader implications or significance. Implications : This template explores the relationship between a cause and its effects, helping to understand the underlying mechanisms of a phenomenon. Explanation : Example Prompt "Examine the causes and effects of deforestation in a specific region, considering environmental, economic, and social impacts." Comparison: Describe the first subject for comparison. Subject A: : Describe the second subject for comparison. Subject B Highlight similarities between the two subjects. Key Similarities: : Point out the differences between them. Key Differences : This template highlights similarities and differences between two or more subjects, providing a structured way to evaluate and contrast them. Explanation : Example Prompt "Compare and contrast the educational systems of two different countries, focusing on curriculum structure, teaching methods, and student outcomes." Chronology : : Outline events in chronological order. Past Events : Describe the current state of affairs. Present Situation : Discuss potential future developments. Future Projections : This template arranges events or processes in chronological order, helping to understand their progression over time. Explanation : Example Prompt "Trace the historical development of communication technology from the invention of the printing press to the modern era of social media platforms." Pros&Cons: : List the advantages or positive aspects. Pros : Identify the disadvantages or negative aspects. Cons : Offer considerations or mitigations for the cons. Considerations : This template lists the advantages (pros) and disadvantages (cons) of a particular topic or decision, facilitating a balanced analysis. Explanation : Example Prompt "Evaluate the pros and cons of implementing renewable energy initiatives in a city, considering factors such as cost-effectiveness, environmental impact, and community engagement." Decision-Making : : Present the available choices or options. Options : Establish criteria for evaluating the options. Criteria : Assess each option against the criteria. Evaluation : Make a recommendation or decision based on the evaluation. Decision : This template guides the decision-making process by presenting options, establishing criteria for evaluation, and making a recommendation based on the analysis. Explanation : Example Prompt "You are a project manager tasked with selecting a software development methodology for an upcoming project. Compare agile and waterfall methodologies, evaluate their suitability for the project requirements, and recommend the most appropriate approach." Five W's and One H: : Identify the relevant individuals or groups involved. Who : Define the subject or topic. What : Specify the timing or timeframe. When : Determine the location or context. Where : Explore the reasons or motivations. Why : Describe the methods or processes involved. How : This template prompts exploration by addressing the basic questions of who, what, when, where, why, and how, providing a comprehensive understanding of a topic. Explanation : Example Prompt "Investigate the impact of a natural disaster (such as a hurricane, earthquake, or wildfire) on a local community, addressing who was affected, what damages occurred, when it happened, where it occurred, why it happened, and how the community responded." These templates offer structured frameworks for efficient prompts and better results.

Prompt Engineering Techniques: Structures and Templates

This paper is available on arxiv under CC 4.0 license. Authors: (1) Vogt, Lars, TIB Leibniz Information Centre for Science and Technology; (2) Konrad, Marcel, TIB Leibniz Information Centre for Science and Technology; (3) Prinz, Manuel, TIB Leibniz Information Centre for Science and Technology. Table of Links Abstract & Introduction Interoperability Semantic interoperability and what natural languages like English can teach us Requirements for successfully communicating terms and statements Parallels between the structure of natural language statements and data schemata with implications for semantic interoperability What makes a term a good term and a schema a good schema? The need for a machine-actionable Rosetta Stone for (meta)data that acts as an interlingua for specifying reference terms and reference schemata to support cognitive and semantic interoperability Rosetta Stone and machine-readability: UPRIs, XML Schema datatypes, and RDF for communicating terms, datatypes, and statements Rosetta Stone and machine-interpretability: Wikidata and a modeling paradigm for (meta)data statements based on English Rosetta Stone and semantic interoperability: Specifying term mappings and schema crosswalks Rosetta Stone and cognitive interoperability: Specifying display templates and using a query builder Discussion Related work Conclusion, Acknowledgements, & References Rosetta Stone and cognitive interoperability: Specifying display templates and using a query builder Display templates Humans usually do not want to see the (meta)data of a knowledge graph in the form of triples—they do not want to read them in any of the RDF serializations, nor do they want to visualize them as a graph. In order to display the content of a (meta)data statement modeled according to the Rosetta approach in a human-actionable way, a frontend application needs a display template that specifies how a rendering function can translate a given (meta)data structure into a human-readable statement. Display templates organize information from the (meta)data structure along with additional prepositions to be presented in the UI. For example, if a weight measurement with a 95% confidence interval were stored according to an appropriate reference schema, the schema would specify four literal-object-positions (MAIN_VALUE, UPPER_VALUE, LOWER_VALUE, INTERVAL_VALUE) and one resource-object-position (UNIT). The form-based display template could specify that this information should be displayed in the frontend as ‘SUBJECT has weight (INTERVAL_VALUE% conf. interval): MAIN_VALUE (LOWER_VALUE-UPPER_VALUE) UNIT’. Another example is a travel statement where the corresponding reference schema specifies one required resource-object-position (DESTINATION_LOCATION), two optional resource-object-positions (DEPARTURE_LOCATION, TRANSPORTATION), and one optional literal-object-position (DATETIME). The corresponding display template would display a travel statement in the frontend as ‘PERSON travels by TRANSPORTATION from DEPARTURE_LOCATION to DESTINATION_LOCATION on the DATETIME‘. In other words, the subject-position and the various object-positions (i.e., the syntactic positions with their associated semantic roles) are mapped to corresponding variables within a string to form a human-readable statement (see Fig. 10, top). We call such textual display templates dynamic labels. In addition to textual display templates, it is also possible to specify graphical display templates for a mind-map-like representation of a statement using dynamic mind-map patterns. Dynamic mind-map patterns use a label for the predicate underlying the corresponding statement type and, if there is more than one object-position, labels for relating the various objects to the predicate. As a result, the statement can be visualized as a mind-map like graph, where each subject and object is represented as a node with the label of the corresponding resource from the underlying graph of the (meta)data statement (see Fig. 10, bottom). Such graphical representations of statements can also be combined to form a mind-map of larger contexts and interrelationships that connect the dynamic mind-map patterns of multiple statements. Mind-map-like representations of complex interrelationships between different entities are easier to understand than form-based textual representations, thus increasing the human-actionability of a knowledge graph. (Meta)data can be communicated to the presentation layer in the UI, with the templates filtering the complex data structure for the information relevant to a human user, using dynamic labels and dynamic mind-map patterns to present statements, decoupling human-readable data display from machine-actionable data storage. A given reference schema can have multiple dynamic labels and dynamic mind-map patterns associated with it. It can be beneficial to be able to choose between different display templates depending on the context in which the (meta)data are accessed (PC vs. smartphone, expert user vs. layperson, etc.). The specifications of each display template should be associated with its corresponding reference schema and statement class, thus contributing to the easily accessible and usable Rosetta module mentioned above, moving it even closer to the concept of Knowledge Graph Building Blocks (64). A Rosetta Query-Builder We believe that findability is the most important aspect of any tool that stores and documents (meta)data. If relevant (meta)data cannot be found, no other operations can be performed on it, and interoperability issues become secondary. In the context of knowledge graphs, specific query endpoints have been established along with corresponding graph query languages to interact with the graph. These are SPARQL for RDF- and OWL-based knowledge graphs and Cypher for labeled property graphs such as Neo4J. Our personal experience is that most users and software developers have no experience with graph-based databases, are not familiar with graph query languages and their benefits, and therefore do not see the need to learn them. And even those who are familiar with them report that writing more complex queries can be challenging. Apparently, the need to write SPARQL or Cypher queries is a barrier to interacting with knowledge graphs and hinders their wider use (65). The semantic unit framework introduced some-instance and every-instance resources as two new types of resources in addition to named-individuals, classes, and properties (50). This allows, besides specifying universal statements and negations without having to use blank nodes and simplifying negations and cardinality statements, modeling them as ABox expressions, also representing questions as statements in the graph (for a discussion, see (10,64)). Instead of named-individuals, one uses some-instance resources of a given class for a given slot of a reference schema to specify that the answer to the question may have any instance of that class at that position in any statement of the type to which the reference schema is associated. If you are asking about universal statements, you would use the every-instance resource instead. The resulting statement can be stored as a question within the knowledge graph, by classifying its statement resource to instantiate the ‘question statement’ class. Since all question statements in a given knowledge graph would reflect the structure of their corresponding reference schema, and since all reference schemata have been created according to the same modeling paradigm, one could develop a Rosetta Query-Builder that converts the question into a query that returns a Boolean true/false answer if the subject and object-positions contained fully specified inputs (i.e., named-individual resources), or a list of statements as the answer that match the specifications provided by the question statement if one or more of these positions contained underspecified input (i.e., some-instance, every-instance, or class resources). The same idea provides the basis for developing query interfaces for knowledge graph applications: users can create their own queries with the input forms for creating statements using named-individuals, some-instances, every-instances, classes, and datatypes as inputs for subject and object-positions without having to know and use any graph query languages. The Query-Builder translates the question statements into actual graph queries. The generic structure of the reference schemata greatly facilitates the development of procedures for this translation step. By using Boolean operators (AND and OR) and by reusing object resources as subject resources in another question statement, multiple question statements can be combined to form a more complex question. Question units not only allow you to document questions in the graph, but also to make them operable. This can be used, for example, to document competency questions for a project in a readily actionable way within the knowledge graph itself. The ability to store question statements and make them operable moves the Rosetta Framework another step closer to the concept of Knowledge Graph Building Blocks (64) and further enhances its overall cognitive interoperability.

Rosetta Stone and Cognitive Interoperability: Specifying Display Templates and Using a Query Builder

This paper is available on arxiv under CC 4.0 license. Authors: (1) Ulysse Gazin, Universit´e Paris Cit´e and Sorbonne Universit´e, CNRS, Laboratoire de Probabilit´es, Statistique et Mod´elisation, (2) Gilles Blanchard, Universit´e Paris Saclay, Institut Math´ematique d’Orsay, (3) Etienne Roquain, Sorbonne Universit´e and Universit´e Paris Cit´e, CNRS, Laboratoire de Probabilit´es, Statistique et Mod´elisation. Table of Links Abstract & Introduction Main results Application to prediction intervals Application to novelty detection Conclusion, Acknowledgements and References Appendix A: Exact formulas for Pn,m Appendix B: Numerical bounds and templates Appendix C: Proof Appendix D: Explicit control of (16) for α=0 Appendix E: Proof of Corollary 4.1 Appendix F: The Simes inequality Appendix G: Uniform FDP bound for AdaDetect Appendix H:  Additional experiments B Numerical bounds and templates The bound proposed in Theorem 2.3 are explicit and elegant, but can be conservative in some cases and we develop here the numerical approach mentioned in Remark 2.5. Hence, let us consider

Transductive Conformal Inference With Adaptive Scores: Numerical Bounds and Templates

On the seventh day, amidst the darkness, God granted ProjectDiscovery, aiding brave souls in their perilous pen-testing journey. In the wake of ProjectDiscovery's ascent, tools like Nuclei, Katana, Subfinder, Naabu, and the latest addition, cvemap, emerged to fortify the arsenal of the brave. CVEmap and Nuclei missing feature And most of the were disappointed by the missing feature to “map” results directly to existing nuclei templates. penetration testers cvemap This absolutely necessary feature does not exist today, and I hope it will change - I will create an issue on to address this problem. GitHub However, I decided to fix this problem in this guide myself because a solution might not come at all. Fortunately, the existing nuclei templates use the same naming convention as the CVE one, and nuclei support an argument where you can enter the ID of the desired templates directly into the input.  CVEmap’s flag  nicely informs that the template exists in the Nuclei, but unfortunately, it doesn't tell how and where to find it. -template By combining this information, I came up with an ugly but short solution. Solution A bit of allows us to create the following script. bash glue This script scans targets from a file, with Nuclei templates filtered based on criteria from cvemap. Command expansion ( ) creates the resulting list of template IDs, separated by a comma, which Nuclei accepts as valid template selection. targets.txt $(…) nuclei -l "targets.txt" \
       -id "$(cvemap -template -list-id -silent \
        -age '<365' -q '"remote code execution" is_remote:true' -vendor cisco |
        tr -s '\n' ',')" \
       -o "output.txt" Precisely, in this case, the command scans CVEs of the Cisco products that provide RCE to the attackers and are less than one year old. Isn't that great!? Feel free to change the query on line 3 for your purpose. The other lines are mandatory. Postface Why this feature doesn't exist officially, I don't know, but if I had to bet, it's because they want to use the synergy of these tools in their paid cloud platform, and they don't want to give all the features for free but at the same time they want to be opensource. So they created a flag with the flag, which informs you that the template exists, but which one it is, and so on, you must look up yourself. cvemap -template Resources https://docs.projectdiscovery.io/tools/cvemap/running https://cloud.projectdiscovery.io/?ref=api_key https://github.com/projectdiscovery/cvemap https://github.com/projectdiscovery/nuclei

The Pen-Tester's Arsenal: ProjectDiscovery's CVEmap to Nuclei Template Mapping

In a world where time is money, finding ways to boost productivity is key. One effective strategy is leveraging quality templates. In this article, we'll explore eight game-changing template sites across various categories to help you achieve more in less time. Dive into the world of templates for websites, graphic design, emails, AI prompts, mockups, marketing, copywriting, and more. Say goodbye to repetitive tasks and hello to efficiency with these handpicked resources! Hope these will be useful for your daily workflow! 💻 Websites 👉 htmlrev.com HTMLrev offers a collection of free HTML templates for websites and landing pages. These templates are licensed for personal and commercial projects, providing users with various options for creating and customizing their web presence. 👩‍🎨 Graphics 👉 canva.com/templates Canva provides a platform with professionally designed and customizable templates for various graphic design needs. Users can explore a wide range of templates for different occasions and easily personalize them to suit their creative projects. 📱Mockups 👉 smartmockups.com Smartmockups allow users to create high-resolution product mockups directly within their browsers. The platform offers thousands of mockups and advanced features such as changeable backgrounds, device colors, and a crop tool, providing a seamless experience for visualizing designs. 📪 Emails 👉 beefree.io/templates Beefree provides a collection of email templates for various purposes. These templates are designed to facilitate the creation of visually appealing and responsive emails, simplifying the email marketing process for users. 🤖 AI Prompts 👉 promptport.ai PromptPort lists useful AI prompts to aid in content creation. It offers a variety of prompts to inspire and assist users in generating creative and engaging content across different domains. 📅 Management 👉 notion.so/templates Notion provides templates for effective project and task management. Users can leverage these templates to streamline workflows and enhance collaboration within the Notion platform. 🚀 Marketing 👉 marketingexamples.com It serves as a valuable resource for marketing inspiration. It offers real-world examples and case studies to help marketers learn and apply effective strategies in their campaigns, ✍️ Copywriting 👉 marketingexamples.com/inspiration A dedicated section for copywriting inspiration. It provides insights and examples to guide copywriters in creating compelling and persuasive content for marketing purposes. Did you like the resources? Here's more 👇 Over the previous months, I've compiled The Ultimate Bundle with every resource you need from starting to learn to code to landing your dream tech role! Includes 900+ resources in total, further divided into 99 categories for easier navigation and access! Save 1000s of hours and focus on what matters! I'm currently offering 50%OFF just for my readers! Don't miss out on this! ⭐ ! ⭐ Get it here: Ultimate Resources Bundle to Land a Job in Tech Writing has always been my passion, and it gives me pleasure to help and inspire people. If you have any questions, feel free to reach out! Make sure to receive the best resources, tools, productivity tips, and career growth tips I discover by subscribing to ! my newsletter Also, connect with me on , , and ! Twitter LinkedIn GitHub Also published . here

8 Sizzling Template Sites to 10X Your Productivity 🚀🔥

Heyo, Hacker! is designed by our friends at Āut Labs with themes and ideas for you to enter the Opt Out Writing contest. This writing prompt Click here to write with this template. See the contest announcement . Learn how to enter the contest . here here Theme 1: . Opt out of a System that doesn’t represent you #autonomy: : Explore the critical role of autonomy in decentralized systems like DAOs. Consider focusing on how Āut’s mission and products (i.e.: Nova, ĀutID, ĀutOS, …) enhance this. You can tell us about Roman’s , Greek’s , French or some role-based, [dys/u]topian society that is yet to come. Autonomy in Decentralized Systems, Collectives and DAOs triumvirates poleis communes - : Remember the “ ” in the Berlin of the 90ies? We love that vibe. Consider the intersection of autonomy in art, technology, and activist reforms - highlighting innovative approaches based on autonomy of one or multiple parties. As well as how these parties can play together to take down a censoring, centralized, self-absorbed Moloch. Autonomy in Art, Technology, and Activism hacker labs : Tell us a story on how a “ ” may look like. Are we aiming towards a dystopian, whole-state surveillance, or towards the highest level of individual autonomy and collective productivity that humankind has ever seen? Anything worse? Anything in between? Reshape the future workplace and work culture, especially imagining a world where decentralized organizations actually made it. Autonomy in the Workplace workplace of the future : . Is different for DeFi degens vs. artists & writers vs. political scientists & philosophers vs. governance vs. devs & mathematicians? Feel free to tackle them all at once, tell us a story about one of them - or create a role-based governance model that is going to take the future generations by storm. Role-specific Autonomy 50 shades of Autonomy autonomy : Square and simple. What is , isn't it a paradox in terms, and what does that even mean? Yeah, all that jazz. You can take a mathematical angle, invent new game-theorical rules of the game, or just make up a story that even for a second lets us suspend our disbeliefs. Collective Autonomy Collective Autonomy #identity: : What is identity in the digital space? Is it a mere reflection of what we are offline, or is it an augmented version of ourselves? Is there a “minimum viable tech stack” that can be combined to create verifiable individuals? This is an open prompt - feel free to take it from a technical or philosophical standpoint. And be provocative - we aim for non-trivial answers only on how digital technologies enable new forms of identity, personal expression and verification. Identity in the Digital Space : That’s an obvious one. How identity evolved over the centuries. Did we “mature” as a society? Did technology change what we are as individuals? Are humans different in their [self-awareness; proprioception; way to perceive others] or we did nothing but taking a long stroll from Stone Age to Technocracy? The History of Identity : we talk DAOs, distributed nations, on-chain agencies. But what are individuals within groups? Is collective intelligence a “flattening model” that blurs individuality within collectives, or it turns each individual actor into a needed, recognizable tile of the puzzle? And what is the threshold between individual and collective identity? This is a difficult one - new models, visual graphs, and brand-new, DAO-shaking processes are encouraged. Collective Identity : from Metaverses and NFTs, to basic PGP and SSIDs. How can an ID be as unstoppable, and uncensorable on one side, as it is credible, and reliable on the other? Please, be as geeky as needs be - use your tech-knowledge and understanding as an act of civil disobedience. On-chain Identities : This is our Sci-fi prompt. Tell us stories. Speculate on how identity will evolve in decentralized societies. On how they will impact individuality. For this prompt you can share your tech journal, tell us personal identity narratives, or even invent on-chain personas and breed them to NFT perpetual life. Whatever works. The Evolution of Identity in Decentralized Societies #selfsovereignty: : What is -sovereignty? Why it matters? “ ” is already a long, difficult word per se - so why did we even feel the need to add the prefix “ ” there? This is all about the inalienable individuals’ right to privacy and selective disclosure. Give us self-sovereignty straight, or explore it in a specific context. The Essence of Self-Sovereignty self Sovereignty self- : Provide real-world examples or case studies where self-sovereignty is effectively implemented. Can’t find any? Even better. Make one up, and let’s make it happen together. Self-Sovereignty in Action : This is a big one. As the Anarchist proverb goes, . But what are the borders of this personal freedom? Should self-sovereignty self-enforce in decentralized social/community contracts? Or we should somehow “hardwire” a sort of collective ethos beforehand, into the decentralized smart contracts that will govern us all? Balancing Self-Sovereignty and Collective Responsibility one can only be free if everyone else is free : Think of DeFi credit score, think of UBI. Is a self-sovereign, verifiable ID enough to automate the individual and collective distribution of wealth? Or we still need/want/expect “watchmen” to supervise that all goes smooth - and to potentially deem liable if something goes wrong? Self-Sovereignty in Financial Systems : Should we really be limited by old-world concepts such as “1 person : 1 Identity/vote/seat”? Or meritocracy means that we should be able to enforce a self-sovereign right to multiplicity in the digital space, as long as we can handle our multifaceted selves? To Sybil or not to Sybil Open Prompts: : The old, best writing advise: write about what you know. From literature, to robotics, to the legal system - write about one of the contest topics in relation to a specific field you are deeply knowledgeable or passionate about. [#autonomy; #identity; #selfsovereignty] in [insert field] This is a quote that we like, from J.P. Proudhon. To be governed is to be watched, inspected, spied upon, directed, law-driven, numbered, regulated, enrolled, indoctrinated, preached at, controlled, checked, estimated, valued, censured, commanded, by creatures who have neither the right nor the wisdom nor the virtue to do so. To be governed is to be at every operation, at every transaction noted, registered, counted, taxed, stamped, measured, numbered, assessed, licensed, authorized, admonished, prevented, forbidden, reformed, corrected, punished. It is, under pretext of public utility, and in the name of the general interest, to be placed under contribution, drilled, fleeced, exploited, monopolized, extorted from, squeezed, hoaxed, robbed; then, at the slightest resistance, the first word of complaint, to be repressed, fined, vilified, harassed, hunted down, abused, clubbed, disarmed, bound, choked, imprisoned, judged, condemned, shot, deported, sacrificed, sold, betrayed; and to crown all, mocked, ridiculed, derided, outraged, dishonored. That is government; that is its justice; that is its morality. , - Pierre-Joseph Proudhon The General Idea of the Revolution Explore it in the key that you like, adherent to one of the three main themes. Or just use it as an inspiration, and write about whatever you want :) Click here to write with this template.

Aut Labs Story Template: Opt Out of a System that Doesn’t Represent You

অট ল্যাবস স্টোরি টেমপ্লেট: এমন একটি সিস্টেম থেকে অপ্ট আউট করুন যা আপনাকে প্রতিনিধিত্ব করে না

Aut Labs-Story-Vorlage: Melden Sie sich von einem System ab, das Sie nicht repräsentiert

Plantilla de historia de Aut Labs: optar por no participar en un sistema que no lo representa

Modèle d'histoire Aut Labs : désinscription d'un système qui ne vous représente pas

ऑट लैब्स स्टोरी टेम्प्लेट: उस सिस्टम से ऑप्ट आउट करें जो आपका प्रतिनिधित्व नहीं करता है

Aut Labs ストーリー テンプレート: あなたを代表しないシステムからオプトアウトする

Aut Labs 스토리 템플릿: 귀하를 대표하지 않는 시스템에서 탈퇴

Modelo de história do Aut Labs: desative um sistema que não representa você

Шаблон истории Aut Labs: Откажитесь от системы, которая не представляет вас

Aut Labs Hikaye Şablonu: Sizi Temsil Etmeyen Bir Sistemden Vazgeçin

Mẫu câu chuyện của Aut Labs: Chọn không tham gia hệ thống không đại diện cho bạn

自动实验室故事模板：选择退出不代表您的系统

In Ansible, variables and facts, along with templates, are foundational tools for creating flexible automation workflows. Variables allow you to manage and change your configurations dynamically. Facts are a special subset of variables that Ansible gathers from the remote systems, providing context-specific information. Templates enable the generation of variable-driven configuration files, making your playbooks adaptable to varied environments and scenarios. These tools make playbooks reusable and adaptable, allowing you to avoid hard-coding values and enabling customization for different environments. Variables & Facts Variables allow for parameters to be modified without altering the playbook's core logic. Types of Variables: True or False values. Boolean: An ordered collection of items. List: Key-value pairs for complex data structures. Dictionary: Captures the output of tasks to use later in your playbook. Registered Variables: Auto-collected variables that provide details about the remote systems you are managing. Facts: Avoid conflicts in variable names by using bracket notation. NB: - name: Print the distribution of the target
  hosts: all
  vars:
   curr_time: "{{ now() }}"
  tasks:
   - name: Distro Check
     ansible.builtin.debug:
      msg: "The target system is {{ ansible_facts['distribution'] }}. Timestamp: {{ curr_time }}" Templates & Files Templates in Ansible use the Jinja2 templating language to dynamically create files using variable interpolation, loops, and conditionals. - name: Write distro name
  hosts: all
  tasks:
   - name: Write distro name
     ansible.builtin.template:
      src: distro.j2
      dest: /root/distro.txt
      mode: '644'

# src: location of jinja2 template file
# dest: location it will be copied to
# permissions that will be granted to the file Practice We're going to use the OS Family to determine whether to install NGINX of Lighttpd, and then, we'll deploy a custom homepage to the remote host containing NGINX all without hardcoding hostnames. Clone the repo. git clone https://github.com/perplexedyawdie/ansible-learn.git 2. Change directory to facts-and-templates cd ansible-learn/facts-and-templates 3. Spin up the environment using docker-compose docker compose up -d --build 4. SSH into the Ansible server ssh -o StrictHostKeyChecking=no -o NoHostAuthenticationForLocalhost=yes root@localhost -p 2200
# password: test123 Variables & Facts 5. Create a playbook called . Here, we'll setup NGINX & Lighttpd, and then, output the name of the distro for each remote host. server_setup.yaml - name: Install NGINX on Debian & Lighttpd on RedHat
  hosts: all
  vars:
   dev1: "Debian"
   dev2: "RedHat"
  tasks:
   - name: Install NGINX for Debian-based systems   
     ansible.builtin.apt:
      name: nginx
      state: present
     when: ansible_facts['os_family'] == dev1       

   - name: Install Lighttpd for RedHat-based systems 
     ansible.builtin.yum:
      name: lighttpd
      state: present
     when: ansible_facts['os_family'] == dev2       

   - name: Display the distribution
     ansible.builtin.debug:
      msg: "The server is running {{ ansible_facts['distribution'] }}" 6. Run ansible-lint. ansible-lint server_setup.yaml 7. Run the playbook. ansible-playbook --key-file /root/.ssh/id_rsa_ansible -u root -i inventory.yaml server_setup.yaml 8. Confirm that the setup was successful. ssh -i /root/.ssh/id_rsa_ansible root@server3 nginx -V

ssh -i /root/.ssh/id_rsa_ansible root@server2 lighttpd -v
ssh -i /root/.ssh/id_rsa_ansible root@server1 lighttpd -v Templates & Files 9. Create a Jinja2 template file called index.html.j2 It will get auto-populated with the OS Family & Distribution. <html>
<head>
  <title>Welcome to {{ ansible_facts['os_family'] }}</title>
</head>
<body>
  <h1>Server running on {{ ansible_facts['distribution'] }}</h1>
</body>
</html> 10. Create a playbook called custom_homepage.yaml. We're deploying the custom homepage created above to NGINX then restarting the server. - name: Deploy Custom Homepage and restart
  hosts: all
  vars:
   dev1: "Debian"
   dev2: "RedHat"
  tasks:
   - name: Create Homepage with Jinja2 Template for NGINX
     ansible.builtin.template:
      src: index.html.j2
      dest: /var/www/html/index.html
      mode: '644'
     when: ansible_facts['os_family'] == dev1
     notify: restart nginx

  handlers:
   - name: Restart NGINX
     listen: "restart nginx"
     ansible.builtin.service:
      name: nginx
      state: restarted
     when: ansible_facts['os_family'] == dev1 11. Run the linter. ansible-lint custom_homepage.yaml 12. Run the playbook. ansible-playbook --key-file /root/.ssh/id_rsa_ansible -u root -i inventory.yaml custom_homepage.yaml 13. Confirm deployment by visiting in your browser. http://localhost:2203 Recap Awesome effort! 🙌 We've learned how to use variables & facts in a playbook along with how to create dynamic files using templates. Next, we'll look at modularization and error handling. Til then, take care!

Ansible 101: Working With Facts and Templates

উত্তর 101: ফ্যাক্টস এবং টেমপ্লেট নিয়ে কাজ করা

Ansible 101: Arbeiten mit Fakten und Vorlagen

Ansible 101: trabajar con hechos y plantillas

Ansible 101 : Travailler avec des faits et des modèles

Ansible 101: तथ्यों और टेम्पलेट्स के साथ कार्य करना

Ansible 101: ファクトとテンプレートの操作

Ansible 101: 팩트 및 템플릿 작업

Ansible 101: Trabalhando com fatos e modelos

Ansible 101: работа с фактами и шаблонами

Ansible 101: Gerçekler ve Şablonlarla Çalışmak

Ansible 101: Làm việc với các sự kiện và mẫu

Ansible 101：使用事实和模板

As a writer at HackerNoon, you'll appreciate the value of our writing tool: writing templates. Created to be a reliable companion throughout the highs and lows of your writing journey, these templates are designed to combat writer's block and assist you in constructing articles with an ideal structure. We offer over developed by HackerNoon editors to streamline and enhance your writing process. However, they don't just contribute to efficiency, they also boost the quality of your content. 100 templates Every template includes rich, native Notion-like embeds for Tables, Code Blocks, Page Breaks, Snippets, Headings, and more, ensuring your articles are not only informative but also visually captivating. Accessing HackerNoon’s Templates To access these tools, navigate to your . Here, you’ll discover a search bar and a collection of templates. You can filter your search by popularity, recentness, or input your own terms, and select the template that's best for you. writer dashboard Once you've chosen a template, you can either preview it and use it if it fulfills your needs, or dive in and begin writing immediately. Additionally, you can share the template by clicking the link icon and save it for future projects. You might have noticed that each template is accompanied by a number. This reflects the count of individuals who have found and used each template beneficial. Most Popular Writing Templates in 2023 To aid you in getting started, here are some of our writers’ favorite templates from 2023: Meet The Writer Web Development Web3 General Interview Write a Hackernoon Top Story Writer Versus Blank Page Everyone Should Know About It Describe Your Life Hacks

Dive Into the World of HackerNoon's Free Writing Templates

হ্যাকারনুনের লেখার টেমপ্লেটের জগতে ডুব দিন

Tauchen Sie ein in die Welt der Schreibvorlagen von HackerNoon

Sumérgete en el mundo de las plantillas de escritura de HackerNoon

Plongez dans le monde des modèles d'écriture de HackerNoon

हैकरनून के लेखन टेम्पलेट्स की दुनिया में गोता लगाएँ

HackerNoon のライティング テンプレートの世界に飛び込む

HackerNoon의 글쓰기 템플릿 세계에 빠져보세요

Mergulhe no mundo dos modelos de escrita do HackerNoon

Погрузитесь в мир шаблонов письма HackerNoon

HackerNoon'un Yazma Şablonlarının Dünyasına Dalın

Đi sâu vào thế giới các mẫu viết của HackerNoon

深入 HackerNoon 写作模板的世界

✨ As we welcome 2024, let's take a moment to applaud the incredible stories that fueled our hacker minds in 2023! 🚀 We've compiled a 2023 roundup of the top most-read stories, top active writers, top tech categories, and even the top most popular templates. These insights might be just what you need to start the 2024 right! Pro-tip: There’s a little surprise at the end! Most Read Stories Of The Year⁠ We've compiled the 23 most-read stories from last year: it's time to give a virtual high-five to our phenomenal writers! 📚✨ 1. , by Every Game of the Year Winner in Chronological Order . Jose Hernandez https://hackernoon.com/every-game-of-the-year-winner-in-chronological-order?embedable=true , by Navigating Big Data's Potential and Privacy in Modern Medicine Viktoriia Erokhina https://hackernoon.com/navigating-big-datas-potential-and-privacy-in-modern-medicine?embedable=true , by How to Implement a Merkle Tree in Solidity Daniel Shvetsov https://hackernoon.com/how-to-implement-a-merkle-tree-in-solidity?embedable=true , by Solid Principles in Smart Contract Development Daniel Shvetsov https://hackernoon.com/solid-principles-in-smart-contract-development?embedable=true , by Android Devices in Enterprise Mobility: Navigating Key Risks Alexey Zhurba https://hackernoon.com/android-devices-in-enterprise-mobility-navigating-key-risks?embedable=true , by Profiting in Times of Crises: The Silicon Valley Bank Story Alexey Zhurba https://hackernoon.com/profiting-in-times-of-crises-the-silicon-valley-bank-story?embedable=true , by The World Is Ready for a New Type of Operating System Theo Priestley https://hackernoon.com/the-world-is-ready-for-a-new-type-of-operating-system?embedable=true , by How to Centre an Element in CSS with Tailwind Jonathon Simpson https://hackernoon.com/how-to-centre-an-element-in-css-with-tailwind?embedable=true by Smart Contract Optimization: How to Use Less Gas in Ethereum Daniel Shvetsov https://hackernoon.com/smart-contract-optimization-how-to-use-less-gas-in-ethereum?embedable=true , by The Potential Impact of the Metaverse on Education Lomit Patel https://hackernoon.com/the-potential-impact-of-the-metaverse-on-education?embedable=true by The 7 Software Architecture Books Experienced Developers Need to Read Javin Paul https://hackernoon.com/the-7-software-architecture-books-experienced-developers-need-to-read?embedable=true by 13 Best Datasets for Power BI Practice Datasets https://hackernoon.com/13-best-datasets-for-power-bi-practice?embedable=true , by Coding: The Universal Language You Must Learn Lomit Patel https://hackernoon.com/coding-the-universal-language-you-must-learn?embedable=true , by Portfolio Optimization with Python and Quantum Computing Techniques Dmitrii Abramov , by Validate Binary Search Tree: Blind 75 LeetCode Question Ruslan Rakhmedo by 15 Excel Datasets for Data Analytics Beginners Datasets , by Introducing Drag-Your-GAN: Drag Objects to Create New Images Louis-François Bouchard , by How to Design a Messaging Service in Your 45-Minute System Design Interview Leonid Zemenkov by How to Fix Android Not Receiving Verification Texts Error Manmohan Singh , by I Conducted Experiments with the Alpacallama-7B Language Model: Here Are the Results Zheng "Bruce" Li , by Unveiling the Power of PM and P3M Algorithms on GPUs Alexey Ozeritskiy by How to Create a Solar System in JavaScript with Three.js Daniel Shvetsov , by Facilitating Team Development in a High-Pressure Environment Anton Rysin Use to share writing tips with the HackerNoon community! this template Most Active Writers Of The Year And now, let's cheer for the movers and shakers of 2023 – some of our most active writers, the ones who never let their keyboards gather dust and kept us hooked with the hottest info on the web. Let’s give it up to: Ishan Pandey Ulrik Lykke Andrey Didovskiy ZeroRequiem Mike Young Shai Almog Obyte Nicolas Fränkel Marcin Wosinek Frank Z Most Popular Tech Categories in 2023 Some Tech Categories really got you going - let’s take a look at the top ten of 2023: : This category resounds popular, accounting for 37% of all reads! Programming [Write a programming story with .] this template : The second runner-up drops to 16% of all reads on HackerNoon - a significant decrease but still huge in readers’ interest. Machine-learning [Tell us what they don’t say about AI/ML with ] this template : The third place earned 13% of the whole audience readership! Web3 [Discuss Web3’s future with ] this template : Just a little bit behind, Tech Stories accounts for 12% of all reads. Tech Stories [Tell us the last thing you learned with ] this template : Now, for the second noteworthy drop: Gaming accounts for almost 5% of all reads; though significantly lower, it still encompasses 565,728 reads! Gaming [Review a game with ] this template : This category accounts for 3,82% of all reads. Cloud [Write a Cloud story with ] this template : A short distance behind, we have the Cybersecurity category, representing 3,70% of all reads. Cybersecurity [Tell us how you got into Cybersecurity story with ] this template : With 3,55%, Data Science holds the 8th place on this list. Data Science [Write about Data with ] this template : This category holds 3,26% of all readership! Futurism [Discuss the Future of Tech with ] this template : Last but not least, the business category contains 3,09% of all readership, which breaks down to 377,215 reads. Business [Tell us about your Business with ] this template Most Popular Writing Templates in 2023 HackerNoon writing templates are at your disposal at all times, but you clearly had some favorites: Meet The Writer Web Development Web3 General Interview Write a Hackernoon Top Story Writer Versus Blank Page Everyone Should Know About It Describe Your Life Hacks Thank you all for the words you shared with HackerNoon 💚 We couldn’t have done it without you! If you didn’t see your name up on this list, don’t get discouraged - you’re on our personal favorites list for sure 🤗 And you add “reach a wider audience” or “become a more productive writer” to your 2024 resolutions. You have what it takes to smash your goals and we’ll keep feeding you the tips you need to get there, right here, in your inbox 📧 Surprise Time! HackerNoon is partnering with the 2024 editions of , , and , and we have three (3) tickets to offer! CXO 2.0 Conference Marketing 2.0 Conference Internet 2.0 Conference The 2.0 Conferences explore the future of , tools and insights to excel in today's landscape, and draw innovative minds from around the world. They’ll be taking place from February 20th to 22nd in Dubai and from March 18th to 20th in Las Vegas. #leadership #marketing Find out more about the event here. Curious? Email to express your interest - the lucky winners will be revealed in the next writers’ note. monica@hackernoon.com Happy 2024!

Unveiling the Best of 2023: Top Stories, Writers, Tech Categories, and Templates! 📚

How to Build and Deploy a Real-time Traffic Monitoring App Using Quix's Computer Vision Template

কুইক্সের কম্পিউটার ভিশন টেমপ্লেট ব্যবহার করে কীভাবে একটি রিয়েল-টাইম ট্র্যাফিক মনিটরিং অ্যাপ তৈরি এবং স্থাপন করবেন

So erstellen und implementieren Sie eine Echtzeit-Verkehrsüberwachungs-App mithilfe der Computer Vision-Vorlage von Quix

Cómo crear e implementar una aplicación de monitoreo de tráfico en tiempo real utilizando la plantilla de visión por computadora de Quix

Comment créer et déployer une application de surveillance du trafic en temps réel à l'aide du modèle de vision par ordinateur de Quix

क्विक्स के कंप्यूटर विज़न टेम्पलेट का उपयोग करके रीयल-टाइम ट्रैफ़िक मॉनिटरिंग ऐप कैसे बनाएं और तैनात करें

Quix の Computer Vision テンプレートを使用してリアルタイム トラフィック監視アプリを構築および展開する方法

Quix의 컴퓨터 비전 템플릿을 사용하여 실시간 교통 모니터링 앱을 구축하고 배포하는 방법

Como construir e implantar um aplicativo de monitoramento de tráfego em tempo real usando o modelo de visão computacional do Quix

Как создать и развернуть приложение для мониторинга трафика в реальном времени с использованием шаблона компьютерного зрения Quix

Quix'in Görüntü İşleme Şablonunu Kullanarak Gerçek Zamanlı Trafik İzleme Uygulaması Nasıl Oluşturulur ve Dağıtılır

Cách xây dựng và triển khai ứng dụng giám sát lưu lượng truy cập thời gian thực bằng mẫu thị giác máy tính của Quix

如何使用 Quix 的计算机视觉模板构建和部署实时流量监控应用程序

React Native has gained immense popularity for building cross-platform mobile applications. While React Native offers a fantastic starting point with its default template, sometimes you may want to create a custom template to streamline your development process or enforce standards across multiple projects. In this article, we'll walk you through the steps to create your own React Native template. coding Why Create Custom Templates? There are several reasons to create custom templates for your : React Native projects : You can include reusable components, libraries, and styles in your templates. This promotes code reuse across different projects, saving development effort and reducing the chance of bugs. Code Reusability : You can enforce best practices and architectural patterns by including them in your custom template. Best Practices : With a template, you don't have to start from scratch. You can leverage the boilerplate code, configurations, and UI components to accelerate development. Faster Development : Templates simplify the onboarding process for new team members. They can quickly understand the project structure and development practices, leading to faster productivity. Onboarding : By using templates with predefined configurations and dependencies, you reduce the likelihood of configuration errors and compatibility issues. Reduced Errors Prerequisites Before creating a custom , make sure you have the following prerequisites in place: React Native template : Ensure you have Node.js installed on your machine. You can download it from . Node.js nodejs.org : Install the React Native CLI globally using the following command: React Native CLI npm install -g react-native-cli Steps to Create a Custom Template Step 1: Initialize a New Template Project First, create a new directory for your project: custom template mkdir custom-rn-template
cd custom-rn-template
npm init Your file should look like this: package.json {
  "name": "MyCustomTemplate",
  "version": "1.0.0",
  "description": "React Native Custom Template",
  "files": [
    "template",
    "template.config.js"
  ]
  ...
} Create file: template.config.js module.exports = {
  placeholderName: 'MyCustomTemplate',
  templateDir: './template',
} Next, use the to initialize a new project: React Native CLI npx react-native init MyCustomTemplate After that, rename the "MyCustomTemplate" folder to "template.” Step 2: Customize Your Template Now that you have a base project, you can customize it to fit your needs. You can make various modifications, including: : Organize your project structure the way you prefer. Project Structure : Add or remove dependencies by modifying the file. Dependencies package.json : Include common components, utilities, or screens that you frequently use in your projects. Boilerplate Code : Set up linting, testing, and other configurations that align with your development practices. Configuration Step 3: Document Your Template To make your custom template user-friendly, create documentation that explains how to use it. You can include: : Explain how to create a new React Native project using your template. Installation : Provide guidance on how to customize the template further. Customization : Describe any additional steps or configurations required for specific features or libraries included in the template. Usage Step 4: Publish Your Template Once you've customized and documented your template, it's time to publish it. You can publish your template as an npm package, making it accessible to your team and the community. Create an account on if you don't have one already. npmjs.com Navigate to your template project directory and login to npm: npm login Publish your template to npm: npm publish --access public Step 5: Use Your Custom Template To create a new React Native project using your custom template, run the following command: npx react-native init MyCustomApp --template MyCustomTemplate Replace "MyCustomApp" with the name of your new project. React Native will generate a new project based on your custom template. Conclusion Creating custom React Native templates can significantly improve your development workflow by enforcing best practices, maintaining consistency, and saving time on project setup. Also, check my own , which includes what I use when creating new projects. react-native-modular-template

Creating Custom React Native Templates: A Step-by-Step Guide

Introduction In the fast-paced realm of web development, crafting engaging and interactive user interfaces is a top priority. Angular, a widely used JavaScript framework developed by Google, offers a robust solution for building contemporary web applications with dynamic user experiences. Central to this is the management of forms. equips developers with a powerful set of tools and strategies for handling forms effectively, enabling the creation of seamless and compelling user interactions. In this comprehensive guide, we'll delve deep into the realm of Angular forms, exploring their diverse types, features, and best practices. Angular Table of Contents Understanding Angular Forms 1.1 Types of Forms in Angular Template-Driven Forms Reactive Forms Mastering Template-Driven Forms 2.1 Creating Form Elements 2.2 Two-Way Data Binding 2.3 Form Validation Harnessing the Power of Reactive Forms 3.1 Setting Up Reactive Forms 3.2 Form Controls and Groups 3.3 Reactive Form Validation 3.4 Dynamic Form Fields Elevating User Experience 4.1 Handling Form Submission 4.2 Providing User Feedback FAQs About Angular Forms 5.1 Template-Driven vs. Reactive Forms 5.2 Custom Validation in Angular Forms 5.3 Building Dynamic Forms 5.4 Handling Form Submission and Server Interaction Conclusion 1. Understanding Angular Forms 1.1 Types of Forms in Angular Angular offers two primary types of forms to manage user input: Template-Driven Forms Template-driven forms are ideal for simpler forms where you want . They are declarative and rely on directives embedded within the HTML template to handle form data binding and validation. Angular to handle much of the heavy lifting Reactive Forms Reactive Forms provide more control and flexibility. They are programmatically driven and suitable for complex forms with dynamic validation requirements. With Reactive Forms, you define the form structure and behavior in the component class. 2. Mastering Template-Driven Forms 2.1 Creating Form Elements Let's create a simple login form as an example: <form #loginForm="ngForm" (ngSubmit)="onSubmit(loginForm)">
  <input type="text" name="username" ngModel required>
  <input type="password" name="password" ngModel required>
  <button type="submit">Log In</button>
</form> 2.2 Two-Way Data Binding With template-driven forms, two-way data binding simplifies form-control interactions. For instance, in the above form, the directive binds the input values to properties in the component. ngModel 2.3 Form Validation Adding validation is straightforward: <input type="email" name="email" ngModel required email>
<div *ngIf="loginForm.controls.email.invalid && (loginForm.controls.email.dirty || loginForm.controls.email.touched)">
  <div *ngIf="loginForm.controls.email.errors.required">Email is required</div>
  <div *ngIf="loginForm.controls.email.errors.email">Invalid email format</div>
</div> 3. Harnessing the Power of Reactive Forms 3.1 Setting Up Reactive Forms In your module: import { ReactiveFormsModule } from '@angular/forms';

@NgModule({
  imports: [ReactiveFormsModule],
}) 3.2 Form Controls and Groups Creating a reactive form: import { FormGroup, FormBuilder, Validators } from '@angular/forms';

@Component({
  // ...
})
export class MyComponent implements OnInit {
  loginForm: FormGroup;

  constructor(private fb: FormBuilder) {}

  ngOnInit() {
    this.loginForm = this.fb.group({
      username: ['', Validators.required],
      password: ['', Validators.required],
    });
  }
} 3.3 Reactive Form Validation Adding validators: this.loginForm = this.fb.group({
  email: ['', [Validators.required, Validators.email]],
  password: ['', [Validators.required, Validators.minLength(8)]],
}); 3.4 Dynamic Form Fields Adding fields dynamically: addNewField() {
  this.loginForm.addControl('newField', this.fb.control(''));
} 4. Elevating User Experience 4.1 Handling Form Submission <form [formGroup]="loginForm" (ngSubmit)="onSubmit()">
  
  <button type="submit" [disabled]="loginForm.invalid">Log In</button>
</form> 4.2 Providing User Feedback <input type="text" formControlName="username">
<div *ngIf="loginForm.controls.username.invalid && loginForm.controls.username.touched">
  <div *ngIf="loginForm.controls.username.errors.required">Username is required</div>
</div> 5. FAQs About Angular Forms 5.1 Template-Driven vs. Reactive Forms What's the difference between template-driven and reactive forms? Q: Template-driven forms rely on directives within the HTML template and are great for simpler forms. Reactive forms offer more control and are suitable for complex forms with dynamic requirements. A: 5.2 Custom Validation in Angular Forms How can I perform custom validation? Q: You can create custom validation functions and add them to the control's validator array. A: 5.3 Building Dynamic Forms Can I build dynamic forms with a variable number of fields? Q: Yes, reactive forms are excellent for dynamic forms. You can add or remove fields based on user actions. A: 5.4 Handling Form Submission and Server Interaction How do I handle form submission and send data to the server? Q: Use the event to trigger a method. Validate the data and use to send it to the server. A: (ngSubmit) Angular's HTTP client Conclusion Angular forms are the backbone of user interaction in modern web development. By comprehending the distinctions between template-driven and reactive forms and utilizing their unique capabilities, you can build captivating user experiences that elevate your applications. Embrace the world of Angular forms and unlock the potential to create web applications that engage, delight, and stand out in the digital landscape. Also published . here

Angular Forms: Building Engaging User Interfaces with Template-Driven and Reactive Forms

Start Template Now Whats going on here? Explain the news in 1-3 sentences. Be direct. What does this mean? Your opinion in 1-3 paragraphs. Be logical and back up your takes. Why should I care? Answer why this news could matter more in the years ahead. [Paste and Embed Link to Story] Start Template Now Example: Start Template Now

The Ben Tossell Tech News Template: What's going on here? What does this mean? Why should I care?

Why documentation is also important for software developer’s career growth The resistance to documentation among developers is well known and needs no emphasis. Software developers all desire good documentation, and we are well aware of how challenging it can be. However, have you ever considered the vital role that good documentation plays in one’s career growth? Over the past decade, I have had the opportunity to work at lean startups, large tech companies, and even in different countries with their unique work cultures. Throughout my journey, I have consistently practiced collecting various types of notes. These habits have proven to be immensely beneficial for acing job interviews, securing promotions, expanding my professional network, and sharpening my technical skills. I have crafted these practices into a streamlined workflow in . My hope is that it can also aid in your career growth. In this post, I will guide you through the motivation and intention behind this template. this Notion template The benefit of using this Notion template : Previously collecting success stories for promotions or resumes often left me with days of frustration due to insufficient data points. This template basically prompts you to keep track of all your achievements, by the time you need it, it’s almost effortless to convert them into the success stories you need. Keep track of your achievements : The idea behind it is that taking relevant notes as you go about your daily tasks can help the future you. You may remember the excitement when you finally find a solution to fix a tricky bug, however a few months later, you may not even remember what was the problem you’ve solved at that time. This template essentially guides you to write your own developer journals regularly. Write developer journals : This notion template also includes a task management section, you can link specific tasks from this section when building up your knowledge base. Essentially this notion template dashboard provides everything you need to work as a software developer. Having said that, if you already have a customized workflow to manage tasks, you could skip the task management section. Task management and knowledge management in one place : Your network connections, including managers, mentors, mentees, and peers, hold immense learning potential. I recommend maximize this opportunity by scheduling regular coffee chats with them and capture valuable thought-provoking exchanges in your notes. Harness the power of your network : Have you ever jotted down a useful snippet, command, or config somewhere on your laptop, only to struggle to find it when you need it again? Say goodbye to the chaos of scattered notes and enjoy the convenience of having everything you need stored in one centralized place. Farewell to cluttered notes Based on my own experience, the habit of keep these notes and the ability to manage everything in has helped me tremendously to: one Notion dashboard - update my resume effortlessly - prepare for behaviour interview round with plenty of stories - collect datapoints for promotions - build up my own knowledge base - capture valuable lessons from my professional network - be productive since I have everything needed in one place I hope will help you to grow your career as well! this notion template . I’ve compiled and curated a list of job hunting resources for software developers, it covers resources for writing resumes, applying and managing job applications, efficient ways to prepare for coding interviews, resources to learn system design, you can download the free PDF here Also published here .

Unleashing Your Software Developer Potential: Mastering Growth with a Notion Template

When using ChatGPT, very often, you have to repeat the same prompts or parts of the same prompts. It gets very annoying to type the same thing over and over, especially if ChatGPT forgets the purpose of the chat, then you have to repeat the same request in the context of this or that dialogue. Initially, I copied standard prompts into a text notepad. These were, for example, such prompts: Summarize the following text in English: If the following text is in English, translate it into Italian, and if in Italian, then into English: Create a poem based on the following text: My name is Ilya, think of what to answer me in this dialogue: But opening a text document every time and copying and pasting the required prompt is also not convenient. Not to mention the fact that I am very lazy and do not like to repeat the same actions. And then I had an idea to make a plugin for Google Chrome, with which you can add buttons directly to the ChatGPT interface, by pressing which the required prompt will be inserted into the text input field. The plugin is not complicated, and I will share its code here with you. First, create a directory somewhere where our plugin will be. I will name it /gptinsert In the directory, you can immediately create an icon of 48x48 pixels, naming it icon.png After that, we create a file with the following content: manifest.json {
    "manifest_version": 3,
    "name": "ChatGPT textarea buttons",
    "version": "1.0",
    "permissions": ["activeTab"],
    "content_scripts": [
      {
        "matches": ["https://chat.openai.com/*"],
        "js": ["content.js"]
      }
    ],
    "icons": {
      "48": "icon.png"
    }
  } After that, we create a file that will perform the work of our module; we name it and add the following code to it in JavaScript: content.js, const insertText = (text) => {
    // Check if the page has a textarea.
    const textarea = document.querySelector('textarea');
    if (textarea) {
      const startPosition = textarea.selectionStart; // The position of the cursor at the beginning of the selected text.
      const endPosition = textarea.selectionEnd; // The position of the cursor at the end of the selected text.
      const originalText = textarea.value; // The original text in the textarea.
      const newText = originalText.slice(0, startPosition) + text + originalText.slice(endPosition); // The new text in the textarea.
      
      textarea.value = newText; // Insert the new text into the textarea.
      textarea.focus(); // Focus on the textarea.
      textarea.selectionEnd = startPosition + text.length; // Set the cursor position at the end of the inserted text.
      textarea.selectionStart = startPosition + text.length; // Set the cursor position at the beginning of the inserted text.
    }
  };
  
  // Create a button.
  const addButton = (title,text) => {
    const button = document.createElement('button'); // Create a button.
    button.textContent = `${title}`; // Set the button text.
    button.addEventListener('click', (event) => {
        event.preventDefault();
        insertText(text); // Insert text into the textarea.
      });
    return button;
  };
  
  // Add buttons to the page.
  const init = () => {
    // Check if the page has a textarea.
    const textarea = document.querySelector('textarea').parentElement;
    if (textarea && !document.querySelector('.textarea-buttons')) {
      // Create a container for the buttons.
      const container = document.createElement('div');
      container.className = 'textarea-buttons';
      container.style.display = 'flex';
      container.style.gap = '5px';
      container.style.marginTop = '5px';
      // Add buttons to the container.
      container.appendChild(addButton('Summarize','Summarize the following text in English: '));
      container.appendChild(addButton('Translate','If the following text is in English, translate it into Italian, and if in Italian, then into English: '));
      container.appendChild(addButton('Poem','Create a poem based on the following text: '));
      container.appendChild(addButton('Response','My name is Ilya, write that I can answer my interlocutor in this dialogue: '));
      // Add the container below the textarea.
      textarea.parentNode.insertBefore(container, textarea.nextSibling);
    }
  };
  
  init();
  
  // If the page uses dynamic elements, periodically check and add buttons if necessary.
  setInterval(init, 1000); Now we need to add this plugin to Google Chrome. For this, we go to Unpacked, then open the directory with our plugin and click the button. Menu->Settings->Extensions->Load /gptinsert, "Select Folder" After this, the logo of our plugin will appear next to the address bar in the browser. Now, we can use it. To do this, simply open , and create a new chat, after which 4 buttons will appear at the bottom of our chat: Summarize, Translate, Poem, and Response. https://chat.openai.com/ By pressing, for example, on Summarize, the prompt "Summarize the following text in English:" will appear in the input field. After this, you can insert any text in any supported language, and ChatGPT will output its brief content and meaning. Let's check the work of the "Response" button for example: If you need to add a new button, you just need to add the following code to the file: content.js container.appendChild(addButton('My button','My prompt text: ')); After saving - you just need to restart the browser, and everything will work. In this way, you can add an unlimited number of buttons and prompts. With frequent use, this noticeably speeds up work and adds convenience ;) GitHub link: https://github.com/sinenko/ChatGptPromptInsert

Create ChatGPT Prompt Templates by Using This Google Chrome Plugin

এই Google Chrome প্লাগইন ব্যবহার করে ChatGPT প্রম্পট টেমপ্লেট তৈরি করুন

Erstellen Sie ChatGPT-Eingabeaufforderungsvorlagen mit diesem Google Chrome-Plugin

Cree plantillas de solicitud de ChatGPT mediante el uso de este complemento de Google Chrome

Créer des modèles d'invite ChatGPT en utilisant ce plugin Google Chrome

इस Google क्रोम प्लगइन का उपयोग करके चैटजीपीटी प्रॉम्प्ट टेम्पलेट बनाएं

この Google Chrome プラグインを使用して ChatGPT プロンプト テンプレートを作成する

이 Google Chrome 플러그인을 사용하여 ChatGPT 프롬프트 템플릿 만들기

Crie modelos de prompt do ChatGPT usando este plug-in do Google Chrome

Bu Google Chrome Eklentisini Kullanarak ChatGPT İstemi Şablonları Oluşturun

Tạo mẫu lời nhắc ChatGPT bằng cách sử dụng Plugin Google Chrome này

使用此 Google Chrome 插件创建 ChatGPT 提示模板

Stories, News & Mentions about PETPLATE

Petplate’s Stories on HackerNoon