{"id":140,"date":"2009-08-14T14:14:14","date_gmt":"2009-08-14T08:44:14","guid":{"rendered":"https:\/\/www.bridge-global.com\/blog\/blog\/\/?p=140"},"modified":"2020-06-23T12:37:39","modified_gmt":"2020-06-23T12:37:39","slug":"website-wireframes","status":"publish","type":"post","link":"https:\/\/www.bridge-global.com\/blog\/website-wireframes\/","title":{"rendered":"Website Wireframes"},"content":{"rendered":"

<\/p>\n

\"WebsiteI came across a very interesting article on the blog of Infosys. The author, Ritesh Radhakrishnan, describes why currently available wireframe tools fall short in capturing the requirements of a rich web 2.0 site or application. As traditional websites were more static, straightforward tools to describe each element in a web page were sufficient. But with the current web 2.0 advancements, we get more javascript, Flash, Flex and other technologies which require more advanced requirements specification.<\/p>\n

I believe that web projects may in some respect be more complex to capture in clear requirements then a traditional software project. The challenge in software projects is to clearly specify the logical complexity. The challenge in web projects is to clearly specify rich interfaces + in more complex web applications, also the logic. I do agree with the author that there is a need for advanced wireframe tools that can help us develop complex web projects that start with clear specifications.
If anybody knows of a tool described in the article, I hope you will share it on our blog.<\/p>\n

The text of the article:

The Ancient Art of Wireframing<\/strong><\/p>\n

Website Wireframes have been always been an essential tool for capturing user interface requirements. They have been very effective in ideating, discussing and capturing the UI requirements for a new website. They have been an essential mode<\/p>\n<\/p>\n

\"WebsiteI came across a very interesting article on the blog of Infosys. The author, Ritesh Radhakrishnan, describes why currently available wireframe tools fall short in capturing the requirements of a rich web 2.0 site or application. As traditional websites were more static, straightforward tools to describe each element in a web page were sufficient. But with the current web 2.0 advancements, we get more javascript, Flash, Flex and other technologies which require more advanced requirements specification.<\/p>\n

I believe that web projects may in some respect be more complex to capture in clear requirements then a traditional software project. The challenge in software projects is to clearly specify the logical complexity. The challenge in web projects is to clearly specify rich interfaces + in more complex web applications, also the logic. I do agree with the author that there is a need for advanced wireframe tools that can help us develop complex web projects that start with clear specifications.
\nIf anybody knows of a tool described in the article, I hope you will share it on our blog.<\/p>\n

The text of the article:
\n
\nThe Ancient Art of Wireframing<\/strong><\/p>\n

Website Wireframes have been always been an essential tool for capturing user interface requirements. They have been very effective in ideating, discussing and capturing the UI requirements for a new website. They have been an essential mode<\/p>\n<\/p>\n

\"WebsiteI came across a very interesting article on the blog of Infosys. The author, Ritesh Radhakrishnan, describes why currently available wireframe tools fall short in capturing the requirements of a rich web 2.0 site or application. As traditional websites were more static, straightforward tools to describe each element in a web page were sufficient. But with the current web 2.0 advancements, we get more javascript, Flash, Flex and other technologies which require more advanced requirements specification.<\/p>\n

I believe that web projects may in some respect be more complex to capture in clear requirements then a traditional software project. The challenge in software projects is to clearly specify the logical complexity. The challenge in web projects is to clearly specify rich interfaces + in more complex web applications, also the logic. I do agree with the author that there is a need for advanced wireframe tools that can help us develop complex web projects that start with clear specifications.
\nIf anybody knows of a tool described in the article, I hope you will share it on our blog.<\/p>\n

The text of the article:
\n
\nThe Ancient Art of Wireframing<\/strong><\/p>\n

Website Wireframes have been always been an essential tool for capturing user interface requirements. They have been very effective in ideating, discussing and capturing the UI requirements for a new website. They have been an essential mode<\/p>\n<\/p>\n

\"WebsiteI came across a very interesting article on the blog of Infosys. The author, Ritesh Radhakrishnan, describes why currently available wireframe tools fall short in capturing the requirements of a rich web 2.0 site or application. As traditional websites were more static, straightforward tools to describe each element in a web page were sufficient. But with the current web 2.0 advancements, we get more javascript, Flash, Flex and other technologies which require more advanced requirements specification.<\/p>\n

I believe that web projects may in some respect be more complex to capture in clear requirements then a traditional software project. The challenge in software projects is to clearly specify the logical complexity. The challenge in web projects is to clearly specify rich interfaces + in more complex web applications, also the logic. I do agree with the author that there is a need for advanced wireframe tools that can help us develop complex web projects that start with clear specifications.
\nIf anybody knows of a tool described in the article, I hope you will share it on our blog.<\/p>\n

The text of the article:
\n
\nThe Ancient Art of Wireframing<\/strong><\/p>\n

Website Wireframes have been always been an essential tool for capturing user interface requirements. They have been very effective in ideating, discussing and capturing the UI requirements for a new website. They have been an essential mode of communication for web designers to express their designs to clients and developers alike.\u00a0 But over the last few years, the rules of the game have changed threatening to make the art of wireframing obsolete.<\/p>\n

What are website wireframes?<\/strong><\/p>\n

Wireframes are simple line drawings which aide visual design. They represent the layout of various pages and relationship between them. They are the fist step in visualizing a new website and are drawn before the artwork is done. Once Wireframes have been finalized post discussions with the client, the web designers fill in the colors and artwork to complete the UI specifications for the website.<\/p>\n

So what has changed?<\/strong><\/p>\n

The last few years have seen a new wave of website, popularly referred to as Rich Internet Applications. These websites mimic desktop applications more and more closely and have capabilities to deliver a much richer user experience than the traditional websites through usage of various technologies like Flex, DHTM Toolkits and AJAX. The user experience of these websites can no longer be expressed using simple line diagrams or artwork. Some of these features are animations, transitions and partial page refreshes. Wireframes fall short when it comes to capturing these aspects of the new websites.<\/p>\n

An example is a fly-out menu. A fly-out menu has many more information points to be captured than merely how it looks or where it appears. It is important to capture the speed at which it animates, the transition while it appears, how it animates upon various events like mouse over or mouse out, when it disappears and how it should transition while disappearing. These aspects today are usually captured as notes on the wireframes or more often decided only after a prototype is built. But these aspects of UI design are as core to the user experience as are the placement of content and appearance. The speed of transition could change a cool feature into a visually disturbing blotch on your website.<\/p>\n

Did you say agile?<\/strong><\/p>\n

Am sure most of you have heard of \u201cagile methodologies\u201d and some of you lucky ones out there would have even worked on \u201cagile\u201d projects. To me, the basic tenets of agile methodology is to build iteratively, while maintaining the connect with your client all along. What better methodology would fit a User Experience design project, which relies heavily on client feedback? But User Experience design has been painstakingly slow and costly because of the long cycle time involved from Wireframing to Artwork design to prototyping before the users can actually experience the final product. It has brought about the question, is wireframing really worth the money?<\/p>\n

Time for a new standard?<\/strong><\/p>\n

Firstly, It is quite obvious in my belief that the current UI methods and tools are unfit for capturing and building the rich user experience of the websites of tomorrow. Secondly, there is no standard path to convert a Rich UI design into a working prototype automatically. The need of the hour is to be able to cut down the time from wireframing to prototyping for a rich web site.<\/p>\n

In my opinion, this calls for a new standard for RIA UI wireframes Standard. The new standard for UI wireframes needs to define the following aspects of UI design<\/p>\n

1.\u00a0\u00a0 \u00a0Core components of a UI design, e.g. simple content areas to rich widgets like an accordion, carousel, fly-out, and animation.
2.\u00a0\u00a0 \u00a0Core parameters defining the behavioral aspects of every UI component e.g. animation speed, direction, rotation, transition, partial page refresh, drag-able or drop-able etc.
3.\u00a0\u00a0 \u00a0Events on each component e.g. onClick, onMouseOver, onMouseOut etc.
4.\u00a0\u00a0 \u00a0Relationships between different components e.g. when one rotates, the other component should slide.<\/p>\n

This standard could also be extended to capture non-functional aspects like accessibility support, performance and response times and low vs hign bandwidth behaviour.<\/p>\n

What are the advantages?<\/strong><\/p>\n

Here are a few advantages of defining a wireframes standard I could think of :<\/p>\n

1.\u00a0\u00a0 \u00a0A new standard will help capture and communicate UI designs for Rich website more effectively, without any miscommunication.
2.\u00a0\u00a0 \u00a0Tools could be developed based on the standard to quickly build wireframes by dragging, dropping and configuring UI components from a palette, like HTML design tools do today.
3.\u00a0\u00a0 \u00a0Ability to generate code directly from the UI design in the language of choice e.g. Flex or Javascript.
4.\u00a0\u00a0 \u00a0Advanced tools could help generate a UI prototype along with the wireframe enabling the clients to preview all aspects of the new UI design.<\/p>\n

The Web 2.0 way<\/strong><\/p>\n

In the future, a standard understood by everyone could also allow collaborative development of UI designs by putting a UI design tool on the web for users to create their own version through simple drag and drop and configuration. The best UI version could emerge by considering the most popular settings for each information point, e.g. the animation time selected by most users could be the most visually pleasing.

Source: http:\/\/www.infosysblogs.com<\/a><\/p>\n

\"\"<\/a><\/p>\n

of communication for web designers to express their designs to clients and developers alike.\u00a0 But over the last few years, the rules of the game have changed threatening to make the art of wireframing obsolete.<\/p>\n

What are website wireframes?<\/strong><\/p>\n

Wireframes are simple line drawings which aide visual design. They represent the layout of various pages and relationship between them. They are the fist step in visualizing a new website and are drawn before the artwork is done. Once Wireframes have been finalized post discussions with the client, the web designers fill in the colors and artwork to complete the UI specifications for the website.<\/p>\n

So what has changed?<\/strong><\/p>\n

The last few years have seen a new wave of website, popularly referred to as Rich Internet Applications. These websites mimic desktop applications more and more closely and have capabilities to deliver a much richer user experience than the traditional websites through usage of various technologies like Flex, DHTM Toolkits and AJAX. The user experience of these websites can no longer be expressed using simple line diagrams or artwork. Some of these features are animations, transitions and partial page refreshes. Wireframes fall short when it comes to capturing these aspects of the new websites.<\/p>\n

An example is a fly-out menu. A fly-out menu has many more information points to be captured than merely how it looks or where it appears. It is important to capture the speed at which it animates, the transition while it appears, how it animates upon various events like mouse over or mouse out, when it disappears and how it should transition while disappearing. These aspects today are usually captured as notes on the wireframes or more often decided only after a prototype is built. But these aspects of UI design are as core to the user experience as are the placement of content and appearance. The speed of transition could change a cool feature into a visually disturbing blotch on your website.<\/p>\n

Did you say agile?<\/strong><\/p>\n

Am sure most of you have heard of \u201cagile methodologies\u201d and some of you lucky ones out there would have even worked on \u201cagile\u201d projects. To me, the basic tenets of agile methodology is to build iteratively, while maintaining the connect with your client all along. What better methodology would fit a User Experience design project, which relies heavily on client feedback? But User Experience design has been painstakingly slow and costly because of the long cycle time involved from Wireframing to Artwork design to prototyping before the users can actually experience the final product. It has brought about the question, is wireframing really worth the money?<\/p>\n

Time for a new standard?<\/strong><\/p>\n

Firstly, It is quite obvious in my belief that the current UI methods and tools are unfit for capturing and building the rich user experience of the websites of tomorrow. Secondly, there is no standard path to convert a Rich UI design into a working prototype automatically. The need of the hour is to be able to cut down the time from wireframing to prototyping for a rich web site.<\/p>\n

In my opinion, this calls for a new standard for RIA UI wireframes Standard. The new standard for UI wireframes needs to define the following aspects of UI design<\/p>\n

1.\u00a0\u00a0 \u00a0Core components of a UI design, e.g. simple content areas to rich widgets like an accordion, carousel, fly-out, and animation.
\n2.\u00a0\u00a0 \u00a0Core parameters defining the behavioral aspects of every UI component e.g. animation speed, direction, rotation, transition, partial page refresh, drag-able or drop-able etc.
\n3.\u00a0\u00a0 \u00a0Events on each component e.g. onClick, onMouseOver, onMouseOut etc.
\n4.\u00a0\u00a0 \u00a0Relationships between different components e.g. when one rotates, the other component should slide.<\/p>\n

This standard could also be extended to capture non-functional aspects like accessibility support, performance and response times and low vs hign bandwidth behaviour.<\/p>\n

What are the advantages?<\/strong><\/p>\n

Here are a few advantages of defining a wireframes standard I could think of :<\/p>\n

1.\u00a0\u00a0 \u00a0A new standard will help capture and communicate UI designs for Rich website more effectively, without any miscommunication.
\n2.\u00a0\u00a0 \u00a0Tools could be developed based on the standard to quickly build wireframes by dragging, dropping and configuring UI components from a palette, like HTML design tools do today.
\n3.\u00a0\u00a0 \u00a0Ability to generate code directly from the UI design in the language of choice e.g. Flex or Javascript.
\n4.\u00a0\u00a0 \u00a0Advanced tools could help generate a UI prototype along with the wireframe enabling the clients to preview all aspects of the new UI design.<\/p>\n

The Web 2.0 way<\/strong><\/p>\n

In the future, a standard understood by everyone could also allow collaborative development of UI designs by putting a UI design tool on the web for users to create their own version through simple drag and drop and configuration. The best UI version could emerge by considering the most popular settings for each information point, e.g. the animation time selected by most users could be the most visually pleasing.
\n
\nSource: http:\/\/www.infosysblogs.com<\/a><\/p>\n<\/p>\n

of communication for web designers to express their designs to clients and developers alike.\u00a0 But over the last few years, the rules of the game have changed threatening to make the art of wireframing obsolete.<\/p>\n

What are website wireframes?<\/strong><\/p>\n

Wireframes are simple line drawings which aide visual design. They represent the layout of various pages and relationship between them. They are the fist step in visualizing a new website and are drawn before the artwork is done. Once Wireframes have been finalized post discussions with the client, the web designers fill in the colors and artwork to complete the UI specifications for the website.<\/p>\n

So what has changed?<\/strong><\/p>\n

The last few years have seen a new wave of website, popularly referred to as Rich Internet Applications. These websites mimic desktop applications more and more closely and have capabilities to deliver a much richer user experience than the traditional websites through usage of various technologies like Flex, DHTM Toolkits and AJAX. The user experience of these websites can no longer be expressed using simple line diagrams or artwork. Some of these features are animations, transitions and partial page refreshes. Wireframes fall short when it comes to capturing these aspects of the new websites.<\/p>\n

An example is a fly-out menu. A fly-out menu has many more information points to be captured than merely how it looks or where it appears. It is important to capture the speed at which it animates, the transition while it appears, how it animates upon various events like mouse over or mouse out, when it disappears and how it should transition while disappearing. These aspects today are usually captured as notes on the wireframes or more often decided only after a prototype is built. But these aspects of UI design are as core to the user experience as are the placement of content and appearance. The speed of transition could change a cool feature into a visually disturbing blotch on your website.<\/p>\n

Did you say agile?<\/strong><\/p>\n

Am sure most of you have heard of \u201cagile methodologies\u201d and some of you lucky ones out there would have even worked on \u201cagile\u201d projects. To me, the basic tenets of agile methodology is to build iteratively, while maintaining the connect with your client all along. What better methodology would fit a User Experience design project, which relies heavily on client feedback? But User Experience design has been painstakingly slow and costly because of the long cycle time involved from Wireframing to Artwork design to prototyping before the users can actually experience the final product. It has brought about the question, is wireframing really worth the money?<\/p>\n

Time for a new standard?<\/strong><\/p>\n

Firstly, It is quite obvious in my belief that the current UI methods and tools are unfit for capturing and building the rich user experience of the websites of tomorrow. Secondly, there is no standard path to convert a Rich UI design into a working prototype automatically. The need of the hour is to be able to cut down the time from wireframing to prototyping for a rich web site.<\/p>\n

In my opinion, this calls for a new standard for RIA UI wireframes Standard. The new standard for UI wireframes needs to define the following aspects of UI design<\/p>\n

1.\u00a0\u00a0 \u00a0Core components of a UI design, e.g. simple content areas to rich widgets like an accordion, carousel, fly-out, and animation.
\n2.\u00a0\u00a0 \u00a0Core parameters defining the behavioral aspects of every UI component e.g. animation speed, direction, rotation, transition, partial page refresh, drag-able or drop-able etc.
\n3.\u00a0\u00a0 \u00a0Events on each component e.g. onClick, onMouseOver, onMouseOut etc.
\n4.\u00a0\u00a0 \u00a0Relationships between different components e.g. when one rotates, the other component should slide.<\/p>\n

This standard could also be extended to capture non-functional aspects like accessibility support, performance and response times and low vs hign bandwidth behaviour.<\/p>\n

What are the advantages?<\/strong><\/p>\n

Here are a few advantages of defining a wireframes standard I could think of :<\/p>\n

1.\u00a0\u00a0 \u00a0A new standard will help capture and communicate UI designs for Rich website more effectively, without any miscommunication.
\n2.\u00a0\u00a0 \u00a0Tools could be developed based on the standard to quickly build wireframes by dragging, dropping and configuring UI components from a palette, like HTML design tools do today.
\n3.\u00a0\u00a0 \u00a0Ability to generate code directly from the UI design in the language of choice e.g. Flex or Javascript.
\n4.\u00a0\u00a0 \u00a0Advanced tools could help generate a UI prototype along with the wireframe enabling the clients to preview all aspects of the new UI design.<\/p>\n

The Web 2.0 way<\/strong><\/p>\n

In the future, a standard understood by everyone could also allow collaborative development of UI designs by putting a UI design tool on the web for users to create their own version through simple drag and drop and configuration. The best UI version could emerge by considering the most popular settings for each information point, e.g. the animation time selected by most users could be the most visually pleasing.
\n
\nSource: http:\/\/www.infosysblogs.com<\/a><\/p>\n<\/p>\n

of communication for web designers to express their designs to clients and developers alike.\u00a0 But over the last few years, the rules of the game have changed threatening to make the art of wireframing obsolete.<\/p>\n

What are website wireframes?<\/strong><\/p>\n

Wireframes are simple line drawings which aide visual design. They represent the layout of various pages and relationship between them. They are the fist step in visualizing a new website and are drawn before the artwork is done. Once Wireframes have been finalized post discussions with the client, the web designers fill in the colors and artwork to complete the UI specifications for the website.<\/p>\n

So what has changed?<\/strong><\/p>\n

The last few years have seen a new wave of website, popularly referred to as Rich Internet Applications. These websites mimic desktop applications more and more closely and have capabilities to deliver a much richer user experience than the traditional websites through usage of various technologies like Flex, DHTM Toolkits and AJAX. The user experience of these websites can no longer be expressed using simple line diagrams or artwork. Some of these features are animations, transitions and partial page refreshes. Wireframes fall short when it comes to capturing these aspects of the new websites.<\/p>\n

An example is a fly-out menu. A fly-out menu has many more information points to be captured than merely how it looks or where it appears. It is important to capture the speed at which it animates, the transition while it appears, how it animates upon various events like mouse over or mouse out, when it disappears and how it should transition while disappearing. These aspects today are usually captured as notes on the wireframes or more often decided only after a prototype is built. But these aspects of UI design are as core to the user experience as are the placement of content and appearance. The speed of transition could change a cool feature into a visually disturbing blotch on your website.<\/p>\n

Did you say agile?<\/strong><\/p>\n

Am sure most of you have heard of \u201cagile methodologies\u201d and some of you lucky ones out there would have even worked on \u201cagile\u201d projects. To me, the basic tenets of agile methodology is to build iteratively, while maintaining the connect with your client all along. What better methodology would fit a User Experience design project, which relies heavily on client feedback? But User Experience design has been painstakingly slow and costly because of the long cycle time involved from Wireframing to Artwork design to prototyping before the users can actually experience the final product. It has brought about the question, is wireframing really worth the money?<\/p>\n

Time for a new standard?<\/strong><\/p>\n

Firstly, It is quite obvious in my belief that the current UI methods and tools are unfit for capturing and building the rich user experience of the websites of tomorrow. Secondly, there is no standard path to convert a Rich UI design into a working prototype automatically. The need of the hour is to be able to cut down the time from wireframing to prototyping for a rich web site.<\/p>\n

In my opinion, this calls for a new standard for RIA UI wireframes Standard. The new standard for UI wireframes needs to define the following aspects of UI design<\/p>\n

1.\u00a0\u00a0 \u00a0Core components of a UI design, e.g. simple content areas to rich widgets like an accordion, carousel, fly-out, and animation.
\n2.\u00a0\u00a0 \u00a0Core parameters defining the behavioral aspects of every UI component e.g. animation speed, direction, rotation, transition, partial page refresh, drag-able or drop-able etc.
\n3.\u00a0\u00a0 \u00a0Events on each component e.g. onClick, onMouseOver, onMouseOut etc.
\n4.\u00a0\u00a0 \u00a0Relationships between different components e.g. when one rotates, the other component should slide.<\/p>\n

This standard could also be extended to capture non-functional aspects like accessibility support, performance and response times and low vs hign bandwidth behaviour.<\/p>\n

What are the advantages?<\/strong><\/p>\n

Here are a few advantages of defining a wireframes standard I could think of :<\/p>\n

1.\u00a0\u00a0 \u00a0A new standard will help capture and communicate UI designs for Rich website more effectively, without any miscommunication.
\n2.\u00a0\u00a0 \u00a0Tools could be developed based on the standard to quickly build wireframes by dragging, dropping and configuring UI components from a palette, like HTML design tools do today.
\n3.\u00a0\u00a0 \u00a0Ability to generate code directly from the UI design in the language of choice e.g. Flex or Javascript.
\n4.\u00a0\u00a0 \u00a0Advanced tools could help generate a UI prototype along with the wireframe enabling the clients to preview all aspects of the new UI design.<\/p>\n

The Web 2.0 way<\/strong><\/p>\n

In the future, a standard understood by everyone could also allow collaborative development of UI designs by putting a UI design tool on the web for users to create their own version through simple drag and drop and configuration. The best UI version could emerge by considering the most popular settings for each information point, e.g. the animation time selected by most users could be the most visually pleasing.
\n
\nSource: http:\/\/www.infosysblogs.com<\/a><\/p>\n<\/p>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

I came across a very interesting article on the blog of Infosys. The author, Ritesh Radhakrishnan, describes why currently available wireframe tools fall short in capturing the requirements of a rich web 2.0 site or application. As traditional websites were …<\/p>\n","protected":false},"author":4,"featured_media":43502,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[112],"tags":[],"class_list":["post-140","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-custom-software-development"],"featured_image_src":"https:\/\/www.bridge-global.com\/blog\/wp-content\/uploads\/2009\/08\/blog-wireframe.jpg","author_info":{"display_name":"Hugo Messer","author_link":"https:\/\/www.bridge-global.com\/blog\/author\/hugomesser\/"},"_links":{"self":[{"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/posts\/140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/comments?post=140"}],"version-history":[{"count":3,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/posts\/140\/revisions"}],"predecessor-version":[{"id":43503,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/posts\/140\/revisions\/43503"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/media\/43502"}],"wp:attachment":[{"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/media?parent=140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/categories?post=140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bridge-global.com\/blog\/wp-json\/wp\/v2\/tags?post=140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}