Open Graph Beta / Meta Tags - meta-tags

do you have to add og meta tags manually to each webpage? I have a website that has lots of seperate articles and I need a way to automatically create the og tags
Thanks

If your articles are generated by a server side programming language, you could programmatically add the meta tags into the code which outputs the other article information
If they're individual HTML files you'll have to add them manually or write a script to insert them into your pages

Related

AsciiDoc navigation panel

How i can create a left navigation panel in AsciiDoc?
like this one here https://docs.asciidoctor.org/asciidoc/latest/
not a list of contents.
Thanks.
The navigation pane in your screenshot includes links to many HTML files. asciidoctor doesn't have any built-in facility for generating multiple HTML files from an Asciidoc markup file.
To do that for your own Asciidoc content, you need a tool that processes many Asciidoc files and generates an entire site. Such tools are called static site generators. There are many, and quite a few support Asciidoc markup, including Hugo, Jekyll, and Eleventy.
The Asciidoctor documentation was generated with a tool called Antora, which was created by the author of asciidoctor. Its goal is to specifically support generating technical documentation web sites (and eventually PDF documents) from Asciidoc markup.
Many companies with large sets of technical documentation use Antora. This page lists the companies and sites using Antora, plus public repos with the implementations (where available).

Editing xmp tags pyexiv2 modify_xmp does not replace xmp tags correctly

I am trying to write a script that will loop through a large number of images and write new xmp tags based on certain criteria.
I am using pyexiv2 to read and modify the 'Xmp.dc.subject' tag.
I am able to assign a new set of tags to the image, and using pyexiv2.read_xmp() to check my results shows that the new set of tags has replaced the old set of tags, as expected.
However, when I check the properties in windows explorer or another photo manager, the old tags remain in addition to the new set of tags.
see my code below
from pyexiv2 import Image
path=some_path
img=Image(path)
tags=img.read_xmp()
tags.get('Xmp.dc.subject') ####outputs list of tags ['old_tag1', 'old_tag2', 'old_tag3']
newtags=['new_tag1','new_tag2']
dict1={'Xmp.dc.subject':newtags}
img.modify_xmp(dict1)
img.close()
Now, when I open properties of the file in Explorer, or check in a photo manager software, the tags on the file are ['old_tag1', 'old_tag2', 'old_tag3','new_tag1','new_tag2']. The expected behaviour as stated in the pyexiv2 tutorial is that the new list of tags will replace the old tags.
I have tried using py3exiv2, but I am having problems with that library due to an error referencing Microsoft Visual Studio.
Is there a way to achieve my outcome ideally using pyexiv2, or alternatively using any other method?
I found the solution to this problem.
Windows explorer (and Adbobe Bridge, and i'm guessing other software too) displays both xmp tags and iptc tags.
So if you modify the xmp tags only, explorer (or other software) will show the new xmp tags as well as the old iptc tags.
So the solution is to use modify_xmp() and modify_iptc() to change both sets of tags.

Is there a way to read a word document section by section with c#

I have a word template which has multiple sections( tables, parragraphs, lists, etc.. ). The idea is that users fill the template and upload it to a asp.net application. I need the application to read the information section by section. So, is there a way to name the section of a word document and identify it by using c#?
I think it is much better to create a custom web page for filling fields there and constructing a Word document on the server-side using the Open XML SDK, see Welcome to the Open XML SDK 2.5 for Office for more information.
However, you may consider using bookmarks or content controls as a marker for sections.
Otherwise, you'll need to parse the uploaded document by searching for keywords presented in the template.

SharePoint - Document Filtering (Tags/Metadata?)

I'm creating a SharePoint site which will be used to dynamically store and display documents on various pages, among other things. Is the following possible?
My view is to have one central Document Library which will include all files. Files with have 'tags' or 'metadata' attached to them. On pages, i will add a document library (or similar) webpart and then call only those documents with a certain tag/metadata.
For example.
Document Library ('Folder') - Contains ('Project Document.xls' and 'Training Document.ppt')
On 'index.html' i will add 'Folder' to the page, but i only want to display 'Project Document.xls' not 'Training Document.ppt'.
I'm aware that you can set up target audiences but that requires a lot of user management.
Thanks for any advice.
If I understand you correctly, this sounds like something you could accomplish using a filter. The name of the file is stored as a column. Try editing the web part on that page and edit the current view. That view will be cached for that page without changing the view across the site. If you want to be able to dynamically choose the document you display then one option is to add an HTML Form web part (which contains a text box and submit button), connect it to the doc library web part and filter the name column based on the HTML Form web part.

Sharepoint - Custom ItemStyle in a new file

how can I customize the presentation of a Content Query Web Part by modyfing the xsl it uses without touching ItemStyle.xsl but using a brand new .xsl file?
I'm using MOSS 2007.
Thanks
There are lots of Articles on Customising the CQWP,
Healther Soloman's being one of my faves
here
But this
is a succint article doing exactly what you describe
using your own xsl by changing the Settings in the DWP (export/edit/import)
You could get really fancy and create your own version of the CQWP by inheriting from ContentByQueryWebPart and setting all the attributes you want in that code and including the files in you new feature to house said webpart and new files.

Resources