9+ Obsidian Dataview: Hide Empty Query Results

Conditional show of dynamic content material inside notes, generated from the be aware’s metadata and content material utilizing a question language, will be achieved by way of intelligent use of inline JavaScript inside Dataview queries. This permits the question outcomes to be evaluated, and if no outcomes match the supplied standards, all the output, together with any surrounding markup, will be suppressed. As an example, a DataviewJS question can examine for the presence of particular key phrases or tags inside a be aware, and render content material solely when these circumstances are met. A sensible instance entails displaying a particular part of a mission overview be aware provided that the mission is marked as “energetic.”

This dynamic management over content material visibility affords important benefits for be aware group and information administration. It permits for the creation of versatile and adaptable templates that regulate their output primarily based on the info inside every be aware. This minimizes litter and presents solely essentially the most related info, streamlining workflows and enhancing the usability of interconnected notes. Traditionally, reaching such dynamic habits required extra advanced workarounds or third-party plugins, however with the mixing of JavaScript into Dataview, this performance turns into extra readily accessible.

The next sections will delve into particular strategies for implementing this conditional show, protecting each easy and sophisticated eventualities with illustrative examples. It will embrace explanations of tips on how to combine JavaScript inside Dataview queries, totally different approaches for conditional logic, and sensible ideas for optimizing question efficiency and sustaining readability.

1. Conditional Logic

Conditional logic varieties the core of controlling Dataview question visibility. By leveraging JavaScript’s `if/else` statements inside DataviewJS queries, one can decide whether or not the outcomes of a question needs to be rendered. This permits for exact management over the show of dynamic content material. For instance, if a question searches for notes tagged with “mission/energetic” and no such notes exist, the conditional logic can forestall the show of the related mission abstract part, maintaining the be aware uncluttered.

The absence of conditional logic would necessitate displaying all potential output whatever the question outcomes. This might result in irrelevant info cluttering notes, particularly when coping with quite a few dynamic sections primarily based on various standards. Think about a dashboard view aggregating duties from totally different initiatives. With out conditional logic, empty mission sections would nonetheless seem, even when these initiatives at present don’t have any duties. Conditional logic prevents this by making certain solely sections with precise knowledge are rendered. One other sensible utility lies in displaying assembly notes solely when a “assembly/accomplished” tag exists on a each day be aware, maintaining the each day be aware centered on present duties till the assembly concludes.

Efficient utilization of conditional logic inside DataviewJS queries is essential for dynamic content material administration inside Obsidian. This method allows responsive templates that adapt to altering knowledge, minimizing litter and enhancing total be aware group. The power to suppress empty question outcomes considerably contributes to a extra streamlined and centered workflow by making certain solely related info is introduced primarily based on the present knowledge state.

2. JavaScript Integration

JavaScript integration inside Dataview supplies the core mechanism for reaching conditional rendering of question outcomes. With out JavaScript, Dataview queries operate primarily as templated shows of present knowledge, missing the flexibility to react dynamically to the presence or absence of outcomes. JavaScript empowers customers to introduce logic that governs the show of data primarily based on the end result of queries, enabling subtle management over content material visibility.

• Conditional Rendering:

  JavaScript’s `if/else` statements, when embedded inside DataviewJS code blocks, enable for the conditional execution of code primarily based on question outcomes. This allows dynamic rendering the place content material related to a question is displayed provided that the question returns knowledge. That is the basic precept behind making a Dataview question “disappear” when no outcomes are discovered. A sensible instance entails a activity checklist question that solely renders if duties tagged with a particular mission exist.

• Information Manipulation and Transformation:

  Past merely checking for the presence of outcomes, JavaScript permits for knowledge manipulation and transformation previous to rendering. This may contain filtering, sorting, or aggregating knowledge returned by the question. As an example, one might filter an inventory of information to show solely these modified throughout the final week, after which conditionally render the checklist provided that information meet that standards. This additional refines the management over what info is displayed, dynamically adjusting the output primarily based on extra advanced knowledge standards.

• Customized Operate Creation:

  JavaScript permits for the creation of customized capabilities inside DataviewJS queries. These capabilities can encapsulate advanced logic for figuring out content material visibility, enabling larger code reusability and maintainability. A operate could possibly be outlined to examine for particular circumstances throughout a number of metadata fields and return a boolean worth figuring out whether or not a piece needs to be rendered. This promotes a extra modular and arranged method to managing conditional rendering logic.

• Interplay with the Obsidian API:

  Whereas circuitously associated to creating Dataview content material disappear, JavaScript integration inside Dataview permits for interplay with the Obsidian API. This unlocks potential for extra superior dynamic behaviors, resembling programmatically opening notes or manipulating the Obsidian interface primarily based on question outcomes. Whereas this extends past the core scope of conditional rendering, it highlights the broader energy and adaptability provided by JavaScript throughout the Dataview context.

These aspects of JavaScript integration collectively empower customers to create extremely dynamic and responsive be aware templates. By leveraging JavaScript’s logical capabilities and its interplay with Dataview and the Obsidian API, content material will be exactly managed, making certain solely related info is introduced primarily based on the underlying knowledge. This granular management over content material visibility is important for sustaining organized and environment friendly information administration workflows inside Obsidian.

3. DataviewJS Queries

DataviewJS queries present the important mechanism for implementing conditional rendering, thus controlling the visibility of dynamic content material inside Obsidian notes. Not like normal Dataview queries, which primarily concentrate on knowledge retrieval and templating, DataviewJS queries incorporate JavaScript, enabling logical operations and conditional execution of code. This permits outcomes to be evaluated earlier than rendering, offering the flexibility to suppress output fully if particular standards should not met. This addresses the core goal of creating content material disappear when no related knowledge exists. A sensible instance entails a question displaying an inventory of mission duties. A DataviewJS question can examine if any duties exist for a given mission and conditionally render the checklist, making certain empty mission sections don’t litter the be aware.

The mixing of JavaScript inside DataviewJS queries permits for classy management over the displayed content material. Circumstances can vary from easy checks for the presence of information to advanced evaluations involving a number of metadata fields or exterior knowledge sources. Think about a situation the place a be aware shows details about upcoming deadlines. A DataviewJS question might filter duties by due date, after which conditionally render the “Upcoming Deadlines” part provided that duties are due throughout the subsequent week. This dynamic habits ensures the be aware stays related and avoids displaying empty sections when no instant deadlines exist. One other instance entails dynamically producing tables of contents primarily based on the headings inside a be aware. The question can examine for the presence of headings earlier than rendering the desk of contents, making certain its visibility solely when the be aware construction necessitates it.

Leveraging DataviewJS queries for conditional rendering considerably contributes to environment friendly info administration inside Obsidian. By controlling the visibility of dynamic content material primarily based on knowledge availability, notes stay uncluttered and centered on related info. This method fosters a extra streamlined workflow, decreasing cognitive overhead and enhancing the general consumer expertise. The power to dynamically regulate content material visibility contributes to a extra adaptable and responsive information administration system, accommodating evolving info landscapes and user-specific wants.

4. Empty Consequence Dealing with

Empty end result dealing with is essential for reaching clear and environment friendly conditional rendering inside Dataview. When a Dataview question yields no outcomes, the default habits is commonly to show an empty placeholder or, in some instances, an error message. This may result in cluttered notes full of irrelevant or distracting parts, counteracting the objective of dynamic content material show. Efficient empty end result dealing with supplies the mechanism to utterly suppress the output of a question, together with any surrounding markup, when no knowledge matches the required standards. This instantly addresses the problem of creating Dataview content material disappear when no outcomes are discovered.

Think about a dashboard displaying mission statuses. With out correct empty end result dealing with, initiatives with out updates may nonetheless occupy area, displaying empty sections or placeholders. This clutters the dashboard and diminishes its effectiveness. By implementing empty end result dealing with throughout the DataviewJS question, the mission sections disappear fully when no related knowledge exists, leading to a clear and centered view of energetic initiatives. Equally, think about a each day be aware template that shows assembly notes. If no assembly occurred on a specific day, an empty “Assembly Notes” part would seem. Empty end result dealing with ensures this part solely renders when assembly notes exist, sustaining a streamlined each day be aware construction. In additional advanced eventualities, resembling dynamically generated bibliographies, empty end result dealing with prevents the show of empty quotation lists when no sources are related to a specific doc, sustaining a sophisticated {and professional} look.

Efficient empty end result dealing with is inextricably linked to the flexibility to create really dynamic and contextually related notes. By suppressing irrelevant content material, focus is maintained on the knowledge that issues, resulting in improved readability and a extra environment friendly workflow. Challenges might come up in advanced queries the place figuring out empty outcomes requires nuanced logic, however the advantages of a clear and responsive be aware construction outweigh the implementation effort. Mastering empty end result dealing with is important for leveraging the total potential of Dataview and optimizing information administration inside Obsidian.

5. Dynamic Content material

Dynamic content material lies on the coronary heart of reaching conditional visibility inside Dataview. The power to generate content material that adapts to altering knowledge and user-specified standards is key to creating responsive and uncluttered notes. Controlling the show of this dynamic content material, particularly making it disappear when no related knowledge exists, is the important thing focus of optimizing Dataview for environment friendly information administration. This entails a deeper understanding of how dynamic content material is generated and the way its visibility will be managed primarily based on question outcomes.

• Context-Conscious Info:

  Dynamic content material adapts to the particular context of a be aware. Somewhat than statically displaying all potential info, dynamic content material is generated primarily based on the present knowledge throughout the be aware and associated information. This context-awareness is essential for displaying solely related info. For instance, a mission overview be aware may dynamically show duties, deadlines, and related information primarily based on the mission’s present standing. If no duties are assigned, the duty checklist disappears, making certain the be aware stays centered on the related info. This adaptability is essential for sustaining clear and environment friendly be aware constructions.

• Question-Pushed Technology:

  Dataview queries drive the era of dynamic content material. These queries, usually primarily based on metadata or content material inside notes, retrieve and filter info, forming the idea for dynamic shows. The question outcomes dictate what content material is generated and in the end displayed. As an example, a question filtering duties by due date can populate a dynamic activity checklist, making certain solely upcoming duties are seen. This question-driven method is important for creating versatile and adaptable be aware templates that reply to evolving knowledge.

• Conditional Visibility Management:

  Conditional logic, primarily applied by way of JavaScript inside DataviewJS queries, governs the visibility of dynamic content material. This logic evaluates question outcomes and determines whether or not or not the related content material needs to be rendered. The power to make content material disappear when no outcomes are discovered depends fully on this conditional management. A basic instance entails a gathering notes part that solely seems if a gathering occurred on a given day, stopping empty sections from cluttering each day notes.

• Template-Based mostly Rendering:

  Templates present the construction for displaying dynamic content material. They outline how the info retrieved by queries is formatted and introduced throughout the be aware. This separation of content material and presentation permits for constant formatting whereas sustaining dynamic adaptability. As an example, a template may outline the structure of a activity checklist, whereas the precise duties displayed are dynamically populated primarily based on question outcomes. This structured method ensures consistency and maintainability whereas permitting for versatile content material updates.

These aspects of dynamic content material display its integral position in reaching conditional visibility inside Dataview. By combining query-driven era with conditional visibility management and template-based rendering, customers achieve fine-grained management over what info is displayed, making certain notes stay centered and related. This dynamic method is essential for creating adaptable be aware methods that successfully help evolving information administration wants inside Obsidian.

6. Metadata Filtering

Metadata filtering performs a vital position in controlling the visibility of dynamic content material generated by Dataview queries. The power to selectively question knowledge primarily based on metadata permits for exact management over which info is retrieved and subsequently displayed. This selective retrieval varieties the muse for conditional rendering, enabling dynamic content material to look solely when related metadata is current. With out metadata filtering, conditional rendering would lack the mandatory granularity to find out what content material needs to be displayed primarily based on the particular context of a be aware.

• Focused Information Retrieval:

  Metadata filtering allows focused knowledge retrieval by specifying standards that have to be met for knowledge to be included in question outcomes. This permits for the creation of extremely particular queries that extract solely the specified info from a set of notes. For instance, filtering for notes tagged with “mission/energetic” ensures solely energetic mission notes are thought-about for dynamic content material era. This focused retrieval is essential for making certain the displayed content material precisely displays the present context and avoids cluttering notes with irrelevant info.

• Conditional Rendering Basis:

  Metadata filtering supplies the muse for conditional rendering by figuring out whether or not or not knowledge exists that matches particular standards. If no knowledge meets the filter standards, the related dynamic content material will be suppressed. This direct hyperlink between filtering and rendering is important for making content material disappear when no related info exists. Think about a activity checklist filtered by mission tag. If no duties exist for a specific mission, metadata filtering ensures the question returns no outcomes, triggering the conditional logic to suppress the duty checklist show.

• Dynamic Content material Management:

  Metadata filtering allows fine-grained management over dynamic content material visibility. By combining a number of metadata filters, advanced circumstances will be outlined to exactly management when content material seems. For instance, filtering for duties tagged with “precedence/excessive” and due throughout the subsequent week permits for a dynamic show of pressing duties. This degree of management ensures customers see solely essentially the most vital info, streamlining workflows and decreasing cognitive overload.

• Contextual Relevance:

  Metadata filtering enhances the contextual relevance of dynamic content material by tailoring the displayed info to the particular circumstances inside a be aware. This ensures the displayed info aligns with the be aware’s goal and avoids presenting irrelevant knowledge. As an example, a each day be aware template might use metadata filtering to show solely conferences scheduled for that particular day, sustaining a centered and related each day overview.

These aspects of metadata filtering spotlight its integral position in controlling dynamic content material visibility. By enabling exact knowledge retrieval, offering the idea for conditional rendering, and enhancing contextual relevance, metadata filtering empowers customers to create extremely adaptable and centered be aware methods. With out efficient metadata filtering, reaching the core goal of creating Dataview content material disappear when no outcomes are discovered turns into considerably tougher. The mix of metadata filtering and conditional logic inside DataviewJS queries supplies the important instruments for managing info successfully and sustaining a streamlined workflow inside Obsidian.

7. Template Flexibility

Template flexibility is important for successfully managing dynamic content material visibility inside Dataview, significantly when aiming to suppress output when queries yield no outcomes. Adaptable templates enable content material constructions to regulate dynamically primarily based on knowledge availability, making certain solely related info is displayed. This adaptability is essential for sustaining clear and centered notes, stopping empty sections or placeholders from cluttering the interface when queries return no knowledge. With out template flexibility, reaching conditional rendering and controlling content material visibility turns into considerably tougher.

• Conditional Sections:

  Templates can incorporate conditional sections that seem or disappear primarily based on question outcomes. This permits whole blocks of content material, resembling mission summaries or activity lists, to be rendered solely when related knowledge exists. A mission administration template might embrace a activity checklist part that solely seems if duties are assigned to that mission. This prevents empty activity lists from cluttering mission notes when no duties are current, sustaining a centered and uncluttered view.

• Variable Content material Inclusion:

  Template flexibility extends to variable content material inclusion. Particular parts inside a template will be dynamically populated or omitted primarily based on knowledge availability. Think about a guide assessment template. A piece for quotes could possibly be conditionally included provided that quotes have been added to the be aware. This avoids displaying empty quote sections, sustaining a streamlined template construction that adapts to the obtainable info. This degree of management enhances the template’s reusability throughout numerous contexts.

• Iterative Rendering:

  Templates can leverage iterative rendering to generate repeating content material blocks primarily based on question outcomes. For instance, a gathering notes template can make the most of iterative rendering to create a separate part for every attendee, displaying their particular person contributions. If an attendee didn’t contribute, the corresponding part will be omitted, making certain solely related participant info is displayed. This avoids pointless repetition and maintains a concise assembly abstract.

• Nested Conditionals:

  Extra advanced templates can incorporate nested conditional logic, permitting for nuanced management over content material visibility. A template summarizing analysis papers might embrace a piece for experimental outcomes, which additional comprises subsections for various experimental circumstances. These subsections could possibly be conditionally rendered primarily based on the supply of information for every situation. This granular management ensures solely related experimental knowledge is displayed, sustaining a clear and arranged construction even inside advanced analysis summaries.

These aspects of template flexibility underscore its significance in reaching dynamic content material management inside Dataview. By enabling conditional sections, variable content material inclusion, iterative rendering, and nested conditionals, templates grow to be highly effective instruments for creating adaptable and responsive notes. This flexibility instantly addresses the core goal of creating Dataview content material disappear when no outcomes are discovered, contributing to a extra environment friendly and uncluttered note-taking expertise inside Obsidian.

8. Workflow Enhancement

Workflow enhancement is a direct consequence of successfully managing dynamic content material visibility inside Dataview. The power to suppress question outcomes when no knowledge exists, successfully making content material disappear, streamlines info entry and reduces cognitive overhead. This contributes to a extra centered and environment friendly workflow by presenting solely related info, eliminating the necessity to sift by way of empty sections or irrelevant knowledge. Think about a researcher utilizing Obsidian to handle literature notes. With out conditional rendering, literature evaluations may include quite a few empty sections for papers missing particular knowledge factors (e.g., experimental outcomes, particular methodologies). By conditionally displaying these sections solely when knowledge exists, the researcher positive factors a clearer overview of the related literature, focusing solely on papers pertinent to the present analysis query. This focused info entry instantly interprets right into a extra environment friendly literature assessment course of.

The sensible significance of this workflow enhancement extends to numerous eventualities. Venture managers utilizing Obsidian for activity administration profit from dynamic activity lists that solely show duties related to the present mission part. Empty mission sections are eradicated, offering a centered view of energetic duties and streamlining mission monitoring. Equally, writers can use conditional rendering to dynamically show related analysis notes, outlines, or character sketches primarily based on the present writing context. This eliminates distractions and ensures solely pertinent info is available, fostering a extra centered and productive writing atmosphere. In software program improvement, dynamic documentation generated by way of Dataview can conditionally show code examples, API references, or troubleshooting steps primarily based on the present improvement activity. This context-sensitive info supply minimizes search time and accelerates the event course of.

Conditional content material visibility, achieved by way of strategies like DataviewJS and strategic metadata filtering, is important for workflow optimization inside Obsidian. Whereas preliminary setup might require a deeper understanding of Dataview’s capabilities, the ensuing enhancements in info entry and cognitive effectivity considerably improve productiveness. The power to tailor info show to particular contexts reduces litter, minimizes distractions, and in the end fosters a extra streamlined and efficient workflow throughout numerous information work domains. The problem lies in placing a stability between template complexity and maintainability, making certain the advantages of conditional rendering outweigh the overhead of implementing and managing advanced queries. This cautious stability permits customers to completely leverage the facility of Dataview for enhanced information administration and workflow optimization.

9. Improved Readability

Improved readability is a direct consequence of controlling dynamic content material visibility inside Obsidian notes utilizing Dataview. By suppressing the show of irrelevant or empty question outcomes, notes grow to be extra centered and simpler to parse. This enhanced readability stems from decreasing visible litter and cognitive overhead related to processing pointless info. Think about a dashboard view aggregating info from a number of sources. With out conditional rendering, empty sections similar to data-deficient sources would litter the view, hindering fast comprehension. Conditional show ensures solely sections with precise knowledge are rendered, considerably bettering the dashboard’s at-a-glance readability. Equally, in a each day be aware incorporating dynamic activity lists, suppressing empty lists for initiatives with out present duties declutters the be aware, permitting for speedy evaluation of each day priorities.

The sensible significance of this improved readability extends past easy visible readability. In advanced analysis notes, dynamically hiding irrelevant literature summaries or experimental knowledge primarily based on particular queries dramatically improves comprehension. The reader’s consideration stays centered on the pertinent info, decreasing the cognitive effort required to extract key insights. This focused info presentation permits for extra environment friendly evaluation and synthesis of advanced analysis supplies. In mission administration contexts, dynamically hiding accomplished duties or irrelevant mission particulars streamlines mission monitoring. The mission overview turns into extra concise, facilitating fast assessments of mission standing and upcoming milestones. This environment friendly info entry contributes to improved decision-making and mission execution. In collaborative writing eventualities, dynamically controlling part visibility permits writers to concentrate on particular facets of a doc, resembling character improvement, plot outlines, or analysis supplies, with out being distracted by irrelevant sections.

Conditional content material visibility, due to this fact, is essential for maximizing readability inside Obsidian. Whereas reaching dynamic management might require preliminary effort in establishing Dataview queries and JavaScript logic, the ensuing enhancements in readability contribute considerably to extra environment friendly information administration and improved cognitive focus. Challenges might come up in balancing template complexity with maintainability, requiring cautious consideration of question construction and conditional logic. In the end, the advantages of enhanced readability, enabling speedy info assimilation and diminished cognitive burden, outweigh the preliminary funding in establishing efficient conditional rendering methods. This cautious stability permits customers to completely leverage the facility of Dataview and remodel Obsidian into a really responsive and environment friendly information administration instrument.

Continuously Requested Questions

This part addresses frequent queries concerning the conditional show of Dataview content material inside Obsidian, specializing in strategies to suppress output when question outcomes are empty.

Query 1: What are the first strategies for hiding Dataview content material when no outcomes are discovered?

The first methodology entails utilizing DataviewJS, which permits JavaScript code to manage rendering logic primarily based on question outcomes. Particularly, `if/else` statements throughout the JavaScript code can examine for empty end result units and forestall content material rendering.

Query 2: How does JavaScript integration improve management over Dataview output?

JavaScript supplies the logical framework mandatory for conditional rendering. With out JavaScript, Dataview primarily capabilities as a templating engine, missing the flexibility to react dynamically to question outcomes. JavaScript permits for extra advanced evaluations and management over what’s displayed primarily based on these outcomes.

Query 3: Can normal Dataview queries obtain the identical conditional rendering as DataviewJS?

Normal Dataview queries provide restricted conditional rendering capabilities. Whereas some primary filtering will be achieved, advanced logic requiring evaluations and conditional show of content material necessitates the usage of DataviewJS.

Query 4: Are there efficiency issues when utilizing JavaScript inside Dataview?

Advanced JavaScript code inside Dataview queries can probably affect efficiency, significantly with massive datasets or advanced circumstances. Optimizing JavaScript code for effectivity and minimizing pointless computations can mitigate potential efficiency bottlenecks.

Query 5: How can metadata affect the conditional show of content material?

Metadata acts as the first filter for Dataview queries. By defining particular metadata standards, queries can selectively retrieve knowledge. This focused knowledge retrieval varieties the idea for conditional rendering, because the presence or absence of particular metadata determines whether or not content material is displayed.

Query 6: What are the benefits of utilizing dynamic content material management in comparison with static content material show?

Dynamic content material adapts to altering knowledge and user-specified standards, creating extra responsive and uncluttered notes. Static content material stays fastened no matter knowledge modifications, resulting in potential redundancy and diminished readability. Dynamic content material, managed successfully, ensures solely related info is displayed, enhancing readability and effectivity.

Mastering conditional rendering strategies empowers customers to create adaptable, centered, and extremely readable notes. By understanding the interaction between DataviewJS, metadata filtering, and template design, one can successfully harness the total energy of Dataview for enhanced information administration inside Obsidian.

The next part will delve into particular code examples and sensible implementation methods for conditional content material show inside Dataview.

Sensible Ideas for Conditional Dataview Rendering

The following pointers present sensible steerage for implementing conditional content material show inside Dataview, specializing in suppressing output when queries yield no outcomes. Efficient implementation enhances be aware group, readability, and total workflow effectivity inside Obsidian.

Tip 1: Make the most of `dv.pages(”)` for Empty Array Checks: When checking for empty arrays returned by Dataview queries, using `dv.pages(”)` inside a conditional assertion affords a concise and dependable methodology. This ensures the code block executes solely when outcomes exist, stopping pointless rendering of empty sections. Instance: `if (dv.pages(‘”tag”‘).size > 0) { }`

Tip 2: Leverage the `none` Key phrase for Empty Consequence Dealing with: The `none` key phrase inside DataviewJS supplies a streamlined method to dealing with empty question outcomes. This key phrase simplifies the conditional logic, making templates cleaner and simpler to keep up. Instance: `dv.pages(‘”tag”‘) or “No outcomes discovered.”`

Tip 3: Make use of `if/else` Statements for Advanced Conditional Logic: For extra advanced eventualities involving a number of circumstances or knowledge manipulations, JavaScript’s `if/else` statements provide granular management over content material rendering. This allows tailor-made show logic primarily based on numerous knowledge states. Instance: “`javascript if (dv.pages(‘”tag1″ and “tag2″‘).size > 0) { dv.taskList(dv.pages(‘”tag1” and “tag2″‘)); } else if (dv.pages(‘”tag1″‘).size > 0) { dv.paragraph(“Solely tag1 discovered.”); } else { dv.paragraph(“No matching tags discovered.”); } “`

Tip 4: Construction Templates for Clear Conditional Rendering: Organizing templates with distinct sections for conditionally rendered content material improves maintainability and readability. This clear separation facilitates debugging and modification of rendering logic. Instance: Utilizing HTML `