 # This is the title of a demo blog post Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. This paragrph will show us an example of and inline link [This is the link](https://loremipsum.io/). Next we'll look at created ordered and unordered lists. Oh and if you would like to add an image to a doc please make sure the url is using ipfs. You can go here (as of 4/3/2024) to upload an image to ipfs. At this location you will only get the cid: bafkreicfdfpu5kwn3ofi6tw2pvdxugybhmt5pt5gdjuxvi6dwkulfwwwxi, simply add that to the end of this url and you should be good to go! https://ipfs.near.social/ipfs/. ex: https://ipfs.near.social/ipfs/bafkreicfdfpu5kwn3ofi6tw2pvdxugybhmt5pt5gdjuxvi6dwkulfwwwxi. Once done imply create your alt text inside brackets with an exclamation point before it like so: ![my aweseom alt text here] + (my ipfs url). remove the + sign and the space and it will work properly. Also there is a little eye icon when posting this from near social. If you click on this while typing out your markdown you can see a preview of what your post will look like before committing it on chain.  ## This is the header/title for a section What separates this title form the post title is the number of hashtags. See the headings section of the basic markdown syntax page for me. Best practice is to have a full blank line before and after all headings. Below we will see an unordered list. - The '-' also know as a hyphen or minus sign with a space after will act as the bullet for an ordered list. Like with the headings it's best practice to have a space before and after each list item. - This one contians a link [NEAR DA](https://near.org/data-availability?_gl=1*uon6x3*_up*MQ..*_ga*MTAwODQzODc0OS4xNzA5MzI0ODM5*_ga_9GWCXQJ62J*MTcwOTMyNDgzNy4xLjAuMTcwOTMyNDgzNy4wLjAuMA), [zkWASM](https://blockworks.co/news/polygon-developers-zk-proofs) (collaboration with Polygon Labs), and another one [EigenLayer-powered Fast Finality](https://near.org/blog/near-foundation-and-eigen-labs-partner-to-enable-faster-cheaper-web3-transactions-for-ethereum-rollups-via-eigenlayer/?_gl=1*52qige*_up*MQ..*_ga*MTAwODQzODc0OS4xNzA5MzI0ODM5*_ga_9GWCXQJ62J*MTcwOTMyNDgzNy4xLjAuMTcwOTMyNDgzNy4wLjAuMA). - Account aggregation on top of this to enable transacting on all chains using a single account - Data layer that supports everything from monolithic, integrated, modular, private and permissioned chains to query data in a [predictable protocol](https://docs.near.org/bos/queryapi/intro). You can also begin a paragraph in the middle of an ordered list. Maybe to tell someone about using a single '*' instead of a '-', however * Intent relayers that can execute complex intents across chains using this infra. * [Decentralized frontends](https://docs.near.org/bos/overview) that provide discoverability and composability for multiple apps across chains into one experience. * Just don't mix in match the '*' and '-' when you're creating your unordered list. Now let's take a look at another list. This one will be ordered. 1. Number, period, space. That is the format and you're good to go. 2. No space between these items. 1. you can also add nested items. The key here is to provided proper indentation via spaces. Sorry tabs. That said this can be a bit tricky so see the [basic syntax doc](https://www.markdownguide.org/basic-syntax/#ordered-lists) for more details. - and nested items can contain unordered lists too! - In case this is something you needed. - Just remember the rules around spacing. If you use 1 space for the parent list item and two for a list within your first item, you will need at least 3 (but 4 is best practive) spaces to get things to look how you want. 3.This concludes our ordered lists section ## Call to Action Maybe there is something you want to block quote. use the'>' and there are quite a few more options available in the [basic syntax doc](https://www.markdownguide.org/basic-syntax/#ordered-lists). > Let’s make chain abstraction a movement. The NEAR ecosystem invites builders from across Web3 to take advantage of the solutions we’re offering and to collaborate with us to build more chain abstraction solutions together. Stay tuned for more news on collaborations as well as details on an exciting event that NEAR Foundation will co-host at ETHDenver 2024. *Special thanks to Zaki Manian for conversations that led to this post as well as for his review.*